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

[Support Team [Clearvision]]

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

[Deepthi Aynumpudi]

Hi,

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

[Patrick Dyle]

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.