Uncategorized

Compute real team capacity — leave, details, allocations — before committing a sprint. A 60-minute agenda and worked example for government agile teams.

Fixed budgets, fiscal-year deadlines, and shrinking teams make capacity-based sprint planning a survival skill for government agile teams. Here’s the math.

An hour-by-hour walkthrough of capacity-aware sprint planning for government teams: baseline math, a worked example, and a defensible commitment.

Record allocation and days off in the sprint plan inside Jira, so “who’s on this?” is answered in one screen — not a spreadsheet reconciliation.

A quarter-by-quarter 12-month roadmap for scaling agile maturity in government: baseline, capacity-based commitments, multi-team rollout, forecasting.

How government agile teams plan sprint capacity across period-of-performance end dates, option years, and the September 30 fiscal-year cutoff.

How to get a sprint planning tool through government procurement: price the status quo, fit the acquisition path, and answer security questions upfront.

How public-sector teams refine their backlog against real capacity — allocations, leave, and holidays — so ready work actually fits the team.

Five sprint planning anti-patterns that derail government agile teams — velocity quotas, ghost capacity, calendar blindness — and how to fix each.

Over-allocation quietly taxes government teams: context-switching, correlated slips, burnout. How to spot it, cost it, and fix it before sprint planning.