0
A Monte Carlo release forecast replaces one optimistic date with a distribution of dates and a confidence level. Here is how it works, what it needs from your Jira data, and where it breaks.
0
The sprint planning capacity spreadsheet keeps starting arguments in Agile forums. Here is what it is genuinely good at, where it quietly lies to you, and how to keep the useful half.
0
Government agile teams often mistake last sprint’s velocity for next sprint’s capacity. Here’s the 5-step framework and worked example to get it right.
0
Three point estimation captures the team’s honest range once, at planning, then PERT collapses it to one number. How to keep that range live against a committed release date, in days, in Jira.
0
A work breakdown structure records what the work is, not what a change to it costs the committed release date. How to keep the decomposition priced, in days, in Jira.
0
Six months ago, two organisations signed the same sentence. It sits in section 4 of the statement of work, between […]
0
How government PMs calculate real sprint capacity when staff are part-time, detailed to other programs, or capped by contractor hours — with a worked example.
0
Every release has a document that predates the team. It might be called a project charter, a project brief or […]
0
How government PMOs and scrum masters can align sprint planning with real team capacity — net of leave, training, and details — before committing to a sprint goal.
0
A missed government sprint is a commitment that already traveled upward. Here’s how to plan real capacity, not headcount, before you commit.