Incredible Agile Teams
summary
Thirty-plus scrum teams across medical imaging test practices like mob testing, which finds defects that solo testing misses, and regular pair programming to raise code readability and bus-factor resilience. Embedding one person in another team for 2–6 months creates trust that lets remote teams deliver hard fixes together; avoiding splitting a team across features produces a single-team focus that shipped the next priority earlier than planned. Regular learning sessions and rotating “fun” keep morale and knowledge sharing high.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 2:37What makes teams incredible
- 9:10Team balance and cross-functionality
- 13:25Connecting with external teams
- 16:36Building trust in distributed teams
- 18:20Why splitting teams fails
- 20:27Overcommitment and technical debt
- 22:33Building the right thing
- 25:42Creating resilient teams
- 29:13Nurturing respect and collaboration
- 32:05Culture of learning
- 33:47Boosting morale and spirit
- 37:40Improving team characteristics
- 38:45Stand-up chicken and appreciation
- 40:30Evolving nature of agile teams
- 41:38Q&A
related talks
48mSoftware Teaming: Onboarding, Remote Work, Productivity — Four Years in an Team's Life
35mBuilding and Growing an Agile Team
47mAgile experience in changing environments and the challenges faced
01h 04mAdvanced Software Teaming
50mMob Programming, A Whole Team Approach
18mAgile leadership and technical mastery, a harmonious alliance
01h 10mAgile Cross Team Collaboration How Tos
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell