Scaling Agile Maturity: A 12-Month Roadmap for Government Teams
A quarter-by-quarter 12-month roadmap for scaling agile maturity in government: baseline, capacity-based commitments, multi-team rollout, forecasting.
How to Plan Capacity Around Contract and Fiscal-Year Boundaries
How government agile teams plan sprint capacity across period-of-performance end dates, option years, and the September 30 fiscal-year cutoff.
Making the Business Case for Better Sprint Planning Tools to Procurement
How to get a sprint planning tool through government procurement: price the status quo, fit the acquisition path, and answer security questions upfront.
Capacity-Aware Backlog Refinement for Government Teams
How public-sector teams refine their backlog against real capacity — allocations, leave, and holidays — so ready work actually fits the team.
Sprint Planning Anti-Patterns in Public-Sector Agile (and Fixes)
Five sprint planning anti-patterns that derail government agile teams — velocity quotas, ghost capacity, calendar blindness — and how to fix each.
The Real Cost of an Over-Allocated Government Developer
Over-allocation quietly taxes government teams: context-switching, correlated slips, burnout. How to spot it, cost it, and fix it before sprint planning.
Forecasting the Next Quarter Using Past Velocity
Average velocity overpromises. Convert past sprints into a throughput rate, apply it to the person-days you’ll actually have, and forecast a defensible quarter.
How to Run Sprint Planning When Requirements Change Mid-Cycle
Requirements change mid-sprint in government, often non-negotiably. Reserve an intake buffer, swap one-for-one by capacity, and record every trade.
Reducing Context-Switching: Planning Capacity in One Tool
Government sprint planning spans four surfaces: backlog, capacity spreadsheet, leave calendar, PMO deck. Here’s what the switching actually costs — and how to collapse it to one screen.