Battlefield Agility: Think Beyond Scrum
summary
Scrum-like timeboxes give way to a battlefield metaphor where a project commander prioritizes features, recon teams scope work, and small attack parties pair up to finish features; rule examples: no more than two tasks per person and at least two people per feature. Field data: adoption across 16 organizations and 22 platoons (~250 people) claims 25–30% faster time to market; one media client moves from about 3 feature releases per month to 35 after adoption. Short, iterative drills surface and fix blockers fast.
AI-written summary · about
chapters (10)
- 0:00Introduction and Scrum age
- 3:06Scrum limitations
- 6:16Interactive team simulation
- 12:05Simulation debrief
- 15:36Iterative simulation
- 23:22Battlefield agility concept
- 29:52Roles in battlefield agility
- 34:03Battlefield agility rules
- 39:17Case study and results
- 42:20Q&A and closing
related talks
35mBuilding and Growing an Agile Team
47mAgile experience in changing environments and the challenges faced
41mSabotaging an Agile Transformation
15mAdvanced Scrum techniques for optimal delivery
49mHow Agile broke peace in steady Casino Business
30mHerding Tigers - Software Development and the Art of War
51mMastering Trade-offs for Scaled Agile Success
51mSabotaging a Transformation
