Building and Growing an Agile Team
summary
A login and registration squad called Lars assembles from 12 people, consolidates scattered JIRA/Trello/Excel backlogs and sees a 130% backlog jump that forces prioritisation by value; work splits into commodity and spike streams, the team halves into two 6‑person pods and stabilises throughput in ~8 weeks. Practices: Kanban + Scrum language, DDD, Theory of Constraints, paired programming, bootcamps and war games. Outcomes: pipeline throughput +30%, visible work +230%, defects −30%, cycle time cut from ~7 days down to 2 days, acceptance into service from 2 hours to 12 minutes.
AI-written summary · about
chapters (21)
- 0:00Building and Growing an Agile Team
- 1:51Be the best login squad thingy
- 2:12Be maximum DevOp!
- 2:30Do Nothing
- 7:10130% product backlog items
- 12:21culture is the ultimate anti-fragility pattern
- 16:29that'll be between
- 17:57Make the Invisible Visible
- 19:23analysis
- 20:30Don't bring your title to the team, bring your skills and your self
- 21:52Everybody
- 22:427 Days Cycle Time
- 23:00Ignore the vanity metrics. Go deeper.
- 24:54How do you make all this stick?
- 27:022 Day Cycle Time
- 27:24the organisation is the impediment
- 29:372 hours Acceptance into Service
- 31:0712 minutes Acceptance into Service
- 32:51sustainably reducing the lead time to business impact
- 33:17Be the most agile-ist squad
- 33:42Don't copy us
related talks
18mAgile leadership and technical mastery, a harmonious alliance
47mBumpy 12 Months Road to Transform Team of Mercenaries Into Product Minded Team
15mAdvanced Scrum techniques for optimal delivery
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell
52mToo many cooks! Supporting augmented teams without getting salty
32mPanel discussion: The journey to building effective engineering teams
01h 04mIs Agile Still the Answer? Lessons from Real World Agility
51mMastering Trade-offs for Scaled Agile Success