0
Story points or hours? A practical framework for choosing an estimation model for government agile teams, with a worked capacity example.
0
Government sprint commitments break when holidays, PTO, and training aren’t subtracted from capacity first. A 5-step framework plus a worked example.
0
A five-sprint framework for onboarding a new government agile team: plan by capacity first, then blend in velocity before reporting predictability.
0
Every fist of five ends the same way. Fingers go up around the room, someone calls out the average, it […]
0
Why documented sprint capacity decisions protect government PMOs under review — and how to build an audit-ready record inside Jira.
0
Three small tickets. That’s usually how it starts. A support fix gets pulled into the release because “it’s basically done […]
0
Government deadlines rarely move. Here’s how to reverse-plan sprints against real velocity and capacity, not headcount, so risk surfaces early.
0
Sprint dependencies aren’t one risk — they’re five: sequential, resource, cross-team, external, and decision. Here’s how to catch each before planning.
0
A real release plan needs three things: an estimated backlog, real velocity, and agreed conditions of satisfaction. Here’s what breaks when one is missing.
0
One backlog refinement question — could a developer start this tomorrow? — surfaces missing acceptance criteria and dependencies before sprint planning.