The Fix Sprint rebuilds one confirmed workflow problem.

This step starts only after the bottleneck is clear enough to scope. The sprint repairs one workflow, not every adjacent issue discovered around it.

Fix Sprint implementation surface

Reserved for a charter excerpt, redesign map, or implementation asset that shows what changes inside the sprint.

The sprint turns diagnosis into operating clarity.

The active workflow, output, boundary, owner, and definition of done are set before implementation begins.

Create a Sprint Charter

Redesign the workflow sequence

Build the core asset or system

Enable the team and hand over the finished workflow

A usable workflow, not a deck.

A defined workflow with visible ownership

The practical asset or system needed to run it

Clear rules for handoffs, reviews, or follow-up

A handover with what to watch during real-world use

The scope stays narrow on purpose.

Adjacent issues are captured, but they do not quietly expand the active sprint.

Adjacent issues are captured, but they do not quietly expand the active sprint.

  • One product line per sprint
  • One workflow problem per sprint
  • New requests require a swap, not an addition

Inspect the sprint, then decide whether it fits.

When the Bottleneck Map shows a clear fix, the next move is a fixed-scope sprint with clear boundaries.