We don't do any estimates based on time. All of our estimates/actuals are based on Story Points. So, when we start grooming our backlog we estimate all of our Story issues with a Story Point value. As those Stories get put into a Sprint we do task breakout. To accurately reflect partially completed Stories we assign Story Point values to the Sub-Task issues. The problem with this is that in the Chart Board and various Dashboard graphs, we can either have sizes on the Sub-Tasks or Stories, but not both due to cumulative rollup, but as far as I can find, the Rapidboard doesn't do that.
You are correct, the sub-tasks (or their estimations) are not displayed on the Rapid Board, plan mode specially.
There is an improvement request regarding it being tracked at GHS-5614. Please add yourself as a watcher to be notified of future updates.
Probably it's a concept issue here, as story points are at story level and technical tasks are estimated in hours during the sprint planning. This is the reason why this aggregation is not done. At the same time, if estimation is based on Orginal estimate, the sum of the values of the estimate is shown in the Detail view of the issue.
We've been working hard for years to get away from the use of hours. You yourself state in the blog that
A story point approach based on original estimates can deliver the answers to these questions without the anxiety around ‘accuracy’ that teams feel when asked to estimate in hours.
So we've been estimating sub-tasks in story points. Now you want us to revert to hours again?
Introduction This article will give insight on how a small software development department implemented Atlassian products to enhance and streamline the business process. The privately held company 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