Loading Profile...
How to Track Estimated Time vs Actual Time?
I'm in the process of implementing SCRUM for our in-house development efforts. One thing I'd like to track is original estimates (in hours) vs actual time (in hours) for tasks. Once you increase or decrease the hours remaining for a given task, it overwrites that value and you lose historical data.
Any suggestions or tips for how to track this metric using Banana Scrum? I want to easily gauge the estimate accuracy of my dev team.
Any suggestions or tips for how to track this metric using Banana Scrum? I want to easily gauge the estimate accuracy of my dev team.
3
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Banana Scrum doesn't track task execution time. In fact, in Scrum the task estimate is always an outlook to the future and is updated only once a day prior to or during the Daily Scrum meetings. Banana Scrum follows this and in it you can always update task estimates, but only the final value for a given day is stored permanently.
As of now we don't plan to change it. We feel there are other, better tools to track time for billing purposes and we also feel introducing too many metrics would ruin the purpose of using agile methods in the first place. Scrum Master can see how well the team is estimating by participating in Daily Scrums anyway and sees that much better than we ever could calculate.
The company says
this answers the question
-
Inappropriate?Hi,
I'm managing an offshore development team.
The problem is in our house we need to pay developers based on the time spent per week.
That's why I have the same problem as ddavis, I need to see how much time spent on task vs estimated time.
I think if we can have another curve in the burn up chart and the burndown chart where developers at the end of a task enters how much time he spent on it.
and of course as long as we progress in developement, team will be well trained on estimation so they will made estimations as close as the actual spent time.
I know that this issue is not not Scrum, but it is essential in the case you pay your team based on hours passed on a project.
Any suggestions guys?
Have a great day
Your app rocks. -
Inappropriate?First of all we are glad that you like Banana Scrum. We understand your needs, but on the other hand we want to keep our tool simple and focused on Scrum. There are millions of time tracking applications out there and we don't want to develop another one. We believe that such functionality would have to be more complex than it looks at the first sight. I'm sure that simple information about time spent per task won't be enough for your needs and you would like to have reports, statistics and ways to analyze this data in a meaningful way that are offered by existing time tracking tools.
One possible solution would be to implement integration with other time tracking applications. As a matter of fact we plan to publish and document an open API for Banana Scrum in the near future so that teams can create their own mash-ups.
The company says
this answers the question
EMPLOYEE
