Barry Forrest bforrest

Ability Level - Fundamentals f your proposal is accepted, this will appear as a description of your topic in the conference program. Please write in paragraph form. Limit to 75 words or less.(600 characters)

  Follow our journey, from passively watching a brew day to winning steins at the Bluebonnet Brew-Off and a gold medal at the Austin region of the NHC a year and a half later. We share the tips and tricks we learned from others and a few of the comical and frustrating mistakes that we made along the way.

Learning Objectives Please list three (3) key objectives that the audience can expect to learn from this presentation.

Description (Lyssa's callouts)
- The discussion will explore transforming as a verb rather than thinking of transformation as a noun. What would it mean for us to be transforming, not just others? What would it mean for someone to be steadfast and unchanging, witness to others’ transforming? How are agile transformations treated like one-time metamorphoses from caterpillar to butterfly?
- Agile experts have “already transformed” and are to assist others going through the same/similar transformation process. While there’s credibility established in being someone who has “been there, done that,” it can make it difficult for the expert to meet the person where they are empathetically and cause the expert to impose an agenda on them to transform in a particular way.
Existing:

Description: What does it mean for an organization of people to be transforming? Advanced agilists are often sought as experts to guide transformations. Agile experts have “already transformed” and are to assist others going th

Do you have team members that squabble like siblings on a family roadtrip? Are you struggling to find a solution for "She's looking at me!" or "He's on my side of the seat!"? There is hope. DISC is a tool that can help you identify where conflict exists within your team. Learning how to identify and more effectively communicate with folks in the four basic DISC behavior profiles just might be part of the answers which you seek. Come learn these skills along with how to make your teammates feel heard, and how to tailor your communication so that they hear you as well.

There's no Iron Throne in Team - Engineering a Culture of Psychological Safety

Abstract: Are your teams safe? Do your teammates have your back? The #1 indicator of a successful team is not team size, tenure, seniority or salary level, but Psychological Safety. Unsafe teams will break or dramatically under-perform. This highly interactive and sometimes introspective session will teach tools and techniques that you can apply within your team to increase psychological safety. Come learn your own dominant communication style and how to recognize it in others to help build safe, collaborative, productive teams.

TALK DESCRIPTION: The #1 indicator of a successful team is not team size, tenure, seniority or salary level, but Psychological Safety. We will start by learning the five effectiveness pillars of a psychologically safe team thru a constellation activity. Examples of how team members responded to an unsafe environment will be explored. We'll have an interactive DiSC activity to learn our dominant communica

Companies flock to agile hoping to get “Twice the Work in Half the Time” and experience crushing failures. Experience hands on learning of some of the key practices and habits that enable team and organizational agility, facilitate delivering customer value and realize the agile promise.

Learning objectives:

Understanding our own dominant communication style and coaching style
Explore DISC, a useful model for identifying and understanding others’ dominant communication styles
A technique for visualizing a team’s styles and recognizing potential conflicts within the team
Practice trust-building communication by adapting to others’ preferred communication styles
We will lead an activity for attendees to identify their dominant DISC style and explore the model as a group to review each of the four behavior styles. In this section, we will touch on what coaching sound like from each dominant behavior

	using System;
	using System.Collections.Generic;
	using System.IO;
	using System.Runtime.Serialization;
	using System.Runtime.Serialization.Json;
	using System.Text;
	using System.Threading.Tasks;
	using MassTransit;
	using MassTransit.Turnout;
	using Messages;

	namespace IDP4
	{
	public static class Config
	{
	public static IEnumerable<Client> GetClients()
	{
	new Client
	{
	ClientName = "DesktopClient",
	ClientId = "native.hybrid",

	pushd;
	import-module sqlps -disablenamechecking;
	popd;

	$s = new-object microsoft.sqlserver.management.smo.server 'localhost';
	$db = $s.Databases['ps_all_the_things'];
	foreach ($proc in $db.StoredProcedures \| where {($_.IsSystemObject -eq $false) -and ($_.Schema -eq 'dbo')}) {
	$file = 'd:\temp\' + $proc.Name + '.sql';
	Write-Host $proc.Name;
	$proc.script() \| Out-File $file;