Brian Watson Brian is an Agile and Product coach for VersionOne. He has over 16 years of experience providing Project Management, Business Analysis, and Agile coaching on small to enterprise level projects in web and software development, process improvement, communications, healthcare education, marketing, aeronautics, mergers and consolidations, long distance telecom, wireless, distribution, and government industries. Since 2005, Brian has been an Agile transformation coach helping consulting software development factories, insurance, manufacturing, workers compensation, and government agencies achieve the benefits of agile. In his spare time Brian enjoys golfing and craft beer.

1. Building Agile Teams
Brian Watson, PMI-ACP, CSM, PSM1
Product and Agile Coach
@bdub1pmp
brian@versionone.com

2. © 2011 VersionOne 2
Team Building

3. © 2011 VersionOne 3
Teams…

4. © 2011 VersionOne 4
Analogy
• Growing Agile teams is like learning to
fly a plane….

5. © 2011 VersionOne 5
Formal Training – Ground School
• You can read a book or take a class to learn
the “major” theoretical elements
– Takeoff/landing, Stalls, Weather, etc.
• You might even be able to pass a written
test after class
• However, are you ready to fly the plane?

6. © 2011 VersionOne 6
Formal Scrum/Agile Training
• Critical foundational element to starting
down the path to agile
• Theoretical concepts
• Review key ceremonies
– “Guard Rails”
• Certified Scrum Master (CSM) or
Professional Scrum Master (PSM)

7. © 2011 VersionOne 7
Flight Training
• With formal knowledge in hand, the student
must fly with an instructor
• Time in the pilot seat will allow the student
to encounter the numerous situations
formal training cannot cover
• There is no substitute for practical
experience…with a guiding hand
• Converts theoretical knowledge into skill

8. © 2011 VersionOne 8
Growing the Team
• Accomplished through pairing the major
skills sets (Dev, BA, QA, PM) with
experienced people
• Allows the experienced people guide the
new team through how to apply their
theoretical knowledge
• A Transition Coach assists with guiding the
entire process
– Provide “guard rails” to the process
– Product owner, management, other teams

9. © 2011 VersionOne 9
Agile Team Schematic
Product Owner
New Dev
Experienced
Dev
Experienced
SM
New SM
Experienced
BA
New BA
Experienced
QA
New QA
Management
Transition
Coach
Formal
Training
Experienced
UX
New UX
Pairing
Pairing
Pairing
Pairing
Pairing

10. © 2011 VersionOne 10
Flying Solo
• Once the student’s skill level has caught up
to their desire and confidence, they can fly
solo
• This occurs after many hours of guidance
from the instructor
• Each person will learn something new when
they fly solo
– Reinforcing and existing concept
– New situation

11. © 2011 VersionOne 11
Coding (Flying) Solo
• Once the team has worked through 3-5
sprints, they should be ready to fly solo
• This will allow the team to grow their skills
in new situations by applying concepts
learned in training and pairing
• Teams will make mistakes in this phase
– Mistakes are part of the learning process
– Mistakes are OK

12. © 2011 VersionOne 12
Sharing the Passion
• Flying solo will allow the knowledge/skill of
the pilot to exceed their level of desire and
passion for flying
• When this occurs, they can begin to share
their knowledge with others
– The cycle begins anew…

13. © 2011 VersionOne 13
Agile Team Progression
Pre-CSM
Training
Post-CSM
Training
Pairing Flying
Solo
Sharing
Knowledge
Skill
Confidence/Desire

14. © 2011 VersionOne 14
Sharing
• When team members are ready, they can be
transferred to a new team to guide and lead
their transition
– Option 1: Remove members of original team
– Option 2: Pairing
• Set expectations - Velocity on the original
team will be reduced

15. © 2011 VersionOne 15
Cost/Benefit Analysis

16. © 2011 VersionOne 16
Infection Rates
• 10% of a team will infect the other 90%
– It is critical that the 10% is positive,
knowledgeable and evangelizing agile concepts
• When removing resources from a productive
team to create a new one, you do not want
to remove more than 10%

17. © 2011 VersionOne 17
Management

18. © 2011 VersionOne 18
Management Support
• Learning is a process, mistakes will happen
• Management needs to transform along with the
team
Command/Control
“Approver”
Work Assignor
Coach
Mentor
Remover of
Roadblocks
Transition
Beware the “middle manager conundrum”

19. © 2011 VersionOne 19
Team Spaces
• Functional, not fancy
– Elbow room for pairing and collaboration
– Dual monitors
• Stimulate teamwork and communication
– Remove walls
– Central location for card wall and stand-ups
• Do not break the bank

20. © 2011 VersionOne 20
Empowerment
• The team should be able to say “no”
• Encourage the team to take risks
– Within guard rails

21. © 2011 VersionOne 21
Culture
• Embrace the new culture
• Work to convert pessimists
– Lack of understanding
– Change
• Not everyone is “cut out” for agile

22. © 2011 VersionOne 22
Organization
• Think local…act global
• Work to limit roadblocks this will cause the team
frustrations

23. © 2011 VersionOne 23
Continuity
• Only a small part of overall team success is
“Agile”
• Teams form a bond
• Teams must be kept together
– Tuckman’s “law” is undefeated and untied…

24. © 2011 VersionOne 24
Psychology

25. © 2011 VersionOne 25
Satir Model

26. © 2011 VersionOne 26

27. © 2011 VersionOne 27

28. © 2011 VersionOne 28

29. © 2011 VersionOne 29
Motivation

30. © 2011 VersionOne 30
Wrap-up
• Avoid “shock and awe”
– Go slow and low…
• Set expectations
– Mistakes
– Not an overnight transformation
• Embrace psychological roadblocks of humans
Allow the teams to evolve into
high performing, motivated groups

31. © 2011 VersionOne 31
Questions

32. Building Agile Teams
Brian Watson, PMI-ACP, CSM, PSM1
Product and Agile Coach
brian@versionone.com
@bdub1pmp
http://www.linkedin.com/in/bdub1pmp