Uncategorized

When requirements change mid-sprint, run a capacity-checked swap, not a re-plan: size the new work, remove equal untouched points, and record the trade.

Government sprint planning burns time reconciling Jira, HR leave calendars, and staffing spreadsheets. Here’s how to collapse four inputs onto one screen.

Five metrics that show whether a government sprint was healthy — capacity utilization, say/do, scope change, carryover age, and allocation concentration.

Hybrid government teams break the usual capacity shortcuts. A four-step method — plus a worked example — for calculating real sprint capacity across telework, time zones, and split allocations.

Points for sizing, person-days for capacity, connected by your team’s own ratio. A practical hybrid estimation model for government agile teams.

A fresh worked example of days-off planning: Labor Day, Guard duty, and training deadlines turn 60 person-days into 40 — and how to commit accordingly.

A five-sprint onboarding plan for government teams new to agile: one planning habit per sprint, a worked capacity example, and a defensible record.

Fixed date, fewer people? Build predictability with days-off-adjusted commitments, a measured unplanned-work buffer, and a tracked say-do ratio.

Over-allocation is the quiet reason multi-program agencies miss dates. A five-step allocation map, a worked example, and a repeatable fix inside Jira.

How government teams split epics into sprint-sized stories and hour-level subtasks that fit real capacity — with a worked example and a 30-minute first step.