Headcount misleads when staff are part-time or detailed elsewhere. Convert everyone to available person-days, then apply past velocity to set a realistic sprint commitment.
Calculate available person-days, convert them to points with real velocity, then commit. A five-step method and worked example for government agile teams.
Government budgets, dates, and headcount are fixed. Here is a five-step way to calculate real sprint capacity before you commit, with a worked example.
What sprint planning looks like when velocity, allocation, and days off sit on one Jira screen: a six-step day with a worked capacity example.
How to see who is working on what across sprints: a four-step framework with a worked capacity example for government teams.
A four-stage, 12-month agile maturity roadmap for government teams, built around knowing real sprint capacity before you commit.
Count the days left before a hard date, subtract holidays, leave and allocations per sprint, and compare forecast capacity to scope owed. A worked example.
How to justify a sprint planning tool to government procurement: baseline your sprint miss from Jira, convert it to staff time, and propose a bounded 90-day pilot.
How many stories should a government team refine? Work backward from capacity: available days, past velocity, and a two-sprint ready target, with a worked example.
Five sprint planning anti-patterns in government agile, from deadline-driven commitments to headcount math, with a worked capacity example and fixes.
© 2026 — Divim, Inc. Digital Visual Management Systems and Consulting, Inc.