For the last four years, my team has used story points as the organisational metric for our sprints. So, we create a new task for the start of a sprint and we add both the story points and an original estimate.
Quite often a task will remain incomplete at the end of the sprint, because that is just life. Perhaps it took longer than you expected, or perhaps its completion relied upon someone else - to review the work, for example.
There is a problem here with the use of story points as a sprint metric - they do not actually reflect the amount of work that's gone into the task, even if they match up to some degree with your original time estimate.
I got the go-ahead to try out time-based sprints, but I cannot use remaining estimate as the sprint metric (estimation method) - it is not available in the board settings - only the original estimate or the story points.
I understand that you need an immutable metric against which to measure sprint performance, but this needs to be the remaining estimate at the start of the sprint, because if you have tasks inherited from a past sprint, that remaining estimate is the original estimate for that sprint.
It would be false if you were to move the remaining estimate into the original estimate, because these figures then are reflective of the actual effort put into the task. This was the whole problem with the story points - we were adjusting the story points at the start of the sprint, breaking the link between story points and the total task effort.
So:
How can I use the remaining estimate at the start of the sprint as the estimation method? This seems to be me to be the only sensible choice.
