Velocity Chart : what is commitment Story Points calculation logic

Hi Team,

I'm capturing agile metric for my project.

So wanted to check for the velocity.

Though there is velocity chart available, but it shows up only for last 5 iterations.

Hence had to go for manual calculation.

Manual calculation logic and chart output is giving different data.

explanation is as follows:

My understanding is,

Commitment Story points = All story points in an iteration that was planned to be completed (which may have been removed or incomplete at the end)

Completed Story Points = All story points that has been completed at the end of an iteration

My query is on commitment story points for Velocity chart that is as follows

  1. I click on a sprint report that gives me details of  Completed Issues, Issues Not Completed, Issues Removed From Sprint
  2. So to calculate commitment story points, I simply add up story points for Completed Issues, Issues Not Completed, Issues Removed From Sprint
  3. For Completed i use Completed Issues
  4. For commitment story points, manual calculation is giving me wrong data whereas the velocity chart is showing different data
    For example

Velocity for iteration/Sprint 48 is

Commitment = 74

Completed = 34

but with manual calculation

Completed Issues(32) + Issues Removed From Sprint(10) +Issues Not Completed(67) =109

so as per graph/chart its 74 whereas by manual calculation its 109

Report and data is given below for reference

 

image2015-7-30 12:13:12.png

Click on customer-sprint 48

View Customer - Sprint 48 in Issue Navigator

Closed Sprint, ended by KING, David27/May/15 9:47 AM - 10/Jun/15 10:00 AM Linked pages

 

  1. View in Issue Navigator
  2. Completed Issues

    View in Issue Navigator

    Key

    Summary

    Issue Type

    Priority

    Status

    Story Points (32)

    BNKBT-61873

     

    Story

    Minor

    Closed

    -

    BNKBT-65993 *

     

    Story

    Minor

    Closed

    1

    BNKBT-72118

     

    Story

    Minor

    Closed

    2

    BNKBT-73206

     

    Story

    Minor

    Closed

    3

    BNKBT-74577 *

     

    Story

    Minor

    Closed

    3

    BNKBT-76602

     

    Story

    Minor

    Closed

    -

    BNKBT-76922

     

    Story

    Minor

    Closed

    3

    BNKBT-77547

     

    Story

    Major

    Closed

    3

    BNKBT-79213

     

    Story

    Minor

    Closed

    3

    BNKBT-79329

     

    Story

    Minor

    Closed

    2

    BNKBT-82045

     

    Story

    Minor

    Closed

    2

    BNKBT-83003

     

    Story

    Minor

    Closed

    3

    BNKBT-83004

     

    Story

    Minor

    Closed

    3

    BNKBT-83430

     

    Story

    Major

    Closed

    1

    BNKBT-84406 *

     

    Story

    Minor

    Closed

    3

    BNKBT-84407 *

     

    Story

    Minor

    Closed

    -

    BNKBT-84715 *

     

    Story

    Minor

    Closed

    -

    1. 1.     Issues Not Completed

     

Key

Summary

Issue Type

Priority

Status

Story Points (67)

BNKBT-50931

 

Story

Medium

Development

1

BNKBT-50932

 

Story

Medium

Development

1

BNKBT-50989

 

Story

Medium

Development

1

BNKBT-50990

 

Story

Medium

Development

1

BNKBT-51053

 

Story

Medium

Development

1

BNKBT-54277 *

 

Epic

Minor

E2E Testing

-

BNKBT-64303 *

 

Story

Minor

Development

2

BNKBT-66007

 

Story

Medium

Test

3

BNKBT-67521

 

Story

Minor

Test

5

BNKBT-67734

 

Story

Minor

Ready

5

BNKBT-68707

 

Story

Medium

Development

3

BNKBT-76966

 

Story

Minor

Test

8

BNKBT-80545

 

Story

Minor

Development

5

BNKBT-80552

 

Story

Minor

Development

8

BNKBT-85048 *

 

Story

Minor

Ready

3

BNKBT-85170 *

 

Story

Minor

Development

5

BNKBT-85173 *

 

Story

Minor

Ready

5

BNKBT-85506 *

 

Story

Minor

Development

3

BNKBT-85779 *

 

Story

Major

Test

3

BNKBT-85780 *

 

Story

Major

Development

2

BNKBT-85781 *

 

Story

Major

Ready

2

 

  1.     Issues Removed From Sprint
  2. View in Issue Navigator

Key

Summary

Issue Type

Priority

Status

Story Points (10)

BNKBT-64319

 

Story

Minor

Ready

-

BNKBT-76601

 

Story

Minor

Ready

2

BNKBT-80555

 

Story

Minor

Test

5

BNKBT-80683 *

 

Story

Minor

Ready

3

BNKBT-86364 *

 

Story

Minor

Ready

-

*Summary details removed intentionally

 

 

4 answers

This widget could not be displayed.

Hey,

even if the question is quite old, but as I was wondering about the JIRA numbers myself, maybe my answer helps others too:

  • Delivered story points in the sprint is the sum of all issues in the list "Completed Issues" = 32 - as it is given in the velocity chart summary.
  • The commitment is everything you planned, even if you didn't complete it or removed it from the sprint afterwards. The sprint reports marks issues with an asteriks "*", if an issues was added to sprint after start time. So to get the 74 story point from the velocity chart summary, calculate:
    (32-1-3-3) + (67-2-3-5-5-3-3-2-2) + (10-3) = 74

Greetings smile

This widget could not be displayed.

Hi Team,

Could you please respond to the above query?

This widget could not be displayed.

Hi Team, Awaiting for your response!

This widget could not be displayed.

We'd like to have an official answer for this as well!  In the meantime...

Our current working assumption is exactly what BK wrote - ignore the points for stories add after the sprint started.  However, we have an additional caveat for story points that have changed during the sprint. These are represented in the report as two numbers with an arrow between (e.g., "42 -> 45"). 

So, when calculating Commitment exclude issues added after the Sprint starts (those with a '*") AND use the number on the "left" if the story points were changed during the sprint.

 

One thing I am not sure of is what happens if a Story was added to the Sprint after it began and then removed before the Sprint ended. I haven't looked into it but I assume that it just doesn't appear.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Apr 22, 2018 in Jira Software

How-to setup a secured Jira Software 7.9.0 on Ubuntu 16.04.4 in less than 30 minutes

...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...

1,482 views 10 12
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you