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?
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.
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...
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!
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