0
A PERT chart puts a probability on a finish date once, from the network known on planning day. Keep that probability live against the committed date, in days.
0
Estimate at three levels: ranges for epics, points for stories, hours for subtasks. Then check totals against real sprint capacity before promising a date.
0
The critical path method finds the longest chain of dependent work once. After the vote the chain changes. See what that costs the committed date, in days.
0
Retire the capacity spreadsheet: a five-step path to keep availability, days off, allocation, and velocity next to the Jira backlog, with a worked example.
0
A scope statement records what is in and out of a release, once. It never says what an item crossing that line costs your committed release date. How to read that gap, in days, in Jira.
0
How to run a release planning meeting: who attends, the inputs to bring, a six-step agenda, and the outputs that keep the release date honest after the meeting ends.
0
Sprint planning with AI agents on the team: how to handle capacity, estimates and the sprint goal when coding agents take Jira tickets, and why human review becomes the constraint.
0
Focus factor in Scrum converts available person-days into a realistic sprint commitment. How to calculate it, where it misleads, and how to replace it with per-person capacity in Jira.
0
A one-number way for government PMs to report sprint predictability to non-technical leadership, with a worked example and a steering-committee-ready framework.
0
A risk register ranks risks by likelihood and impact. It never says how many days a materialising risk costs your committed release date. How to add that number to every review.