0
Conway’s Law predicts where your dependencies will be before anyone writes a ticket. Why they still surface too late — and how to read the cost in days.
0
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.
0
An assumption log records what was true on planning day. Here’s how expired assumptions quietly move a committed release date, measured in days.
0
Government sprint planning burns time reconciling Jira, HR leave calendars, and staffing spreadsheets. Here’s how to collapse four inputs onto one screen.
0
The ninety-ninety rule says the last 10% takes another 90% of the schedule. Here’s why “almost done” hides erosion of a committed release date.
0
Five metrics that show whether a government sprint was healthy — capacity utilization, say/do, scope change, carryover age, and allocation concentration.
0
A hardening sprint is schedule buffer the confidence vote already priced. Here is what quietly spends it before the last iteration starts, and how to read what is left in days.
0
Escalation of commitment is why a feature nobody believes in still ships in the release. What makes agile teams especially vulnerable, and the four mechanics that make cutting scope a normal decision instead of an admission of failure.
0
A velocity forecast gives you one date. Three-point estimation gives you a range and the width of your own uncertainty — which is the number stakeholders actually need before they commit to a release.
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.