Re: Default Task Type


"Steve House" <sjhouse at hotmail dot com> wrote in message
news:%234Lf36niIHA.6032@xxxxxxxxxxxxxxxxxxxxxxx
Except for the rare cases when the task really is something that must run
for a specific time, such as a test that must run for precisely 24 hours,
no more and no less, why would you fix the duration and vary the resources
while recomputing work as the dependent variable? Work effort is what
translates directly to deliverable creation, not the passage of time. It
seems more logical to fix the amount of work to that which will produce
the required deliverable and vary the resources until the computed time
fits into the required deadlines. Indeed, the applications you offer
where you are trying to determine how many resources will be required on
the project is exactly where that approach is most useful. "Our contract
calls for us to deliver 1000 widgets on June 1st and it takes 1 man 1 hour
to make 1 widget. How many resources will it take to complete the
required 1000 man-hours of work by our contracted delivery date?"
Answering that question is best done through fixed work task typing, not
fixed duration, comparing computed end date with the contract deadline and
adjusting resources accordingly.

Why? Fixing duration and entering work will give you the resource
requirement in a single step. I don't understand why you contend that the
easiest way to do this is wrong.

(And note, when you vary the units on a default fixed units
tasks, Project treats the task as fixed work.)

I know that scope tradoffs happen in software development (and
elsewhere) - that doesn't mean they're good.

Changes to a plan in response to reality are inevitable and are neither bad
nor good.

Remember Windows ME? Having to renegotiate for a reduced scope after the
project begins is one of the things one is trying to avoid through proper
planning. Reducing scope because the business objectives or priorities
have changed - no problem. But change orders shouldn't come about from
planning failure, they should come from change to the strategic business
need for the project's objectives, initiated or at the least approved by
higher pay-grades than the project manager. A project that doesn't
complete its stated charter objectives 100% is a failed project, something
we're trying to avoid through proper planning.

The schedule tool doesn't know if a change is good or bad either. I hope you
aren't suggesting that a schedule is failed if there is any change to it.
Changing your "reality" to match your plan is not a particularly good idea.

-Jack Dahlgren


.

Relevant Pages

  • Re: Task Type Differences
    ... you would ever need to use a Fixed Work task. ... > Project uses the formula Work = Units * Duration ... > In this formula Units refers to resources. ... > If you Fix the Units, then adding resources means that you are overriding ...
    (microsoft.public.project)
  • Re: What should be put into a duration?
    ... the availability of the resources required to do the work. ... usually assign a resource at 100% - if Bob is assigned to wax widgets I'm ... So when I input the task I'm going to estimate its duration and let Project ... the training should be split out as individual tasks in their own ...
    (microsoft.public.project)
  • Re: Isnt there a "Machine" Resource Type???
    ... I may also have to go back and fix the duration ... The answer is there is only ONE CLASS used for allocated resources, ... Fixed units, fixed work, and fixed duration only applies to what happens ... SCHEDULE these d_mn tasks. ...
    (microsoft.public.project)
  • Re: Estimated dates
    ... Now your problem is figure out exactly HOW to achieve those objectives - what workflow organization and what sorts of resources and how many to assign where will be required in order for it to be possible for these tasks to take place where they must take place in order for your project to be successful. ... I have a set schedule that I need to stick to based on outside ... I can in fact think of tasks that could have a flexible duration - that could ... Than or a Finish No Earlier Than constraint date (bet you have a little ...
    (microsoft.public.project)
  • Re: Need opinion on Project test questions and calculations
    ... To start with, fixed duration is responsible for more warning messages and confused users than all other settings added together, especially if Calendars are edited to show non-working time. ... For time constrained projects the duration should be entered and resources needed calculated. ... the allocation % is the total available allocation based on the calendar week settings in Microsoft project. ...
    (microsoft.public.project)
Loading