M
michael.franke
Hi
I have a large, complex software project that involves 40+ resources
and spans almost two years. We want to construct a schedule/budget
that takes into account the reality that resources don't ever get 100%
of their time to work on the project. We'd like to allow for about a
day a week in "overhead" (that is not charged to the project).
The project plan I've inherited seems to have approached this from
several angles at once, and I have a strong suspicion that the
estimates have actually been padded the wrong way as a result. The
project contains a schedule, for instance that has 6.4-hour work days,
32-hour work weeks, 16-day work months, and all Fridays as non-working
time. (!).
So. My question, for someone with experience, is: "What's the best
way to account for resources only having about 80% of their time to
dedicate to the project?
(Note: setting all the resource "max units" to 80% seems terribly
cumbersome).
Thanks.
Mike
I have a large, complex software project that involves 40+ resources
and spans almost two years. We want to construct a schedule/budget
that takes into account the reality that resources don't ever get 100%
of their time to work on the project. We'd like to allow for about a
day a week in "overhead" (that is not charged to the project).
The project plan I've inherited seems to have approached this from
several angles at once, and I have a strong suspicion that the
estimates have actually been padded the wrong way as a result. The
project contains a schedule, for instance that has 6.4-hour work days,
32-hour work weeks, 16-day work months, and all Fridays as non-working
time. (!).
So. My question, for someone with experience, is: "What's the best
way to account for resources only having about 80% of their time to
dedicate to the project?
(Note: setting all the resource "max units" to 80% seems terribly
cumbersome).
Thanks.
Mike