Question on dates derived by the MPP

[prashanth.sharangapani]

Dear MPP users,

I have one question. I use MPP 2007.

In general, what I do when I prepare a schedule is -

a) Get the task break down (basically WBS)
b) Identify the dependencies
c) Identify work (hours) required for the line items on WBS
d) Assign resources
e) Level resources - generally I do a 'week by week' leveling and
allow splits in work.

And then work to the dates that the MPP would derive. In my current
MPP, these are the dates put out by the MPP.

Task Work Start
Finish Resource
------------------------------------------------------------------------------------------------
Implementation_1 32 Fri 2/27/09 Fri 4/24/09 A
Implementation_2 24 Thu 2/19/09 Fri 3/13/09 A
Implementation_3 24 Thu 2/19/09 Fri 3/20/09 A

This some how does not make sense practically. How can I expect that
resource 'A' will start with a 32 hour task on 2/27 and assume that it
will go until 4/24 (two months for a 32 hour task!)? And how can I
expect him to start two tasks in parallel on the same day, but go on
to work a 24 hour task for a month?

Typically, a resource would complete one task and then only move to
the next. I understand that the scenario above happens because we
allow splits in the schedule. However, if I do not allow splits, the
schedule duration will become unrealistic. In the above case for
example, when I track my schedule on 2/23, one of the two tasks
Implementation_2 or Implementation_3 will show behind schedule because
'A' can only start one task at a time.

How do I manage this? I need a realistic schedule duration, but also a
practical one which the team members can execute.

Thanks,
Prashanth

 

[JulieS]

Hello Prashanth,

It sounds as though you've assigned your resource at fairly low
assignment units to stretch a task with 24 hours of work out over 1
month. If you assign resource "A" to all three tasks at 100%
assignment units, assuming an 8 hour day, 40 hour week, you should
see durations of 4 days for Implementation_1, and 3 days each for
Implementation_2 and Implementation_3. Using resource leveling will
move the tasks so one follows another. You may wish to try turning
off the option "Allow splits" as it sounds as though you have task
which should be very short duration split multiple times -- likely
to the point that it just doesn't make sense any more.

If you want the resource to be able to work on tasks simultaneously,
you'll need to assign them at less than 100%. If you want them to
work on task 1 & 2 at the same time set assignment units of 50/50 or
60/40 or some other mix. Then do not level those tasks as you have
already manually altered the assignment units to allow them to occur
concurrently.

I hope this helps. Let us know how you get along.

Julie
Project MVP

Visit http://project.mvps.org/ for the FAQs and additional
information about Microsoft Project