Intense Recording: Ten Months of Development Close-Up — The Case of the Vanished Sprint Goal
summary
A ten-month case study following fortnightly Scrum sprints shows how 20+ sprint goals evolved from task-level items (e.g., “send an email”) into inspectable, outcome-focused goals with clear acceptance and inspection criteria. Practices introduced include backlog refinement driven by the sprint goal, choosing reviewers up front, using Daily Scrum as a replanning against the sprint goal, and adding mid-sprint goal inspections; outcomes were higher developer product awareness, better increment quality, and much faster operations (deploys ~3×/day and fixes in ~30 minutes).
AI-written summary · about
chapters (12)
- 0:00Introduction
- 4:20Sprint goal challenges
- 7:10First sprint goal improvements
- 9:39Uncheckable goal steps
- 11:27Refining goal checks
- 13:34Goal improvement summary
- 13:55Committing to goals
- 15:39Daily scrum planning
- 16:22Sprint goal inspection
- 17:28Effective sprint goals value
- 18:31Higher increment quality
- 20:38Key takeaways and Q&A
related talks
26mAgility Works Only If You Are Truly Agile...
15mAdvanced Scrum techniques for optimal delivery
49mBaking Boards: Tweak the Recipe for Agile Development
20mFour Months as a New Scrum Master — Escaping 'Running Scrum Events Without Feeling Any Impact'
20mFacing Our Organization's Philosophy with Scrum
35mTeam transformation to accelerate value delivery
35mCase Study: Seven Years of Agile
35mBuilding and Growing an Agile Team