Loading Profile...
How to show hours completed against a task's total?
How do I show progress against a task (mark hours completed as a part of the total hours for the task)? Do I simply reduce the number of hours for a task to show that some have been completed toward the total task hours?
I’m undecided
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?Simply: yes. Task estimates should be adjusted to whatever you think this task will (from now on) take to finish and if you think it is finished, then mark it as 0.
1 person says
this answers the question
1 Comment Add a comment
This answers the question
-
Thanks for the quick reply. I guess if I want to know what was originally estimated for a task, I can tack it on in the task description. Our scrum master would probably like to be able to see what tasks have had some progress (hours worked) against them. Perhaps I'll have to suggest an enhancement such that the original task estimate is available for viewing against the remaining task estimate. :-) -
Inappropriate?BTW root problem here is a misconception about task estimates in Scrum.
Task estimates in Scrum are outlooks into the future from each day (point in time) onwards, so they can even go up. For example, a developers' initial estimate of task "X" was that it will take 8 hours to complete. After working on it for 4 hours, however, he discovers it is more complex than he thought therefore his estimate the next morning is 10 hours - even though he worked 4 hours on it already. So, the task estimate is supposed to tell us how much time is *left* in a task until it is completed.
Traditionally the team members were required to update the task estimates each day during or just before the daily scrum on a wall. Because Banana is a Scrum tool you could think of as an intelligent replacement for the wall. It just follows Scrum and reports changes in the estimates. It is not a tool that registers actual hours worked - for that a time sheet application would be more appropriate.
Hope that helped.
I’m confident
1 person says
this answers the question
1 Comment Add a comment
This answers the question
-
I'm not in any way an expert on Scrum, but it was my understanding that one of its fundamental purposes is to be constantly inspecting and refining your process. I would imagine that this includes our ability to initially estimate the amount of effort/time involved in tasks. It seems difficult to inspect and refine this skill without actually taking a look at your past accuracy. Although I would agree that Banana Scrum should not be a full-fledged time tracking tool, most examples of Sprint Backlogs that I've seen include columns for initial estimates and work done on each task. Adding this functionality to your product would not, I believe, be in violation of the principles of Scrum.
-
Inappropriate?I guess I can understand that. I'm kind of new to Scrum, so I'm still learning. I can see where as a Scrum purist, a person wouldn't care whether the estimate had changed overnight, but rather only how many hours remain to be completed before the end of the sprint. However, I'm sure that our scrum master and others who are overseeing things would want to know why the "hours remaining" increased overnight, what the problem is, if the "smoke" is a sign of "fire", etc. It looks like they would be forced to poll all those who have active tasks in order to find out what happened. In any case, thanks for responding to clarify.
I’m hopeful
-
Inappropriate?Again, in theory this should surface on the next daily scrum. Someone would say "yesterday I worked on X (backlog item) and I did task Y but task Z turned out to be much more difficult, I've spent some time on it but I had to increase the estimate". At least that's how it works here at Code Sprinters, hence we never experienced a need to have it somehow underlined in the Scrum tool.
But indeed it would help to see if changes to the total number of hours estimated were caused by a change of estimates or by - for example - adding or dropping something from the sprint. We have plans to implement the burnup chart, that makes it more visible.
And I think your query inspired me to think of how we could also make changing the estimate up on a task more visible.
I’m confident
-
Inappropriate?Check out burnup chart in the latest release of Banana Scrum. It will help you track your team's progress against task's total.
I’m happy
EMPLOYEE
