Gaining speed
summary
Reorganized into cross-functional opportunity teams that own features end-to-end and stop passing work through handoffs, the group cuts time-to-value and reports twice the speed of delivering user-facing increments. Practices include backlog refinements at least once per sprint that end with actions (research, prototypes, tests), voting impact maps for prioritization, and continuous discovery every sprint. Technical enablers: frequent web deploys, two-week mobile releases, automated tests and CI to enable small production slices delivered in days.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:06Team collaboration fence
- 3:53Full-stack feature teams
- 5:17Grooming beyond stories
- 7:24Refinements with user stories
- 9:08Shortening time to value
- 12:44Velocity isn’t the goal
- 13:48Journey to speed and agility
related talks
40mDeveloping at Cruise Speed
34mThinking more product: Moving from Scrum to dual-track Agile
10mI am done -
52mSmall Steps Are the Fastest Way Forward: Life Beyond Agile & Scrum
45mSoftware delivery with skills-based, self organising teams
23mA little less testing, a little more quality
46mWhen Rotating Teams as a Tactic to Shorten Lead Time Turned Out to Be LeSS Mob Programming
20mBuilding High-Productivity Teams Focused on Outcomes: Team Design and Collaboration Case Studies