Suggestions on Estimations

[Parveen Vats]

Hello ! Geetings!

I am looking for suggestions on estimations :

Let's assume structure as :

Story Points 1 = 1h - 2h
Story Points 2 = 2h - 4h
Story Points 3 = 4h - 6h

Story Points 4 = 6h-8h and so on....

Case 1) What is the common practice for estimation when we have hierarchy like
User Story >> Tasks >> Sub-Tasks  ?  

 >>>Should we estimate Story first and then divide time in Tasks and then divide it further to sub-tasks ? What are the best scenarios (common approach) we can have in this situation ?

>>>Should we estimate Tasks only and not sub-tasks ? and sum total of Tasks as Story estimate ?

Case 2) If we estimate user story in story points as 4 points. Then we Estimate Task 1 : Original estimate field as 3h and Task 2 as 4h and If we do not further break down the estimation to sub-tasks level -- Then after logged in actual time in field Time Tracking
Can we SUM UP TIME SPENT on Task 1 and Task 2 and it automatically adds up to Original Estimate field of User Story as 7h ?

Please help with your suggestions.

Regards
Parveen

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

There's a lot to talk about here, but I'll try not to write an essay.

• Story points are not a time estimate
• If you want to be estimating in time, the best option in Jira is to use the time estimate (original estimate, remaining estimate, time logged, etc)
• Sub-tasks are not independent items, they are part of their parent issue.
• In Scrum, you do not estimate sub-tasks - as part of a parent issue, their estimates are included in the sprint item estimate
• In Kanban, the card itself is the estimate, you don't put time or story points on them

If you decide to use time estimates, then you'll find plain Jira already does all the sums for you - look to the time-tracking pane on the issues and you'll see an "include subtasks, and the issue navigator has a set of Σ fields for reporting.