Burndown chart Scope change issue on Sprint start

Hi,

I'm facing a problem with the Burndown chart.

I've planned my Sprint 3, and after adding ALL the Stories I start it on the 30/08.

The problem is that the burndown chart is showing the stories as if they were added after the sprint start, as Scope change. Even more akward is that it is marking this Scope changes as one per day for future dates always at 6:00.

Attached is the current Burndown chart on the 02/09.

Any idea what is the cause of this behaviour? And own can I solve it?

9 answers

1 votes

For anyone experiencing this issue, you can simply edit the start time of the sprint to after you made the "scope changes."

You can do this by going to the backlog view and clicking "Edit Sprint" next to the active sprint.

I was seeing this problem with issues added just prior to starting the sprint.  being able to push the start time ahead a couple of minutes fixed it nicely.  thanks!

This is happening to me too.

Were you able to solve the problem?

Are you estimating the stories in your sprint before starting the sprint or after. If it is after that may explain why it is showing as scope change.

In ideal case stories must be estimated before the sprint gets started.

Rahul

@Donny I still have the issue.

@Rahul The estimation was made before, and it work properly for the first 2 sprints. this start to happen at Sprint 3 and it's being occuring since.

@Rahul - yes, the estimation was made before the sprint was started. After the sprint is started, all the stories appear in the burndown chart and report as scope change. My burndown chart and report are similar to Nuno's.

In case it is helpful, my board contains issues from two projects. Also, I have parallel sprints labs feature turned on. I am not using parallel sprints on this board, but they are being used in another project / board in my organization.

Hi @Rahul and @Nuno,

I think my issue might have been caused by adjusting the sprint start date right before starting the sprint, from the default time it gives (current time) to an earlier day/time. We tend to start our sprints after planning meeting, which is usually Monday @ noon. However, in the last sprint, the planning meeting went late and we didn't start the sprint in JIRA until Tuesday morning. When I started the sprint in JIRA, I back-dated the sprint start date to the afternoon of the day before (to reflect when developers started working on issues). However, I think it treated all issues as scope change because of that.

Is that expected? @Nuno - did you adjust your start date?

I just started my next sprint, leaving the defaults, and at least initially, it seems fine. I did experience what @Nuno did with an issue appearing to change scope at the same time every day.

Thanks,
Donny

Hi @Donny,

This happened for the first time in Sprint 3, and I did in fact adjust the dates (not sure if it was the start or end date, and for before or after). however it happens on the following sprint as well, even if the date weren't changed.

If the problem is with the dates being changes, it seems a bug to me. If the date change functionality is available it shouldn't cause this issue.

thanks,
Nuno

Sorry to attempt to revive such an old thread but it's 2016 and this still happens. Basically if you do sprint planning on the first day of the sprint and set the start time to any time before the moment you clicked "Start Sprint" (even an earlier time on the same day), any changes made between the start time set on the sprint and the moment you clicked "Start Sprint" are counted as scope change. This seems pretty crazy. Is there no way to work around this? I've worked with other tools that did not have this problem.

Hi Steve,

What if the scope change date is 2 days after the sprint started, how to fix it?

Thanks,

Sridhar

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

824 views 5 17
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot