This might be one of the biggest downfalls of Greenhopper today and I know that many users already inquired of finally changing the CFD report to utilize story points instead of the issue count.
I'd like to share what I'm doing today to improve the project reporting on a bigger project.
The idea is simple - we have a backlog full of stories and hopefully estimated all the way and we have an average velocity.
Product Owner, Scrum Master and everybody else wants to know when we will the project/product will be complete (meaning the backlog has been completed).
You take the total story points (backlog) and calculate using the average velocity. You will complete all stories in X sprints.
Add a pesimistic and an optimistic projection, and you have some alternative schedules.
Now, put all that in a chart you'll look at something like the picture attached.
This is what I do from excel extracts today and I'm sure there's many of you doing something similar.
I raised a feature request with Atlassian. Please support the request if you'd like to see something like this in the future:
...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...
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