Project Management

Please login or join to subscribe to this thread

SPI rule of thumb

linkedin twitter facebook   Work Breakdown Structures (WBS)  
avatar
Anonymous
Hi, I would like to discuss SPI with a subject matter expert. Is it normal for a tool to recalculate a task that completed early to be on time once it crosses the baseline start and finish. In other words, if I expected to start and complete by 10/13 and instead started and completed by 10/2...on 10/5 it would show an SPI of early yet on 10/16 (after the baseline dates) it now shows on time. Is that normal for a tool to operate that way? Thanks!
Sort By:
avatar
Wayne Mack Retired| Retired South Riding, Va, United States
Probably some clarifications of SPI are in order. SPI addresses the project as a whole, so I am not sure why there would be a task level indication in the tool in question. SPI does not address earliness or lateness of a project, it merely represents how much of the planned effort has actually been completed relative to how much effort had been initially projected to be completed.

Do not try to use SPI at a level below the project level - it really does not have meaning at the task level. There are many know challenges with EVM SPI - I usually recommend tracking progress on the critical path as a better measure of project schedule performance.
avatar
Kenneth Fung The Compleat Business Solutions Inc. Calgary, Alberta, Canada
SPI = EV / PV. If the activity / work package starts and complete earlier than plan. The SPI = 1. For example if the Planned Value = 100 and you have completed the work package, Earned Value would = to 100.
SPI = 100/100 = 1.
avatar
Pablo Lledo President| Pablolledo.com Mendoza, Argentina
Is not right to show SPI = 1 if the task finish before planned. If you make the calculations by hand, in your example you will see that SPI > 1, and the same number should be in your software. However, some softwares by default shows SPI=1 when you completed the Task. You need to change the default configuration to get the right answer, and that is not easy.

On the other hand, it is not possible to finish a task with a SPI < 1. If the task has finished, the SPI must be 1.
avatar
Kenneth Fung The Compleat Business Solutions Inc. Calgary, Alberta, Canada
As per the PMBOK Guide “Earned Value (EV) is the value of work performed expressed in terms of the approved budget assigned to that work for an activity or WBS Component.”, "Measure of work performed expressed in terms of budget authorized for that work. "How much work was actually done?" If the work is 100% completed the value of work performed is equal to the approved budget assigned to that work.
SPI is often used at the Project Level. By using SPI at project level, the EV is the sum of all work that is started and performed at a point in time. PV is the sum of all approved budget of all the work that is started as of a point in time. It is used for performance measurement of a project.
SPI at the work package level is less meaningful. Since no work can finish before it starts (not logical). This would means that the Planned start date is wrong and should be amended. Please NOTE that the schedule baseline the PV should be / can be updated.


...
1 reply by MOHAMMADAMIN SADEGHIPOUYA
Dec 31, 2025 10:46 AM
MOHAMMADAMIN SADEGHIPOUYA
...

However, I believe SPI should be evaluated at the activity or WBS level, as different curve behaviours cancel each other out at the project level. For example,

Engineering (front-loaded) is late → SPI = 0.5

Installation (back-loaded) hasn’t started → SPI = 1.2

At project level: They cancel each other out → Project SPI ≈ 1 Management sees green. Reality is red

avatar
MOHAMMADAMIN SADEGHIPOUYA Project Information Manager| Bercaf London, ENG, United Kingdom
Nov 02, 2014 9:38 AM
Replying to Kenneth Fung
...
As per the PMBOK Guide “Earned Value (EV) is the value of work performed expressed in terms of the approved budget assigned to that work for an activity or WBS Component.”, "Measure of work performed expressed in terms of budget authorized for that work. "How much work was actually done?" If the work is 100% completed the value of work performed is equal to the approved budget assigned to that work.
SPI is often used at the Project Level. By using SPI at project level, the EV is the sum of all work that is started and performed at a point in time. PV is the sum of all approved budget of all the work that is started as of a point in time. It is used for performance measurement of a project.
SPI at the work package level is less meaningful. Since no work can finish before it starts (not logical). This would means that the Planned start date is wrong and should be amended. Please NOTE that the schedule baseline the PV should be / can be updated.


However, I believe SPI should be evaluated at the activity or WBS level, as different curve behaviours cancel each other out at the project level. For example,

Engineering (front-loaded) is late → SPI = 0.5

Installation (back-loaded) hasn’t started → SPI = 1.2

At project level: They cancel each other out → Project SPI ≈ 1 Management sees green. Reality is red

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Consistency is the last refuge of the unimaginative."

- Oscar Wilde

ADVERTISEMENT

Sponsors