Remaining Estimate

Ricard Bertran

I recently adopted Jira as SCRUM ágile development tool.

 

This is my scenario:

• Scrum board
• Estimation Statistic: Original Time Estimate
• Time Tracking: Remaining Estimate and Time Spent

 

1. Our Product Owner populates BackLog with  “User Story” issues
2. Our team estimates each “User Story” so we fill “Original Estimate” field in the “User Story”
3. Once all  “User Stories” are dropped to current sprint, we start sprint.
   At this point, only “User Story” issues exist in current sprint.
4. Then, the development team starts working. 
   So, a team member takes first user story issue and breaks it down into several subtasks (depending on user story complexity).
   At this point, both "User Stories" and "Subtasks" issues exist in current sprint
5. Once sub task is completed, team member logs work into sub task “Time Spent” field.

 

What we expect?

We expect, “Remaining time” in “User Story time tracking” is updated by the following formula:

 

[Remaining Estimate] = [Original Estimate] – ( Sum([ work log ]) )

 

Where Sum([ work log ]) is the sum of “all work log in all sub tasks” plus “work log in user story”

 

What we got

Remaining is ONLY updated with “work log in user story” even when “Include sub-tasks” is checked

 

Example:

1. Create User Story Issue “User Story 1” and estimate it (Original Estimate): 1 week
2. Create subtask “Subtask 1”
3. Create subtask “Subtask 2”
4. Log work in Subtask 1: 1 day
5. Log work un Subtask 2: 1 day
6. Refresh “User Story 1” issue time traking

 

Time Traking

Remainig : 1 week

When actually team has worked 2 days! and "Remaining" should be: 3 days.

1 week (5 working days) - 2 days = 3 days

 

Is there any way or workaround to use Jira to fit our needs?

Thanks

subtask2.png

MainTask.png

subtask1.png

stratejos [stratejos.ai]

It might be easiest to change your process to something like:

When the developer picks up the Parent User Story:

1. Break it into sub tasks 
2. Set the remaining/original estimate of the Parent User Story to 0. 
3. Then put original estimates on the subtasks they have created and work from the subtasks from then on.

The reason why this might be best is that JIRA treats each ticket individually when it comes to estimates. There is a great comment here [https://answers.atlassian.com/questions/127989/answers/4048694] that describes it well.