Focus factor in Scrum converts available person-days into a realistic sprint commitment. How to calculate it, where it misleads, and how to replace it with per-person capacity in Jira.
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.
A step-by-step method for subtracting holidays, leave, and mandatory training from sprint capacity before your government team commits to a sprint goal.
Cross-team dependencies in release planning are the slips that show up late because no single team owns them. Here is how to make them visible, priced, and re-checked.
A Monte Carlo release forecast replaces one optimistic date with a distribution of dates and a confidence level. Here is how it works, what it needs from your Jira data, and where it breaks.
The sprint planning capacity spreadsheet keeps starting arguments in Agile forums. Here is what it is genuinely good at, where it quietly lies to you, and how to keep the useful half.
Government agile teams often mistake last sprint’s velocity for next sprint’s capacity. Here’s the 5-step framework and worked example to get it right.
How government PMs calculate real sprint capacity when staff are part-time, detailed to other programs, or capped by contractor hours — with a worked example.
© 2026 — Divim, Inc. Digital Visual Management Systems and Consulting, Inc.