I'm trying to get comfortable with the new rapid boards (https://answers.atlassian.com/questions/203746/rapid-board-story-points-and-sub-tasks-aggregate-estimates-up).
Based on all the information I've read the last days I now understand that we will have to adjust our process a little, by roughly estimating the tasks (PBI's) when they are added to Jira in the first place, and then add more accurate estimates on the sub-tasks during sprint planning. So both the task and the sub-tasks will have an estimate in story points.
Today we do not estimate PBI's, we only create and estimate sub-tasks during sprint planning and then adjust the commitment towards the velocity before we start the sprint. This has given us agreat deal of control, and possibility to track during the sprint.
My challenge is that I no longer feel comfortable with how I can track the projects in Jira. Before I was able to see story points with the burndown chart. As we estimated sub-tasks using story points, we got a burndown that was based on SP's and not related to hours at all. So in most sprints we more or less followed the guideline given by the agile gadget in regards to burndown.
The burndown chart illustrated here (https://confluence.atlassian.com/display/AGILE/Viewing+the+Burndown+Chart) doesn't really give me anything as a PM for an offshore team. It illustrates that the sprint started May 7th (or 8th), but I am only gaining confidence that the commitment will be met May 18th/19th.
So my question is - how do I track with Rapid Boards when:
- Tasks have estimate in story points
- Sub tasks have estimate in story points
Is there a report or something I haven't seen yet? How can I avoid a "big drop" in story points in the burndown, after e.g. 4 days when a 30 sp's story is suddenly completed? I would like something that is more following the guideline in the burndown.
So I read this question, https://answers.atlassian.com/questions/90079/hour-and-storypoint-burndown-chart-on-rapidboard, and the answers, and realized that it seems I have to use a combination of several different boards to get what I need. The new rapid board can be used as a "beta" now to prepare a transition to it (get to know it) while I should stay with the classic ones to be able to track in "story point mode" on the sub-tasks.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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