Sprints, Rebuilt Around One Goal

Details

A sprint is now a simple thing: a named stretch of work with one goal you agree together. Your team lead can open one when the work is worth naming, delegate it and run it on its own schedule, keep it pointed at the outcome, and close it with a written account of what shipped and what did not. That last part is the reason to bother with sprints at all. A stretch of work that closes with an honest review tells you something a rolling task list never does: whether the goal was the right one, and whether a week of work actually moved it. Sprints stay optional, deliberately. Plenty of good weeks are just a board worked in order, a team with no sprint runs its board exactly as before, and your team will not push you into one you did not ask for. Once a week, if there is genuinely something to decide, your lead raises it with you: what the next stretch should aim at, or how the last one went. Goals are editable again, so a sprint can be sharpened mid-week instead of staying wrong until it ends, and the dashboard now shows what is actually running rather than a stale picture of it.

What changed

• Set and sharpen a sprint goal at any time
• Start a sprint only when the work calls for one
• Close with a written look back at what shipped and what did not
• A weekly check-in on what the next stretch should aim at
• No sprint means a board worked in order, exactly as before