Understanding sprint board metrics in Jira: How story points are calculated in Power BI Jira Connector

Understanding sprint board metrics in Jira: How story points are calculated in Power BI Jira Connector

This article explains how Sprint Board metrics in Jira (such as committed, completed, added, and removed story points) are calculated based on different event types during a sprint. The context is based on a board named Cloud Infrastructure Automation.

Instructions

We reviewed a sprint named CIA.2024.S02 with Sprint ID 2592 on Board ID 815. The reported metrics were verified and found to be accurate, based on the event breakdown and screenshots provided.

A burndown chart is displayed as an example.
A continuation of the burndown chart.

Sprint Metrics Breakdown

The following table desribes each type of story point, along with a description and example.

SP Column

Description

Event Type

Result

SP Column

Description

Event Type

Result

Sprint Committed SP

Story points included in the sprint when it begins, and those added right at the beginning.

Sprint Start & Co-events

25

Sprint Completed SP

Accounts for issues that were marked as Done during the sprint

Issue Completed

17

Sprint Removed SP

Accounts for any mid-sprint scope changes.

Issue Removed from Sprint

7 (1 estimate decreased + 6 removed)

Sprint Added SP

Accounts for any mid-sprint scope changes.

Issue Added to Sprint

25 (20 added + 5 estimate increased)

Sprint Scope Change SP

Represents the net change in scope during the sprint:

Added SP + Estimate Increase - Removed SP - Estimate Decrease

Scope Change

18 (Added 25 - Removed 7)

Sprint Remaining SP

Remaining story points at the end of the sprint.

Sprint Ended

16