C
chris.read-smith
If you create a plan for example and you put say 100 tasks in this
plan each task taking 5 hours each, therefore the entire plans
baseline work is 500 hours. These tasks are on random dates ahead of
today.
You have 1 resource (lets call him Noddy) that can do these tasks and
he is working 7.6 hours a day thus taking him around 66 working days
to complete.
However, the finish date for the project is in 50 days, showing a peak
in the resource graph.
Realistically, there is nothing Noddy can do about this. Noddy's
company is not going to employ anyone else and they are not going to
budge on the finish date.
So, Noddy commences work at project start date and is working to
schedule.. At the end of week one Noddy has done 38 hours of work and
completed everything he was meant to have completed so he now has an
SPI of 1.
Rather than waiting until the following monday to start work, Noddy
comes in on the weekend and knocks off a few of the jobs that werent
meant to have happened until later in the project. (these jobs were
the jobs causing the peak in his resource graph)
On Monday, Noddy comes back into the office and commences his work as
usual.
Now, Little Noddy, he is on schedule, he has completed the work that
was Planned to be done by today, all his jobs that were planned are
100% complete so he has an SPI of 1. On top of this he has also
completed some work that is scheduled ahead of time.. So his SPI is
probably a bit more than 1 indicating he is actually ahead of
schedule. All pretty simple stuff really. If only we all had good
resources like Noddy....
However, there is no resource view in MSP showing that Noddy is the
only resource required to finish the work and that we dont need any
extra resources for those future jobs that were causing the peaks.
Or is there?
plan each task taking 5 hours each, therefore the entire plans
baseline work is 500 hours. These tasks are on random dates ahead of
today.
You have 1 resource (lets call him Noddy) that can do these tasks and
he is working 7.6 hours a day thus taking him around 66 working days
to complete.
However, the finish date for the project is in 50 days, showing a peak
in the resource graph.
Realistically, there is nothing Noddy can do about this. Noddy's
company is not going to employ anyone else and they are not going to
budge on the finish date.
So, Noddy commences work at project start date and is working to
schedule.. At the end of week one Noddy has done 38 hours of work and
completed everything he was meant to have completed so he now has an
SPI of 1.
Rather than waiting until the following monday to start work, Noddy
comes in on the weekend and knocks off a few of the jobs that werent
meant to have happened until later in the project. (these jobs were
the jobs causing the peak in his resource graph)
On Monday, Noddy comes back into the office and commences his work as
usual.
Now, Little Noddy, he is on schedule, he has completed the work that
was Planned to be done by today, all his jobs that were planned are
100% complete so he has an SPI of 1. On top of this he has also
completed some work that is scheduled ahead of time.. So his SPI is
probably a bit more than 1 indicating he is actually ahead of
schedule. All pretty simple stuff really. If only we all had good
resources like Noddy....
However, there is no resource view in MSP showing that Noddy is the
only resource required to finish the work and that we dont need any
extra resources for those future jobs that were causing the peaks.
Or is there?