Project Management Central
|
Please login or join to subscribe to this thread
|
|||
|
|||
Rami Kaibni
 Community Champion
Omar
I trust by SPI you mean Schedule Performance Index. There isn’t a one size SPI that fits all. SPIs are project specific and depends on many project related factors like Risk Tolerance and Thresholds, Stakeholders requirements, Project Needs, impact of project delay and so on. For some projects being slightly behind schedule can be tolerable but for others it might not be so the level at which revisions are needed are project dependent. RK 
Omar -
To add to Rami's feedback, I'd say that you need to work with the team to assess the odds of achieving your original milestone and project end dates based on the SV/SPI so far. I don't know of any rules of thumb regarding SPI, but there is one for CPI in the case of large capital projects where once you've spent about 20-25% of your budget, your CPI won't dramatically change till the end. Kiron 
Keith Novak
Tukwila, Wa, USA
I would add that I generally find that the analysis and discussion of the schedule variance is more important than the SPI itself.
Particularly on smaller projects where you have fewer scheduled events, CPI and SPI can change significantly, especially at the beginning when even fewer are due to complete because then it is more of a step-function, than a continuous variable. The schedule might still be fully recoverable however if there is enough margin/buffer/float/slack to absorb the delay. Once the delinquent event is complete, the SPI then looks healthy again without replanning the project. 
Eduard Hernandez
Community Champion
I find SPI a misleading indicator. At the end of the project, it will always equal one, even if the project has been severely delayed.
Thorughout the project, SPI might have some value but towards the end its significance becomes limited. On the other hand, CPI is a more meaningful indicator throughout the whole project. Instead, the Earned Schedule (ES) allows EVM metrics to be transformed to time or duration metrics to enhance the evaluation of project schedule performance and to forecast the duration needed to complete the project. 
There isn't an average value for SPI for IT Projects. The value of SPI may vary with multiple factors like risks, resource rotation, quality issues, scope changes, contractor delays, etc. Schedule revision should be performed when SPI is under zero because it signifies the project is behind schedule.
When SPI is equal to 1, it means the project is on schedule, and when SPI is greater than 1, it signifies the project goes ahead of schedule. |
|||
Please login or join to reply
ADVERTISEMENTS
|
"If you don't know where you are going, you might wind up someplace else." - Yogi Berra |
