Stories/Effort Added After Sprint Started Not in Sprint Report

Robert Rhyne December 11, 2013

Our team is using JIRA to track our sprint work. Currently we are experiencing the following issue. If a story is added after the sprint was started, or effort increases in a story that’s in a current sprint, the additional points are not being considered in the sprint report and is incorrectly stating the team’s velocity.

Is there anything we can do about this?

3 answers

1 accepted

1 vote
Answer accepted
Preston Ruiz December 11, 2013

Hi Robert,

We observed this issue too and we haven't found a way to force the JIRA Agile Velocity Report to acknowledge story point changes after the sprint is started. It's deceiving because the point field on a story can be edited even after the story is in an active sprint.

We are now extremely cautious in making sure all stories have the correct point value when starting the sprint (or in the case of pulling in a story to an active sprint, we make sure it contains the appropriate point value before adding it to an active sprint).

In the event of a story becoming larger after the sprint starts, my teams don't adjust the point value. Instead, we discuss it in the retrospective to determine what caused us to under-estimate the story.

1 vote
Nicholas Muldoon
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 31, 2013

Hi Preston, Robert,

You may also be interested in voting and watching GHS-8776 which incorporates a change in behaviour to better capture a change in the sprint commitment.

GHS-8776 - As a Scrum Master, I want the story points completed to also include added in user stories that were completed in the Sprint and Velocity Reports and not just committed user story points.

Thanks, have a super 2014!

Cheers,
Nicholas Muldoon
@njm

-----

New Agile Team? Getting started with JIRA? Check out JIRA for Agile Teams.

0 votes
Sminu Joseph January 16, 2019

Any solutions for this yet? I see this post is from 2013 and we are now in 2019. 

Dario B
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 13, 2019

Hi @Sminu Joseph ,

According to below bug ticket this issue should have been solved back in 2015:

 

If you still experience a similar behavior it may be a good idea to either create a new thread or open a support request with Atlassian Support by using the below link:

 

Cheers,
Dario

Suggest an answer

Log in or Sign up to answer