What is the thinking behind the 3 sprint delay in showing predicted sprints for the release burndown chart?

What is the thinking behind the 3 sprint delay in showing predicted sprints for the release burndown chart?

Predicted sprints are calculated based on your team's velocity* (amount of work completed in the last three sprints), but why do we have to wait to show the predicted sprints if these are then based on the total velocity of the team and not the velocity of the selected version/release?

Thanks

2 answers

This widget could not be displayed.

I would also like to know the same. Seems that JIRA could use the team's existing velocity (based on the last 3, 6, 9, etc, sprints) to provide release date projections as soon as work begins on a release. This seems especially helpful for companies who are releasing regularly. If a group has 2 week sprints, then even a "medium-sized" feature (4-6 sprint) project/release would have no visibility until you are nearly done. sad

This widget could not be displayed.

Hi,

Even I am looking for a solution to this. We have very frequent releases and not able to predict anything.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted 5 hours ago in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

23 views 0 1
Join discussion

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