One of the most common questions asked of any engineering team is "when will feature X be done?" Traditional point-based estimation is notoriously unreliable. Monte Carlo simulation offers a statistically rigorous alternative: instead of a single estimate, it gives you a probability distribution of completion dates based on your team's real historical performance.
What Is Monte Carlo Simulation?
Monte Carlo simulation runs thousands of randomized scenarios using your team's actual sprint-over-sprint throughput data. Each scenario randomly samples from your historical delivery rates to simulate how long it might take to complete a backlog of N items. The result is a probability distribution: "there is a 50% chance we finish by March 15, an 85% chance by April 2, and a 95% chance by April 20."
Why Not Just Average Velocity?
Averaging velocity produces a single-point estimate that has no probability attached to it. It ignores the natural variability in your team's delivery. If your velocity ranges from 30 to 60 points per sprint, using the average of 45 gives you a 50% chance of being right — a coin flip. Monte Carlo makes that uncertainty explicit and lets stakeholders choose their risk tolerance.
How Agile Analytics Runs the Simulation
Agile Analytics uses your completed sprint data from Azure DevOps to power the simulation:
- It samples from the distribution of your past sprint throughputs (completed items or story points)
- It runs 10,000 simulated sprints for each scenario
- It plots the cumulative probability of completion by date
- It highlights the 50th, 85th, and 95th percentile dates on the chart
How to Use the Forecast
The Monte Carlo dashboard in Agile Analytics asks you three questions: How many items remain in scope? How many sprints of historical data should be used? What is the target completion date? From these inputs it produces both a "how many sprints" forecast and a "by what date" forecast.
Choosing Your Confidence Level
For internal planning, the 50th percentile (median) is a reasonable target — you're as likely to finish early as late. For commitments to external stakeholders, use the 85th percentile. For contractual deadlines or regulatory milestones, use the 95th percentile.
Scope Sensitivity
Agile Analytics also shows how the forecast changes if scope grows by 10%, 20%, or 30%. This is invaluable for conversations about cutting scope to hit a deadline vs. moving the date.
Communicating Forecasts to Stakeholders
One of the biggest benefits of Monte Carlo forecasting is that it changes the conversation. Instead of defending a single estimate, you can say: "Based on our last 6 sprints, there is an 85% probability we will complete this by April 2. If you need 95% confidence, the date is April 20." This is honest, data-driven, and far more useful than a single-point guess.
Tips for More Accurate Forecasts
- Use at least 6 sprints of history — fewer sprints produce wider uncertainty bands
- Keep your backlog items roughly similar in size for more consistent throughput sampling
- Re-run the forecast each sprint as scope and throughput evolve
- Use item count (not story points) for Monte Carlo — throughput in items is more stable than velocity in points
- Review the forecast in sprint planning and retrospectives to build shared understanding of delivery uncertainty