Uncategorized

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.

A one-number way for government PMs to report sprint predictability to non-technical leadership, with a worked example and a steering-committee-ready framework.

A five-check checklist for government scrum masters: net capacity, a ready backlog, a plain-language sprint goal, a last-sprint review, and a documented allocation record.

How large government agencies roll up capacity across multiple agile teams to catch overcommitment before a Program Increment starts.