The Scaled Agile Framework recognises the importance of data-based feedback loops and SenseAdapt already provides most of the reports that you will need, across PI, Epics and teams, straight out of VSTS.

This is better than the standard VSTS reporting in a number of ways:

  • You can forecast the likely completion dates or the scope that will be achieved by a date
  • Users create the reports once.. and share widely with stakeholders for real-time transparency
  • Anyone can take action directly from the visual, click through to the underlying Work Items and edit them

SAFe is very clear about the importance of an empirical approach to project oversight and measuring progress.

“Metrics are agreed-upon measures used to evaluate how well the organization is progressing toward the portfolio, large solution, program, and team’s business and technical objectives. Thanks to its work physics, timeboxes, and fast feedback, Agile is inherently more measurable than its proxy-based predecessor, the waterfall process.”

There is more on the SAFe metrics at

Potentially Deliverable Scope for a PI

The end-dates of a PI end-dates is fixed, and so the following chart shows the stories at risk of not being completed.

Using the historical throughput rates of the teams AND scope changes it forecasts the ‘probable’ and ‘possible’ lines on the backlog – at a story level.

This helps to focus stakeholders on the functionality that they may not get, and then to have the difficult conversations that are often avoided.

These real time insights also mean that the conversations happen earlier – when there are more options to affect the outcome of the PI.

Burn-up for a PI or Epic  – with forecast range of end-dates

This is a useful to show the emerging scope during a PI and the impact this may be having on the end-date, providing a simple way to summarise the health, or emerging risks, of a PI to stakeholders.

Burn-up chart with ‘landing zone’

This chart shows the likely range of project PI end dates. By highlighting the relationship between scope and throughput rate it helps to engage both stakeholder groups to find options to adjust the ‘landing zone’.

This animation,  using real project data, gives an interesting story of how the project progressed.

Show relative Burn-ups for different teams in a dashboard

If the teams have normalised their story sizing (always a slight question mark over that) then a single Burn-up of the PI would show the overall landing zone.

However,  a good alternative is to put burn-ups from different teams alongside each other in a dashboard and forecast dates compared visually.



Epic Progress chart

See an epic across multiple teams. Epic Owners can drill into an Epic to see underlying user stories.  This simple, real-time, chart enables stakeholders to see the relative size and completeness of all Epics.

Backlog Map

See stories by Epic or Area Path/Tags along the top – and sprints/PIs down the side. This is an engaging way to show areas of focus and state of work on the backlog.