Contents
| Table of Contents | ||||
|---|---|---|---|---|
|
Prerequisites
Ensure that you are good on the following prerequisites:
- Program Predictability Measure report is added to your dashboard
- You have configured the Program Predictability Measure Gadget
Reading the chart
Your Program Predictability Measure Gadget displays the following information:
...
Once you add the gadget to your dashboard and configure it, you can get the following information:
- Business value that an Agile Release Train (ART) committed to deliver for each Program Increment (PI)
- Delivered business value for each PI
- Delivery rate for each PI
- Insights and warnings on the possible wrong configuration to ensure all data is captured and is accurate.
Reading the chart
The following example shows that the team delivered only around 25% for the for 2018 Q2 PI objectives. Starting 2018 Q3 it looks like the lessons were learnt, and the team's delivery rate became much better. This shows a positive tendency not only in the team's better commitments but possibly also in better planning.
Selecting data to display on the chart
The interface enables you to You can customize your report view by showing and hiding the data depending on your current focus. For instance, if you are focused on sprint estimates (commitments) and the estimation error, you can hide the sprint actuals by clicking the name in the chart legend as shown belowClick the elements in the chart legend to hide the respective information on the chart. To display hidden data again, click its name in the legend againlegend.
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 a quick look at the committed and delivered business value for each particular PI, hover over that point on the chart.
The tooltip will show the details for the selected point on the report.
Zoom feature
If you have too many sprints 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
Exporting report data
You can export the statistics and the program details data into the XLS file by clicking the Export button.
Program Predictability Measure details in tabs
...
There are the following tabs with the report insights:
...
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Summary tab
Here you can view information about planned committed and delivered work measured in the selected metrics, average length for the sprint and average velocity, percentage of delivered Business Value, and warnings in case the actual progress is behind the plan. Note: In case source data is not available the panel is hidden.
...
there is a chance that some data is missing or improperly configured.
This statistics can help you plan 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.
| Stats | Description |
|---|---|
| Warning | In case the ART's progress is below the acceptable norm you gat an instant indication of that not only in the chart but also in the tabs. |
| Projects included | Agile Release Train can combine several projects, and this is convenient to see how many projects are included in your ART. |
| Total BV committed |
Total planned Business Value for all |
data on the report. |
|
. | |
| Total BV delivered | Total delivered Business Value for all data on the report. If a certain feature was planned in several PIs but got delivered in the last one, only |
this last PI will count the BV for this feature. Note that the tickets must be marked as done to be counted in the report. |
| Lower point |
Point where a delivered Business Value percentage |
is still considered to be |
within the norm. The default is 80%. |
This setting defines the static area on the chart - green color on the mockup:
| % of BV delivered |
Total BV delivered / total BV committed |
| Total features |
| Amount of |
| tickets examined for the report, even not delivered ones |
...
| . |
PIs tab
The SprintsPIs tab contains details on the sprints program increments that are included in the report. The sprints are clickable to make the navigation faster for you.
This tab will have the following columns (top to bottom in the list corresponds to left to right in the table)
- PI NAME - up to 5 PIs will be here, no pagination
- COMMITTED BV - please use this label, not the one in the mock
- DELIVERED BV - please use this label, not the one in the mock
- % DELIVERED -
- START DATE
- END DATE
Other details
- Tab name should also have the amount of the PIs in the report, see picture for reference, there's 4.
- Columns are sortable. Default sorting by end date of the PIs from the latest on top to the oldest in the bottom
- Align elements left inside the columns
- No decimals for %
- Date format MM/DD/YYYY
Here you can see the delivery rate dynamics across your PI objectives.
Warnings tab
Warnings are generated to help you identify cases when chart's data might show not the actual picture or when there are issues in how your tickets are configured.
For instance, when an issue is not estimated or when a ticket is resolved outside of the sprint and is not marked as a duplicate or clone. 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.
you will get warnings for the following cases:
- Feature wasn't marked as
...
- Feature completion is indicated by a workflow state. Status category = Done/green
- Text: "Feature wasn't marked as done; report data might be incorrect."
...
- Done thus this is a question whether someone forgot to move the ticket to the correct status or maybe this is expected because it was planned but never delivered.
- Features that don't have
...
- Business Value indicated (BV field is empty)
- We should show this warning for both completed features and those that are planned but not completed yet.
- Text: "Feature doesn't have BV indicated; report data might be incorrect."
...
- Any of the children of the Feature are tagged
...
- to a
...
- different
...
- PI.
...
Other details:
- Tab name should also have the amount of the Warnings in the report, see picture for reference, there's 7.
- FEATURE column is sortable. The default sorting should be from the A/lowest, e.g. ABC-123, then KLM-354, then ZYX-867
- Features should be clickable and open the tickets on click. See Sprints tab in other gadgets for reference, this should work in the same way.
- Once a user resolves the warning and comes back to the report, the warning should go away. See logic in other gadgets to see when conditions are checked and data is refreshed.
- There should be 5 warnings max on the page. If there's 6 or more - there should be pagination. See other warnings in other AR gadgets for reference.
Exporting report data
You can save the chart image, all you have to do is right click the chart area and select Save image. You can also export the statistics and the sprints details into the XLS file by clicking the Export button.
Other tips and tricks
- And so on.
For you to have a meaningful data on the Gadget, check on the following items:
...
the report, we recommend that you check the Warnings tab from time to time and triage tickets from there. The tickets 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 tickets first.
See also
BD - Using Burndown reportPPM - Configuring Program Predictability Measure report