0
The LinkedIn debate over whether to re-estimate carryover stories has two camps and one missing question: what is the number for? Here is how to decide, and how to keep carryover from silently eating next sprint’s capacity.
0
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.
0
SPI 0.87 says you’re behind plan — not when you’ll land. Translate earned value and schedule variance into a committed release date on a live 50/85/95% confidence band in Jira.
0
Points for sizing, person-days for capacity, connected by your team’s own ratio. A practical hybrid estimation model for government agile teams.
0
SAFe fixes the train’s departure date — so post-commitment erosion decides what’s on board instead. Keep the PI confidence vote live against a 50/85/95% band in Jira, and choose your scope in days, before the boundary chooses for you.
0
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.
0
A premortem surfaces how your release could fail — scope, dependencies, capacity. Give that judgment a pulse: track it live against the committed date.
0
A five-sprint onboarding plan for government teams new to agile: one planning habit per sprint, a worked capacity example, and a defensible record.
0
A change control board approves scope one small change at a time. Bring the live Monte Carlo confidence band into the meeting and price each approval in days — before the vote.
0
A capacity commitment you can’t reconstruct is a liability. How to build a sprint decision trail that survives turnover — with a worked example.