Sprints and commitments

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.

Scrum Master flips the Sprint Status: Future → Active. The sprint-start-snapshot workflow fires via the configured record event, walks every Issues row attached to the Sprint, bulk-inserts one sprint commitments row per Issue freezing the committed estimate, committed status, and committed assignee snapshot at sprint-start, stamps sprint started at, and emails the kickoff digest with committed scope to the Scrum Master + Project Lead. The Sprint board becomes the squad’s daily surface.

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.

An unfinished issue can move to the next sprint while the closed sprint still needs an accurate record of what happened. Freeze the closure outcome before moving the current issue. The starting commitment retains its estimate and assignee; the closure observation retains its actual state and accepted estimate at the boundary.

Added and removed work appears separately from the original commitment. Carryover counts original commitment that remains unfinished; completing newly added work cannot cancel out an unfinished commitment or make carryover negative. The sprint keeps its starting estimate unit even if a future project configuration changes. Cancelling a large issue must not look like completing it, and a later estimate change must not improve last month’s velocity. A repeated close command returns the same frozen outcomes and rollover destinations.

The trailing velocity average is a planning aid in the project’s chosen unit. A team with little history does not receive a fabricated capacity promise. Use the suggested value alongside holidays, team changes and known constraints, then retain the sprint goal and accepted scope for the retrospective.

• Sprint Calendar. Open the current records for this module within your assigned role and permitted scope.