Burned Work / Remaining Work

I have a question regarding how you propose to use the Remaining and Burned hours for a task. I thought remaining hours is kind of initial estimate of the task. We keep updating burned with actual (which could be more or less of the estimate). That way we know how far is the actual effort from estimate, so that we can use this information for future estimates. But the remaining gets updated by tool automatically by substracting hours burned.
So are you looking at team member updating remaining hours with adjuested forecast based on latest discovery.

Thanks.

Status

Issue is closed.

Comments

Thu, Mar 1, 2012, 18:22 by artjom (PO,T)

Yes, the intention is exactly as you put it. At the end, the burned hours should contain the actual work done and remaining hours should be 0 (in fact, that is how a Task being done is defined).

The burndown chart makes use of those values. You can notice that burned hours make the chart decrease diagonally, while changes is estimation (changes of remaining work, addition or removal of Tasks) makes the chart jump straight up or down.