Microsoft Office Tutorials and References
In Depth Information
How Adding People or Time
Affects Your Project
It’s part of corporate human nature to want to throw money and people at
problems; in some cases, that instinct is on target. However, you don’t always
have the ability to draw on endless supplies of resources or an endless
amount of time to play with. Because of this, you may have to play around
with a combination of options involving time and resources.
Hurry up!
Saving time in Project means doing things faster or adjusting the timing of
things to use up slack. You are likely to find that making this adjustment is
like an intricate puzzle: Correct one thing, and something else pops up to
cause you aggravation.
To accomplish work faster, you have two options:
Get more people to help with tasks. Adding people adds money, so you
might get back on track time-wise — but it will cost you.
Modify the scope of tasks. Modifying the scope of the task may have an
effect on its quality. If you do two inspections instead of three or you
shorten your QA cycle by a week, you may run the risk of other types of
problems down the road.
Changing the timing of tasks and shifting dependencies uses up slack to make
up for delays but may leave you with no wiggle room. The next time a
problem comes up, you’ll be up against the wall with no slack to save you.
In reality, combining small modifications for both time and money is often
what helps you save the day.
Throwing people at the problem
With effort-driven tasks, things get accomplished when the specified amount
of effort is expended. So, a task with a duration of 3 days based on a standard
calendar requires 3 days
8 hours per day to be completed (a total of 24
hours of effort). One resource performing this task working full time takes
three days to complete it; three resources working full time take one day to
complete 24 hours of work. When you add resources to such a task, Project
automatically recalculates its duration.
Search JabSto ::

Custom Search