Loading Profile...
Completing tasks the same day you assign them doesn't update hours complete
If you have an active sprint, plan and add a story, add some tasks to that story, then complete those tasks the same day, your burnup shows work complete as zero. This is a problem because I often add tasks that were done a couple days ago, or add small tasks and complete them later the same day.
The higher-level problem is "what does it mean if you add a task and change the hours?" It could mean that you put the wrong hours, so it doesn't count as work done (current solution); or it could mean you completed the task.
One solution is to have "current" and "total" task hours; but I have perhaps a better solution--when you add stories from the backlog, then those task hours are the "total"; and if you cut them down, it should show as complete.
Or you can just wait a day and mark them as done tomorrow :)
The higher-level problem is "what does it mean if you add a task and change the hours?" It could mean that you put the wrong hours, so it doesn't count as work done (current solution); or it could mean you completed the task.
One solution is to have "current" and "total" task hours; but I have perhaps a better solution--when you add stories from the backlog, then those task hours are the "total"; and if you cut them down, it should show as complete.
Or you can just wait a day and mark them as done tomorrow :)
I’m undecided
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?You are right, it's an important semantic distinction between changing an estimate of a task because you made a mistake (eg. put 100h instead of 10h) and changing an estimate because you actually got the work done.
Our rule of handling this dilemma is imperfect but very simple – any changes made to the estimate during the day it was created are counted as corrections, any further changes are considered "work done".
We considered different design decisions like providing an option to mark the estimate as "final" or implementing two fields: initial and current estimate. However all those ideas require additional steps that the user has to do for *every* task which is prohibitive. We believe that managing tasks should be as simple and quick as possible and in our opinion it's better to have an application that is easier to use even if charts are not perfect.
Finally please take into account that burnup and burndown charts are just a high-level tool to see the general trends during the sprint, not a precise metric.
I’m confident
The company says
this solves the problem
