#ITASKX NEW TASKS ARE EFFORT DRIVEN SOFTWARE#

It's way too complicated to explain in writing!Īnyway, to resolve the bug, the Microsoft Project development team used the Assignment Units field to capture the original Units value for each resource assigned to each task.

#ITASKX NEW TASKS ARE EFFORT DRIVEN SOFTWARE#

When the 2010 version of the software was introduced, I was able to recreate the situation that previously led to a bug in the software, and I was able to see that the new functionality DID successfully resolve the bug. The new behavior was functionality that Microsoft created for the sole purpose of fixing a bug that had been in the software since Assignments data was introduced sometime prior to Project 2000. And I can tell you that this new behavior led to wholesale confusion among the entire user community, from novice users all the way up to power users. I believe you are correct that the new behavior was introduced in the 2010 version of Microsoft Project. Whether that has anything to do with this issue, I don't know. I do recall there was a change to the way peak units are calculated, circa Project 2010 or Project 2013 (I think), but I don't remember the details. Is this a good enough explanation for your 'students'? Don't know, but it might make their heads spin a bit :) 33%) and the peak now readjusts to spread the original work content over 4 resources so it shows 25%. If you assign a fourth resource, the assignment units takes on the previous peak (i.e. 50%) and the peak now readjusts to be equal for all 3 assignments (i.e. Then when the third resource is assigned, the assignment units takes on the peak unit value from the first two assignments (i.e. So for the second assignment, the assignment units is still 100% but the Peak reduces to 50%. As each resources is assigned you will see the Assignment Units replicate the previous resource's units while the Peak adjusts to maintain the constant work value. Instead of 3 resources, consecutively assign 4 resources at 100% to the task. The effort driven strives to keep the work content constant and you can see that in the Task Usage view as you assign each of the 3 resources consecutively. 'phenomenon' occurs when effort driven is checked (default) for a fixed duration task.

Itaskx new tasks are effort driven