This simple representation of the delivery dates and the two key variables is an effective way to engage 'the business' in their key role of managing scope and actively prioritising the backlog.
The history, represented by Scope (1) and throughput rate (2) are clear. Often we see rates of scope increase like this with our clients.
Projecting forwards the chart clearly shows the green landing zone (3) The user sets assumptions about how much history to use for the average rates of decrease in scope and standard deviations for throughput rate
Vertical lines clearly translates this into dates that can be compared to business expectations (4)
All the variables chosen in making the chart are shown in the title data (5), making it easy to copy and paste this into other documents.
The buttons along the top enable easy toggling of other elements of the project.
Teams that care about the proportion of unestimated items can reveal this (1) and (2) - where the purple bit at the top represents the unestimated items. Clicking on this gives a list of those items
The rate of increase of bugs, and the proportion that have been fixed, is also a useful guide to the progress and quality of the project these are shown with (3) and (4) - where the green colour shows fixed and the red shows remaining bugs
The left had scale can be toggled (5) between effort (a total of the story points) and count (the total number of items)
The chart title data (shown in Image 1) can be hidden (6)
Click on the chart to see options to take further action. The dots (1) on the lines will show all the items that make up that status.
You can easily filter (2) and sort the pop-up table, which can be downloaded to your desktop for further analysis
Click on the item title (3) to open it directly in TFS
Change key settings of the chart to provide the most accurate picture. This can then be saved and shared as a URL - with one-click access by anyone in your company.
Sample the historical data (1) at whatever frequency makes sense to your team. Choose the project start and end dates (2).
Each team might have a different 'definition of done' - select the columns (3) that represent 'Done' for your team.
Determine the variables for the future projections of Throughput (4) and Scope (5)