Hi Chris! Chris Nelson wrote: > http://trac-hacks.org/wiki/TimeEstimationUserManual says: > > Fields: ... * Estimated Hours a field that contains the estimated > amount of work > [...] > But now we're looking for burndown chart and both the > EstimationToolsPlugin and the ScrumBurndownPlugin treat Estimated > hours as *remaining hours*. I think that they should be graphing > estimate-actual but maybe I'm missing something.
You're right, both the EstimationToolsPlugin and the ScrumBurndownPlugin interpret the the field as "remaining hours". These plugins are meant as tools for helping teams to control their progress in an agile process, while the TimeEstimationPlugin seems to be meant for billing purposes, so maybe it's not a good idea to mix these together. For example, if the burndown chart would be calculated as you suggest above, we would get the following situation very often: * a developer estimates he needs 40h for some task. * on the next day, after spending 8h on the problem, he understands the problem much better, and sees he needs at least 60h more to solve that. In the current implementation of the burndown chart, you see that the line goes up, and the team is aware things aren't going smoothly. But if we'd use your calculation, the line would go down, and everything would seem to be fine until the end of the sprint. For another discussion on that topic you also might want to look at the following ticket: http://trac-hacks.org/ticket/4301 Joachim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
