Skip to end of banner
Go to start of banner

PPM - Using Program Predictability Measure report

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Contents

Prerequisites

Ensure that you are good on the following prerequisites:

Reading the chart

Your Program Predictability Measure Gadget displays the following information:

  • Commitment for each release measured in Business Values
  • Actual work delivered measured in the same metrics
  • % of the total BV delivered for a certain PI - line on the chart indicating percentage of the total BV delivered for a certain PI. This line helps you identify the accuracy of how your team is providing estimations. The more the percentage, it means that the team is getting better and more precise in measuring the assigned tasks, thus you are on the right track.

Reading the chart

The following example shows that the team had only 10% estimation accuracy for 2018 Q1. Starting 2018 Q2 it looks like the lessons were learnt, and the team's estimates (commitments) become much more accurate - around 50% and more. This shows positive tendency and shows that the team matured and is showing great results in estimate (commitments) accuracy.

Selecting data to display on the chart

The interface enables you to customize your report view by showing and hiding the data depending on your current focus. For instance, if you are focused on estimates (commitments) accuracy, you can hide the Lower point (static green area) on the chart by clicking the name in the chart legend as shown below. To display hidden data again, click its name in the legend again.

Tooltips

For you to have an instant insight into what the certain parts of the chart mean and how much work was delivered at a certain point in time, hover over a place on the chart. The tooltip will show details for the selected point on the report.

Zoom feature

If you have too many PIs displayed on the report, it might get difficult to read data (see screenshot), so you can zoom in to see only a few sprints of interest. To zoom in, hover over the chart area and use the mouse wheel or your track pad. Also, you can pan over the chart by clicking and dragging on a section of the chart. To zoom out, you can use your mouse wheel or click the Refresh button.

Program Predictability Measure details in tabs

Working with the report details, you might want to have more insights in addition to chart view. For this purpose we provide detailed information, insights, and warnings in a table view below the chart.

There are the following tabs with the report insights:

Summary tab

Here you can view information about committed and delivered work measured in the selected metrics, percentage of delivered Business Values, and warnings in case the actual progress is behind the plan. Note: In case source data is not available the panel is hidden.

StatsDescription
Total BV committed 

Sum of all planned BV for all PIs in the report. The sum of all planned BV in the PIs tab is equal to the Total BV committed in the Summary tab. This means that a feature can be calculated several times in the Total BV committed. 

Total BV delivered 

Sum of all BV for all PIs within the period for the reporting. If the feature was planned in several PIs but got delivered in the last one, only this one will be count for the PI where it was delivered.

Lower point

Point where a delivered Business Value percentage should be considered to be still within the norm. The default is 80%.
This setting defines the static area on the chart in green color.

% of BV delivered

Total BV delivered / total BV committed for the period of the report.

Total features
Sum of all features examined for the report, even not delivered ones.


This statistics can help you plan the future releases. For example you can use Total BV committed and Total BV delivered as the value for the ideal team velocity and plan releases taking this into account.

PIs tab

The PIs tab contains details on the projects that are included in the report. The PIs are clickable to make the navigation faster for you.


Warnings tab

Warnings are generated to help you identify cases when chart's data might show not the actual picture. For instance, when Feature wasn't marked as done or Features containing tickets that are not estimated (Original Estimate field is empty). Also there might be Features that don't have BV indicated (BV field is empty) or any of the children of the Feature are tagged to a different PI. The tickets in the Warnings tab are not in included into the chart calculations, so to ensure the chart's accuracy, click the issue in the warning and take action, for instance – fill out the necessary fields in this ticket.


For the children of the Feature  that are tagged to a different PI

  • When a chart is built and shown, check the tickets tied to this feature / capability / portfolio epic. If at least one of these tickets is linked to a PI (fixVersion) that is different from the Pi that a feature / capability / portfolio epic is linked to, this will be displayed in a warning. 
  • If the Feature is committed in a PI, all child stories should also be completed in the PI. The feature should not be marked complete/done until all children are done, and if some children are not done until a later PI, then that Feature should only be credited as "complete" in the later PI. 


Exporting report data

You can export the statistics and the program details data into the XLS file by clicking the Export button.

Other tips and tricks

For you to have a meaningful data on the Gadget, check on the following items:

  • You check the Warnings tab from time to time and triage Features from there. The Features shown in the Warnings tab are not included into the chart calculations, and thus in order to see the accurate picture on the chart, you might want to triage those feautres first.

See also

PPM - Configuring Program Predictability Measure report

  • No labels