Using Remaining Time Estimate as Estimation Statistic

[Lena Boiser]

One of the teams I work with uses Time for estimation. As far as I know, Jira uses Story Points, Original Time Estimate, Business Value, Issue Count, and Numeric Custom Fields. So in this case, the team uses Original Time Estimate. 

The team wants that if an issue is carried over from one Sprint to another, the Estimates should show the Remaining Time Estimate as opposed to the Original Time Estimate so that it's reflective of what is left for them to do. 

I don't think this is an option though. Is there a way for us to use the Remaining Time Estimate as the Estimation Statistic?

[Nic Brough -Adaptavist- · Accepted solution]

Correct, this can't be done.

When a team fails to complete a story it said it would do in the current sprint, the story goes to the top of the pile to do in the next sprint.  The estimate you made for its size doesn't change, it's still whatever it was when you decided to work on the story.  The estimate of the size does not change because you've done a bit of it.  

 Velocity is measured on done or not-done, there are no partial measures.  And it's measured against a value that should not change during a sprint.

Remaining estimate changes when people work on the story, 

So, using remaining estimate as the sprint estimate is complete nonsense.

Your team needs to have their scrum master re-explain how Scrum estimation works, and understand that Jira's Scrum boards support scrum, not processes that are not scrum

[Lena Boiser]

Thanks Nic. Very well explained.