2 posts tagged with "retrospective"

Sprint 47, 8-person team. The standard retro narrative would be: "Velocity dropped 20%, lots of bug fires, we'll prioritize better next sprint." Same vibe as Sprint 46. Same vibe as Sprint 45. Now add one number to the same retro: total sprint cost was $32,800, of which $11,600 (35%) went to bug-fix tickets versus $14,200 (43%) to features. The team's rolling-average bug share is 18%. That single line, "we doubled our usual bug spend this sprint," moved the team from "we'll do better" to "Sprint 48's first three days are bug-prevention only, full stop."

This article shows how to wire one financial number into a 30-minute retro so it produces decisions, not vibes.

The average engineering retro runs 60 minutes, produces five sticky notes, and ships zero action items into the next sprint. The Scrum Alliance's 2023 practitioner survey put "retros feel performative" as the #1 complaint from senior engineers. That's not a meeting problem. It's a measurement problem. Teams debate feelings because nobody pulled the data before the call.

This article gives you a 30-minute retrospective that opens with numbers, ends with named owners, and works on any team between 5 and 25 engineers.