iziRisk Projects · Level 1 · agile Flow
Hover helpForecast an agile delivery the way flow actually behaves: a backlog drained by a throughput that varies sprint to sprint, while the scope itself grows. Throughput is resampled from the team’s own history — no velocity average, no story-point estimate required.
Settings
This sends content to an AI model (Anthropic). What is sent and how it is handled →
Delivery streams
| Name | Backlog | Throughput per period | Ramp | Starts after | Cost / period | Fixed cost | |
|---|---|---|---|---|---|---|---|
Past throughput, comma-separated — the team’s own record, holidays and all.
Scope growth
Impediments & opportunities
| Name | Type | Frequency | Impact | |
|---|---|---|---|---|
Joint confidence — the date AND budget to commit to
Finish and cost move together, so committing to the P80 of each does not deliver both 80% of the time. iziRisk raises both targets over this run’s joint distribution until they are met TOGETHER at the confidence you pick.
AI reports
Four AI agents write a report from this forecast, each for a different reader, as PDF (with the charts) or PowerPoint. Run the forecast first; turn on sensitivity by exclusion and set the joint confidence level for more complete reports.
This sends content to an AI model (Anthropic). What is sent and how it is handled →
Run a forecast first to write a report.
For the delivery lead, the agile coach and the sponsor’s analyst: every figure, which stream sets the date, the drivers, the risk horizon and the recommendations.
For the PMO, the portfolio board, the steering committee and internal audit: assumptions, evidence, contingency and numbered findings.
For the sponsor and management: the date and budget to promise, what drives them and what to do, in two minutes.
For anyone with a stake in the delivery: when it will be done and what could make it later, in everyday words.