One Story, One Sprint

A single backlog item's trip through one Scrum sprint touches every event in the framework — and counting the sprint's fixed coordination shows the process's overhead is arithmetic, not mystery.

A team of six takes a two-week sprint — ten working days. Sprint planning moves one story from the product backlog into the sprint backlog: "riders see real-time bus positions." Days one through ten each open with a daily scrum, fifteen minutes, same time and place: progress inspected, sprint objectives adapted when a map-tile problem surfaces on day four. Count the coordination: ten daily scrums at fifteen minutes is one hundred fifty minutes — two and a half hours of standing coordination per sprint, purchased deliberately for early detection like day four's. Day ten closes the loop twice: the sprint review demonstrates working bus positions to stakeholders, who ask for accuracy indicators — feedback captured as a new backlog item, exactly where feedback goes. Then the retrospective, product set aside: the map-tile surprise cost two days, so the team proposes a spike task next sprint for unknowns. One story entered; a shippable increment, one new backlog item, and one process improvement exited. Every event did its one named job.