Why leave estimation at the story level if it sums up with sub tasks?

A few days ago, I received the following answer:

 If you are creating a story on the spot, put in a rough estimate as a placeholder and then when you break down into sub-tasks you can remove the estimate from the story.  That being said, I recommend leaving the "original estimate" as the sum of the tasks and the remaining estimate (still at the story level) as 0 so you can get valid metrics and forecasting.

I do not think it is correct - when I leave an estimate at the story level and estimate sub-tasks, it will sum-up. In my opinion, there is nothing wrong with leaving an estimate to 0 on the story level and estimate sub-tasks. Or am I missing something?

3 answers

1 accepted

1 vote
Accepted answer

I'm not sure this is "correct" either.  I think JIRA is built to allow all the users to work in different ways.  Some of us need to break up stories into subtasks and estimate just them.   Some of us need to estimate subtasks and reduce estimates on their parent story as we go.  Some of us need to estimate a story and then use subtasks to add new things to the job at hand.  Some of us need to estimate a story and subtasks as individual pieces of work.

All of these approaches are supported in JIRA and it makes no effort to force you to do it in any one way.

What I suggest in all the questions about how estimate work is "talk to your users, work out what works best for you and go that way".  You are absolutely spot-on with "there is nothing wrong with leaving no estimate on a story and estimate the sub tasks" - it's a perfectly valid approach as long as your users know that is what you expect of them.  (It's also my preferred way to work - a story is a rough "something someone wants" and the subtasks are identifiable, discrete and estimate-able chunks of work that need doing to make it happen.  But that's just the way I do it when given free choice.  Other approaches work just as well, depending on the context)



I would suggest that you estimate stories using story points (not based on hours/efforts) and do the sub-tasks on the time basis. This helps in realistic epic burn-downs and release burn-downs. And the sprint burn-down will use the actual time estimates at the sub-task level.


From my perspective estimates in SCRUM are done on Story level. The subtasks are the tiny items (each one max. 1 day) to get the story into Status DONE. This happens during a sprint (1-4 weeks). I see no need at all to estimate subtasks unless you are not doeing SCRUM wink but "misuse" the Scrum Board.

So from your perspective, tracking time on individual subtasks is not required so everybody logs time against the story-must be pretty chaotic. Well, it has nothing to do with doing SCRUM or not..In addition, if you estimate story and subtasks, you have estimated them twice, because logging against the story does not decrease the time from subtasks..So saying you estimate stories and subtasks (just max for a day) does not make sense.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

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...

2,301 views 12 19
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you