Hi all
I was wondering if it would make sense if the burndown reports (release / epic) used velocity to predict
Currently they require 3 sprints to predict, but we have many different initiatives that we break down in different releases and epic and I would like these reports to show the predicted burndown based on our velocity, maybe average over last n sprints (we look at past 6)
Either that, or on the report allow a velocity to be entered to trigger the prediction if required
I understand that driving if off the 3 sprints is the ideal, but at times it's good to get a prediction at the start, and sometime the work isn't much more than 3 sprints anyway
Thoughts?
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Get the most out of Jira
Explore the interface and basic Jira terms, then discover how to effectively manage your work.
Learning Path
Atlassian tools and practices for developers
Focus on your development work by using Jira software features and functions efficiently.
Atlassian Certified Associate
Jira Software Essentials certification
Demonstrate proficiency in utilizing essential Jira features and working efficiently with Agile frameworks like Kanban and Scrum.