1

I'm a ScrumMaster for a new team, who have added a load of user stories to their backlog and now they are breaking them down into sub tasks and giving those sub tasks estimates.

They've then put these into their Sprint Backlog, but noticed that the sub-tasks estimate is just added onto the User Story estimate. So for example: If the Story is estimated for 1w and they make some sub tasks for 2 days estimate the user story will appear as 1w and 2 days. Anyway for the sub task estimate to form part of the Story estimate?

  • What do you want to do if your story is estimated at 7 days and your subtask estimates add up to 9? Wouldn't it make more sense to just set the master task to 0 once all subtasks are estimated? – nvoigt Jan 17 '16 at 8:48
2

Its dangerous to estimate the story and subtasks separately. In my opinion the subtasks is estimated and becomes the total estimate of the story.

Your dev team will always come up with more subtasks once they understand the story better.

1

IMHO, you should create a custom field that is only tracked against sub-tasks to track "hours remaining" specifically. Be careful about going overboard and tracking vs actuals as that can lead to some seriously weaponized metrics. In general, this sort of data is a gold mine for micro-managers; be very careful not to give such managers ammunition to harass an otherwise healthy team :).

You can refer to this guide:

https://confluence.atlassian.com/display/JIRA052/Adding+a+Custom+Field

I would suggest you create the field as a float, but try not to get hung up estimating tasks too granularly :).

You likely have to reindex, but you can do that in the background to keep from interfering with others' work.

Beyond adding the custom field, I would suggest configuring your Agile board card format to show the hours remaining. You'll have to go few a couple hoops to make sure the new field is available in the custom fields group, but Jira prompts you through that process.

At the end of this, you'll have enabled the developers to break a user story into sub-tasks and put hour estimates on those sub-tasks without affecting the story level estimate.

Last, you may be working in a domain that is well suited for temporal estimates. Plenty of very simple, repetitive work lends itself to being easily and precisely estimated in this way; however, if your project is like the majority out their, it's not so simple. Consider reading up and choosing relative estimation techniques to ensure you're getting enough accuracy in your estimates without incurring the overhead and error of forming precise estimates.

  • "weaponized metrics"! Now that's an expression I am going to steal and use as my own! :-) – Mikkel Apr 8 '16 at 16:16
1

Short Answer

Clearly define your approach for estimation with your team. If all user stories will have sub-tasks, then estimate the sub-tasks only and it will roll up correctly to the user story.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.