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.
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.
What a Healthy Sprint Looks Like: Metrics Government PMOs Should Track
The five sprint metrics government PMOs should track to know a sprint is healthy: say-do ratio, velocity stability, commitment-to-capacity, scope churn, and carryover.
Story Points or Hours? Choosing an Estimation Model for Public-Sector Teams
Story points or hours? A practical framework for choosing an estimation model for government agile teams, with a worked capacity example.
How Days-Off Planning Prevents Sprint Failure
Government sprint commitments break when holidays, PTO, and training aren’t subtracted from capacity first. A 5-step framework plus a worked example.
Onboarding a Government Team to Agile: The First Five Sprints
A five-sprint framework for onboarding a new government agile team: plan by capacity first, then blend in velocity before reporting predictability.
The Compliance Case for Documented Sprint Capacity Decisions
Why documented sprint capacity decisions protect government PMOs under review — and how to build an audit-ready record inside Jira.
Building Predictable Delivery for Fixed-Deadline Government Programs
Government deadlines rarely move. Here’s how to reverse-plan sprints against real velocity and capacity, not headcount, so risk surfaces early.