Hi I have a question from one of my Blog readers:
“I wonder if this is a bug in MS Project 2016?
Here what I did:
1. Created a 3-day fixed units, non-effort-driven task
2. Assigned one resource at 100% capacity
3. Changed Duration from 3d to 5d
4. Chose the option “Decrease hours resources work per day but keep the same amount of work” so that scheduled Work remained unchanged
In response Project :
a). changed Peak Units to 60%. Which is correct. But it also changed the Assignment Units to 60%. And I don’t understand why?!!!
b). Project made the task to be an effort-driven. Why?”
First of all, that is not a BUG! I will show you that in MS PROJECT 2016
I’m going to create simple Project with one Task with 3 days Duration:
Then I am going to create one Resource and assign it to the Task.
I will now turn on Task Form, and I will get:
Now I am going to change Duration from 3 to 5 days:
Finally I will get:
Now, I am going to answer to questions:
- Changed Peak Units to 60%. Which is correct. But it also changed the Assignment Units to 60%. And I don’t understand why?!!! – Because if what happens when you decrease or increase duration. It is real assignment units now, in this new situation
- Project made the task to be an effort-driven. Why? – Because if you say that you want to have fixed numbers of hours (same amount of work), than when you add, for example, new resource to the same task, duration or assignment units will be decreased, but the work will remain the same. This is, at the end, all about Effort driven.
Hope this helps!
Nenad. Good post. To put a finer point on it, in the example you show you refer to the task resource allocation as “peak units”. That’s not quite it. Peak units applies to the resource, not the allocation of that resource on a given task. In the example above, the peak and allocated units are the same. If there was another task added that used “Resource”, and started at the same time, you’d see “Peak Units” for the “Resource” at 160%.