Points accepted (by sprint)

About this report

The points accepted (by sprint) report shows the overall velocity by level of effort (LOE) points accepted by teams participating in a program increment (PI). The report displays the data in the form of a bar graph. The LOE point range is on the y-axis, and the sprint sync dates are on the x-axis. This report is designed to give a Portfolio Manager or Release Train Engineer a high-level understanding of whether the work for a PI is on track.

It is beneficial to review the report with team members during pre-PI and post-PI meetings, general team meetings, and sprint review meetings. This report is generated by selecting a target PI and program.

To navigate to this report:

  1. Select Programs in the top navigation bar and select the program you want to view information about.
  2. On the sidebar, select Reports in the list of options.
  3. Select Points accepted (by sprint); the report displays.

    Prerequisites
  1. PI must exist in the system and be tied to a program. 
  2. Sprints must be created and tied to the PI. 
  3. Sync sprints must be scheduled for the PI. 
  4. Team sprints must be associated to sync sprints. 
  5. Stories must be created and tied to the program. 


How are report values calculated? 

  • Points Accepted: Each bar on the chart represents the total number of LOE points accepted by all agile teams within a sprint in the selected program and PI. LOE points are entered for stories via Details panels.
    Note: Kanban teams are not included in this report.

group_velocity.png

How to interpret this report

It is a common misconception that the number of points accepted each sprint should continually increase. The sign of a healthy, stable development organization is that point delivery remains consistent. If you see many peaks and valleys, this may point to team instability (for example, engaging members in other work continuously) or that work has been estimated inaccurately (whether the stories are too large or estimates are wrong).

If there are wide fluctuations in the group's point acceptance, that indicates a poor level of predictability in scope of work that can be expected to be delivered. An ideal group remains consistent.

Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.