Forecast from weekly throughput
Monte Carlo can now forecast from weekly throughput, for teams that do not run sprints. Under Forecast from, choose Weeks instead of Sprints. Teams that use sprints see the same forecast as before unless they choose Weeks, because Sprints stays the default.
- Pick a History of the last 8, 12 or 26 complete weeks, then run the forecast.
- Weeks run Monday to Sunday (UTC), and the current week is not counted.
- It counts every finished item in the team’s area, including items that were never in a sprint, using the team’s Workflow Mapping.
- Items that were reopened or removed since are left out, and the Item Types filter applies.
- A note under the result says which weeks were used and anything that was left out. It also tells you when the early weeks were quiet.
If you have no past sprints
When a team has no past sprints, Monte Carlo now offers a Forecast from weekly throughput button, so you can get a forecast without setting up sprints first.
When there is no forecast
If more than 1,000 items finished in the window you chose, there is no forecast. Choose a shorter History and run it again. The Forecast Scorecard is sprint-only, so it is hidden when you forecast from Weeks.
Epic burn-up in Epic Analytics
Open an Epic that has Features in Epic Analytics to see its burn-up: stories done over time, against today’s total. The expander on an Epic row now shows the burn-up above its Features.
- The dashed lines end at the same 50% and 85% landing dates as the table.
- The flat line is today’s total, not a history of how the scope changed.
- Done stories that have no close date in Azure DevOps are not plotted, so the chart can show fewer done stories than the Stories column. The chart says how many.
What you need to do
Nothing is required. Azure DevOps updates the extension automatically, and teams that use sprints see no change unless they choose Weeks. If a figure looks different after the update, use Ask Henry in the top bar.
Related: Service status