Hi,
I have found that the remaining time estimate (RTE) for a sprint burndown is significantly less than expected.
I believe this occurs when a part complete story is added to a sprint in progress, incurring a scope change, and this story contains sub-tasks that are both part completed or Done. For the sub-tasks already 'Done' the burndown amends a RTE decrease equal to the last timeestimate change.
In my opinion the timeestimate for this sub-task would be zero and would not affect the RTE at any point as it has become Done before the scope change.
I cannot find any evidence of the time being absorbed elsewhere, such as in the story.
This has lead to the sprint dashboard underestimating the RTE by upwards of 30 hours in cases.
Has any one else noticed this error? Or am I miscalculating somehow?
