Why Sprint Capacity Planning Matters More in Government Than Anywhere Else
A missed government sprint is a commitment that already traveled upward. Here’s how to plan real capacity, not headcount, before you commit.
A Day in the Life: Sprint Planning With Capacity on One Screen
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.
Deployment Frequency: How to Measure It and What Good Looks Like
Deployment frequency is the DORA throughput key that is easiest to calculate and easiest to misreport. Here is what counts as a deployment, what the benchmarks actually say after DORA’s 2025 reset, and how to measure it when your delivery record lives in Jira.
Who’s Working on What Across Sprints? A Visibility Playbook for Government Teams
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.
Scaling Agile Maturity: A 12-Month Roadmap for Government Teams
A four-quarter roadmap that takes a government team from running sprints to defensible, predictable delivery — measure, commit on capacity, report upward, then scale.
How to Plan Capacity Around Contract and Fiscal-Year Boundaries: A State and Local Playbook
A boundary ledger, backward planning, and honest overlap math: how state and local agile teams plan sprint capacity across June 30 and vendor transitions.
Making the Business Case for Better Sprint Planning Tools to Procurement
How government delivery teams get a Jira sprint planning app approved: price the status quo in hours, pick the acquisition path first, and scope the security claim precisely.
Capacity-Aware Backlog Refinement for Government Agile Teams
Refine your backlog against real available capacity — not headcount. A five-step method, a worked example, and a readiness check for public-sector agile teams.
Sprint Planning Anti-Patterns in Public-Sector Agile: Carryover, Heroes, and the Support Tax
Five sprint planning anti-patterns that derail government agile teams — invisible carryover, hero buffers, and the unbudgeted support tax — and how to fix each.
Change Failure Rate: How to Measure It and What Counts as Good
Change failure rate is the share of deployments that cause a production failure needing a hotfix or rollback. The formula, the 2025 benchmark shift to 0-2%, and how to measure it when your delivery record lives in Jira.