iziRisk Projects
Three levels, one model. Start at Level 1 by choosing how the work is actually delivered — as a network of dependent tasks, or as a backlog drained sprint by sprint. Levels 2 and 3 extend whichever you pick.
Level 1 — how the work gets delivered. Pick the one that matches your project.
Waterfall — schedule and cost
Will the plan hold? Turn a network of dependent tasks into finish-date and cost distributions — and see which tasks and risks drive them.
Waterfall — schedule and cost
For work planned as a network of dependent tasks with durations. Start from one of 101 worked example projects — or describe your own — and the AI asks the few questions it needs, then builds the probabilistic schedule and cost model for you. The native CPM + Monte Carlo engine runs it: finish-date and cost distributions, the task criticality index, sensitivity tornados (both rank-correlation and the causal by-exclusion one), probabilistic contingency, joint time-and-cost confidence, and a Gantt you can watch the simulation run across.
Agile — delivery flow
When will the backlog really be done? Forecast delivery from your team’s own throughput, with a scope that keeps growing.
Agile — delivery flow
For work that is not a task network: a backlog drained by a throughput that varies sprint to sprint, while the scope itself grows. Start from one of 12 worked delivery examples — or describe your own — and the AI asks what it needs, then builds the model: streams, throughput history, scope growth and impediments. Throughput is resampled from the team’s own history, so no velocity average and no story-point estimate is required. You can also import a Jira or Azure DevOps export and have it measured rather than guessed. Produces finish in sprints, a probabilistic burn-up, which stream sets the date, the service level and a Little’s Law check.
Level 2 — objectives, value and success
On time and on budget is not success. Measure the probability that the project delivers the value it was approved for — objective by objective, stakeholder by stakeholder.
Level 2 — objectives, value and success
Extends either Level 1 model from “will it finish on time and on budget” to “will it deliver the value it was approved for”, in PMBOK 8 terms. A canonical catalogue of 32 objectives with their targets, a KPI graph, gates for the objectives that cannot be traded away, the stakeholders who judge each one and their expectations. Produces the probability of project success, PVaR, the value index and whose expectations are most at risk — closing with an AI executive summary and a PDF report.
Level 3 — programmes and portfolio
Which projects in the portfolio are drifting — and how far can you trust the numbers? Track every project period by period across entities, with exceptions flagged.
Level 3 — programmes and portfolio
Lifts those same projects into a corporate control layer across entities. Five control registers, historic KPI tracking period by period, an objective heat map whose cells are simulated probabilities rather than a colour matrix, thresholds and exception reporting, aggregation that declares explicit bounds instead of multiplying probabilities, and a calibration reading that says whether your organisation’s forecast bands actually contain reality. It never re-simulates — it consolidates what the project models already produced.