Estimated effort vS Actual effort
Status: Beta
Brought to you by:
adam_boas
Menu
▾
▴
In scrum, this is usually done by comparing how many task hours were required to deliver how many points, looking at what was burned down per story is not completely reliable though, since the task hours only represent how many hours are remaining. If someone spends 8 hours on a 5 hour task and marks it complete at the end of the day then those 3 hours are lost. I could allow the iteration admin(s) to enter how many EFTs where in the iteration when it is closed and then the velocity comparison chart would show how many EFTs were required to get the resultant velocity. Would that give you what you are after or are you looking for something completely automated? If so maybe let me know what you think would work better.
Cheers,
Adam
Just re-read my comment and realized it didn't really address your request properly. I could do what you ask and add an input for actual hours. The argument I always get back from agile developers about tools vs cards and walls, though. Is that tools are not saving them time but rather costing them time. Adding another field for entering actual time taken is likely to up the barrier to using the tool for individual team members and make them feel like they are being watched. What I am suggesting in my other response is a way for the scrum master to manage it and get at least gross numbers without effecting the team. I'm not sure if that is enough for what you are after.
Cheers,
Adam