Sprint close to next plan

Step by step

1. Close and roll over Scrum Master / Iteration Manager

   On the Sprint end date the Scrum Master flips Status: Active → Closed. The sprint-end-rollover workflow fires, finds every Issue in the closing Sprint with Status NOT IN (Done, Cancelled), and first freezes sprint outcomes for all committed, added and removed issues. It then applies project issue rollover rule: either nulls issue sprint (back to Backlog) or sets it to the next Future Sprint. The velocity-recompute job upserts the Sprint’s team velocity row with committed points (from sprint commitments), completed points (from immutable sprint outcomes recorded before rollover, using the agreed estimate unit), and Carryover; refreshes the trailing-3 average. The retrospective digest emails to Scrum Master + Project Lead. Scrum Master writes retrospective notes on the closed Sprint.

   • Freeze outcomes before moving current issue assignments
   • Updates Sprint outcomes, Sprint commitments, Issues

2. Review delivery signals Scrum Master / Iteration Manager

   Every role sees a scope-appropriate dashboard: Developer sees My Open Issues + the Active Sprint Board; Scrum Master sees Sprint Burndown + Velocity Trend + Stalled Issues + WIP Warnings; Project Lead sees Backlog Health + Release Progress + Epic Progress; QA sees Bugs Awaiting Verification + Bug SLA Attainment; Stakeholder sees Epic Roadmap + Release Forecast for assigned Projects; Reporter sees My Reported Issues; Admin sees Workflow + issue type health. The Sprint Velocity Report and Sprint Burndown drive the ceremonies; the Cycle Time / Lead Time and Throughput by Type reports drive process improvement; the Release Forecast and Epic Roadmap drive stakeholder communications.

   • Separate missing evidence and scope changes from completed work
   • Updates Team velocity, Burndowns, Epic progress

3. Prepare next commitment Project Lead / Product Owner

   On the Backlog’s grooming cadence, the Product Owner opens the Project Backlog view, ranks Issues via backlog rank, sets Estimate on issue type requires estimate = true rows, assigns parent epic and tentative fix version. For Sprint planning, the Scrum Master opens a Future Sprints row (with Goal, start date, end date, Board, capacity points defaulted from team velocity trailing three average), pulls top-ranked Backlog Issues into the Sprint by setting issue sprint to the Future Sprint, until the committed estimate matches capacity.

   • Use history as a planning aid in the same unit
   • Updates Sprints, Backlogs

Scrum Master / Iteration Manager

Runs the Sprint cadence and the Board. Owns ceremonies (planning, standup, review, retro), WIP discipline, and the burndown.

Project Lead / Product Owner

Owns the Project end-to-end — backlog priority, release planning, estimate overrides, scope decisions. The DRI for the product the Project ships.