The document outlines a series of exercises aimed at improving team dynamics and communication through activities that emphasize understanding and collaboration. It includes debrief sessions for participants to reflect on their perceptions and assumptions about colleagues in a rush hour scenario. Additionally, it introduces core values of agile software development and encourages teams to define and prioritize their personal core values and establish working agreements to foster better relationships.

1. Understanding Each Other
…and building on each other’s ideas…

2. Exercise Time
Game

3. Instructions
• Separate into 3 teams
• Elect a leader
• Leader gets a goal & shares
w/team (visual sharing only)
• 1st team to arrange all chairs
to meet goal w/in 2 min wins!
NO TALKING!
Accredited
to Chris Sims

4. Debrief

5. Exercise
• I’m going to present an image of people in rush
hour in NYC; I’ll have an arrow pointing to one
person.
• I want you to write down the following:
– Is this morning or afternoon rush? What gave you the
clue?
– What type of work do you think that person does &
why you thought that?
– What do you think that person is thinking?
– If you were given $1000 to help that person in some
way other than giving it directly to them, how would
you go about doing it? Why did you select this choice?

7. Exercise (Again)
• I’m going to again present the same image of
people in rush hour in NYC; I’ll have an arrow
pointing to a different person.
• I want you to write down the following:
– What type of work do you think that person does &
why you thought that?
– What do you think that person is thinking?
– If you were given $1000 to help that person in some
way other than giving it directly to them, how would
you go about doing it? Why did you select this choice?

9. Next Step
• For both your responses, categorize what your
answers were into the following:
What was factual?
(What could I actually see…)
What did I infer?
(What did I believe
may be occurring…)
Why did I think that?
(Any prior event that
to led my thinking…)

10. Ladder of Inference
Event
How To Find Common Ground When Engineers Don’t Like Features – Teresa Torres, Jan 2013

11. The Event Of Conversation

12. The Event Of Conversation

13. The Event Of Conversation

14. The Event Of Conversation

15. How do we
our
beliefsfrom getting
prevent
in the way?

16. a shared vision
Co-create

17. assumptions
Voluntarily make
explicit

18. “Yes and…”Utilize
thinking

19. Let’s Learn the Basics of Improv
Yes BUT ---
• Split into pairs
• Pick a person to start…
• For the next 3 minutes -
• That person will say something they want to do
– The other person is to contradict them and propose
something else
– ALWAYS start the sentence with “Yes, but…”
– (even better if you say “we should do” in this counter-
proposal)
Thanks to Mike Sutton
for my learning of this

20. Let’s Learn the Basics of Improv
Yes AND ---
• Same pairs
• Other person to start…
• For the next 3 minutes -
• That person will say something they want to do
– The other person is to add to it and propose
something additional
– ALWAYS start the sentence with “Yes, and…”
– (even better if you say “we can do” in this addition)
Thanks to Mike Sutton
for my learning of this

21. Debrief
• So how did you feel with the “Yes, but…”?
• Any different with “Yes and…”?
• Did you see any change in your thinking when
moving to “Yes and…”?

22. Core
Values

23. Accredited to Michael Sahota & Olaf Lewitz

24. Manifesto for Agile Software
Development
We are uncovering better ways of developing software
by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes
and tools Working software over comprehensive
documentation Customer collaboration over
contract negotiation Responding to change over
following a plan
That is, while there is value in the items on the right, we

25. Select Team Core Values
• Select Personal Core Values
– Use Page of Core Values (feel free to add additional ones)
– Select 5 that you feel you care about the most; that you
feel you exhibit; write each one on a sticky
– Rank these in order of importance to you
– Take the top 3 and post on the wall
• Since the Team’s Identity& Values are the Sum of the
Set of It’s People
– Affinity analysis to cluster the top 4-6 across everyone
– First of 5 for commitment to these
• Generate value statements from these (time
permitting)

26. Establish Working Agreements
• Write behaviors & actions that are important to
you for good working relationships, be specific
• Keep in mind the team’s core values and what
will help the team avoid problems
• Confirmation/refinement that these will work