Planning Sprints Around Federal Holidays, PTO, and Training Days
A step-by-step method for subtracting holidays, leave, and mandatory training from sprint capacity before your government team commits to a sprint goal.
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.
How government PMOs and scrum masters can align sprint planning with real team capacity — net of leave, training, and details — before committing to a sprint goal.
A missed government sprint is a commitment that already traveled upward. Here’s how to plan real capacity, not headcount, before you commit.
What a capacity-aware sprint planning day looks like hour by hour for a government team — with a worked example showing why 60 person-days on paper is really 39.
Cross-sprint visibility means naming who is on what before the sprint starts. A five-step per-person capacity method for public-sector teams, with a worked example.
© 2026 — Divim, Inc. Digital Visual Management Systems and Consulting, Inc.