Sprint Planning

The no estimates vs story points fight misses the point: both are forecasting methods, and both fail without real capacity. Here’s how to settle it in Jira.

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? A practical framework for choosing an estimation model for government agile teams, with a worked capacity example.

A repeatable sprint planning checklist for government scrum masters — verify a refined backlog, real team capacity, and one clear goal before you commit.

A clear definition of ready keeps unrefined stories out of sprint planning so the meeting stays short and the commitment stays realistic. Here is how to build and enforce one.

Optimistic sprint plans built on headcount instead of real capacity quietly wreck government delivery. Here’s how to commit to work your team can actually finish.

The sprint planning mistakes that quietly wreck delivery — no goal, ignoring capacity, hidden dependencies, over-commitment — and a concrete fix for each.

The story points vs hours debate, settled practically: what each measures, where each breaks down, and how to combine relative sizing with real capacity in Jira.