The Compliance Case for Documented Sprint Capacity Decisions (Part 3)
A written sprint capacity record turns ‘why did we commit to that?’ into a two-minute answer. Five items to capture each sprint, with a worked example.
A written sprint capacity record turns ‘why did we commit to that?’ into a two-minute answer. Five items to capture each sprint, with a worked example.
What should a Scrum team do with unfinished work at the end of a sprint? Return it to the backlog, re-check the sprint goal, and plan the next sprint on real capacity.
How often should you update a release plan? Re-forecast every sprint, review scope at milestones, and re-baseline only when the goal changes.
How long should sprint planning take? Up to 8 hours for a one-month sprint, usually less for shorter sprints. Here is how to keep it inside the timebox.
Fixed go-live date, shrinking team? Compare required pace to real sprint capacity early, then decide on scope, staffing, or schedule with a clear record.
How to total each person’s program commitments against available sprint hours, rebalance anything over 100%, and record the decision before you commit.
Estimate at three levels: ranges for epics, points for stories, hours for subtasks. Then check totals against real sprint capacity before promising a date.
Retire the capacity spreadsheet: a five-step path to keep availability, days off, allocation, and velocity next to the Jira backlog, with a worked example.
How to run a release planning meeting: who attends, the inputs to bring, a six-step agenda, and the outputs that keep the release date honest after the meeting ends.
Sprint planning with AI agents on the team: how to handle capacity, estimates and the sprint goal when coding agents take Jira tickets, and why human review becomes the constraint.
© 2026 — Divim, Inc. Digital Visual Management Systems and Consulting, Inc.