W
wendyB
I have a set of projects with multiple interdependencies which do not
consistently utilise resource levelling (with multiple cases of real person
overallocations). Most tasks are fixed duration and some only have generic
resources coming (long history).
Currently I'm working under a mandate to rush the migration of these
projects to Enterprise and to ignore resource overallocations (PMs fix this
online later on).
I am looking for suggestions on the best approach to do this, and how best
to minimise the risk of Project Server rescheduling and shifting dates due to
resource overallocation.
Thanks for any and all suggestions.
consistently utilise resource levelling (with multiple cases of real person
overallocations). Most tasks are fixed duration and some only have generic
resources coming (long history).
Currently I'm working under a mandate to rush the migration of these
projects to Enterprise and to ignore resource overallocations (PMs fix this
online later on).
I am looking for suggestions on the best approach to do this, and how best
to minimise the risk of Project Server rescheduling and shifting dates due to
resource overallocation.
Thanks for any and all suggestions.