Rebaseline would not be a good thing at this point. If you rebaseline, you
are essentially admitting you made a mistake and want to reset your measures
to 1.0.
I am assuming you mean you have a negative schedule variance and a Schedule
Performance Index (SPI) of less than 1.0.
Insert the SPI column into the Gantt Chart. Examine the tasks where SPI is
less than 1. These are the tasks you need to get back on tract to raise your
SPI. Unless you have a change in contract scope or schedule direction, you
should not rebaseline. If you are simply performing poorly, you need to
figure it out.
Typically these problems are coupled with a change in CPI as well. If CPI>1
look to see why, you are probably understaffed and that would account for a
low SPI. If both CPI and SPI are below 1.0, then you underbid the job or ran
into a technical problem (more than likely).
You can use SPI to somewhat predict when the project will end:
[Duration so far] + [Remaning Duration]/[SPI]
If your revised schedule reflect a date too much better than this duration,
question it. Unless you have contractual direction to rebaseline you should
carry this schedule variance as long as it lives. Fortunately, SPI is self
correcting toward the end of a program.
--
If this post was helpful, please consider rating it.
Jim
Visithttp://project.mvps.org/for FAQs and more information
about Microsoft Project
Vinayak Raghuvamshi said:
Mid way through a project, we find that for some of our tasks the
schedule variance is well below 1. So we are lagging behind in some
tasks.
What is the general practice in this scenario? do we rebaseline the
project plan immediately with revised end dates? Do we wait for a
while and try to get project back on track (If so, wait how long)?
What is the best practice? Any other suggestions/ inputs?
Thanks.
-Vinayak- Hide quoted text -
- Show quoted text -
