Epic burndown shows incorrect prediction

Rochelle Levy May 26, 2022

Epic burndown prediction display:

- 38 story points remaining

Screenshot 2022-05-26 at 11.13.37.png

Calculate remaining story points manually = 32 points. 

 

Any ideas?

1 answer

0 votes
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 31, 2022

Hello @Rochelle Levy ,

It sounds like you are running into an issue with scope change, this is mentioned in the documentation:

Noting:

Scope change is not considered when calculating the velocity*, but is included in the total work remaining.

So I would recommend looking for any occurrences of scope change where any issues that do not have a value for the 'Estimate' field when a sprint is started and have values entered after the start of the sprint will be treated as scope change.  They show with a * ("Issue added to sprint after start time") next to them in the Sprint Report. and the Burndown Chart records this as a scope change with 'Issue added to sprint' in event detail.

Regards,
Earl

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events