|
Hello, more on work load calculation: I created a task lasting 10 days with an estimated work duration of 10 hours The task is in the future. If a leave the plan empty and i don't have any other task running during this period, my work load is spread over the 10 days, ie 1 hr / day now i plan the work for this task: 1/ i enter 5 hours on the 6th day of the task, the load then tells me 1hr/day for the first 5 days, then 5 hours on the 6th day then 0 for the remaining days: this looks good 2/ i then add 5 hours in the plan on the 7th day (in addition to the 5 hours on the 6th day), the plan tells me i am over-planned for the 7th day (orange) which is because the load is still 1hr/day for the first 5 days. why is that? 3/ to correct this, i tried and entered 0:0 for the first 5 days but TW then considers there is no plan for these days and leave the 1hr/day load. i got it to work somehow by entering 0:01 for the first days and 4:55 for the 7th day, but this can become tedious for a task with many days... can you reproduce this problem? I would expect to be able to plan the work as two days of 5 hours and get a 0 hr load for the other days and no over planning for these two days. Thank you for your help Julien |
The question has been closed for the following reason "The question is answered, right answer was accepted" by Silvia Chelazzi Jul 06 '11 at 05:20
|
I've tested what you say and I get exactly the same. The problem is that when you enter a period for a task and then a worklog estimated Teamwork tries to guess the load of each day, in this case is one hour per day. The plan is checked day by day so when Teamwork finds the plan on a specific day it removes those hours from the total and continues with the next days. For example 10 hour / 10 days = 1h per day first day 1h second day 1h third day -> plan -> 5 h (the total now become 3h ) this 3 hours are divided by the rest of the task period (7 days). In your case you should move the start date and end date to the days with the plan, this task in fact actually does not last 10 days but 2 because you know exactly when your resource needs to work on it. |
|
What you suggest would indeed work. However, changing the task start and end dates after planning the work seems tedious. But more importantly I believe planning needs to know what the load of the user is in order to be done correctly. In this case, planning is made difficult because we do not see how it affects the load since its calculation is wrong. As you said, "the plan is checked day by day". Wouldn't it be more appropriate to sum the planned hours over the whole task duration and then remove them from the estimated worklog in order to properly calculate the load? Thanks again for your help. Hi again, I would like to know whether the above approach is likely to be corrected in the future unless you consider it is the proper behavior? Thank you for your answer!
(Feb 17 '11 at 10:53)
Julien M
|
|
Hello, good point, I also hope that will be corrected and the load will be calculated in the way that Julien descripe. Regards |
|
We have fixed this behavior in the new Teamwork release out soon. This is what you will have in the next Teamwork release: Operator load of a task lasting 10 days with 10 hours estimated:
Showed plan:
Using plan to add 2 days of 5 hours:
New load showed:
|
Fixed in Teamwork 4.7