Value delivered

About this report

The Value Delivered report shows the daily sum of all estimated value points and the sum of tested value points for a specific sprint. Value points represent an increment of value for the company, such as revenue expectations, improved quality, or speed to market.

The report provides this information in the form of a line graph, depicting a time-series relationship while visually representing volume. Information is graphed on an X and Y axis, using data points connected by line segments. This report is beneficial to Scrum Masters, team leaders and members, and product owners to measure value point totals as stories progress to the Test Complete state during a sprint. It is beneficial to review the report with team members during sprint review meetings and daily standups. Executive management may also be interested in this report. This report is generated by selecting a specific PI and sprint.

Navigation

1. Select the Reports icon from the left Navigation menu.
2. Start typing the report's name in the Search box. 
3. Once found, select the report.

Note: You can also use the categories on the left to search for the needed reports.

Prerequisites

1. PI must exist in the system and be tied to a program.
2. Stories must be assigned to sprints.
3. Value points must be estimated on stories.
4. Sprints must be created for each team. 
5. Teams must be created and tied to a program. 

How are report values calculated? 

• The sum of all value points is pulled from all stories in the sprint with assigned value points, and again from the same stories in a Test Complete state; value points are entered in the Story Gird/New Story panel.
• Story state (Test Complete) is pulled from the Story Grid/New Story panel or kanban board (if categories/columns are mapped to states)
• Sprint dates are pulled from the Sprint List/New Sprint panel.

How to interpret this report

Because value points usually equate to business value, such as selling more units or lowering production costs, most executive managers would rather learn that a sprint team delivered 40 value points, as opposed to 40 effort points or story points.

The goal of any sprint is to have as much value delivered by the end, which is desired before the sprint review. Scrum Masters and product owners should look for a steady cadence of value points moving to the Test Complete state during a sprint, as opposed to high volumes of value being delivered at the end of a sprint.