0
A loose Definition of Done re-opens scope after the vote: undone work returns as rework and quietly erodes the committed date. See the drift in days in Jira.
0
Per-team math, shared specialists as constraints, and bottom-up roll-ups: how large agencies plan capacity across multiple agile teams, with a worked example.
0
The project management triangle — scope, capacity, time — is fixed by the confidence vote and bent by the weeks that follow. How to see each side move a committed release date, in days, in Jira.
0
A RAID log records risks, assumptions, issues and dependencies — as of the last edit. Why the R and the D go stale, and how to keep them live against a committed release date in Jira.
0
Overcommitted sprints corrupt velocity data and erode leadership trust. Five guard-rails to commit to what your government team can actually deliver.
0
How government teams plan sprints around federal holidays, use-or-lose leave, and mandatory training — a five-step method with a worked example.
0
Technical debt is a capacity change in slow motion — no calendar event, just throughput drifting down after the vote. How to see it move a committed release date in days, in Jira, and renegotiate before the slip.
0
Crashing vs fast tracking: what each schedule compression move really costs, and how to size the gap — in days, against a 50/85/95% confidence band — before you pick a rescue.
0
Velocity describes a roster that may no longer exist. How government teams hit by freezes and details should reset sprint commitments to real capacity.
0
Scrum of scrums works when it runs on a live dependency map instead of status theater. A working agenda, the anti-patterns — and how Jira teams keep it to 15 minutes.