Earned Schedule- An improvement to EVM Scheduling Metrics
Picture Credit: Project Control Academy

Earned Schedule- An improvement to EVM Scheduling Metrics

Earned Value Management (EVM) is a powerful tool for evaluating the schedule and cost performance of projects and predicting future results. However, existing earned value schedule performance metrics does not do a good job with schedule performance evaluation and prediction.

Use of “Earned Schedule” enhances the earned value management ’s ability to better represent and forecast schedule information. Watch this video training to learn how:

You cannot rely solely on Earned Value schedule performance metrics (SPI & SV) to assess the schedule performance and predict future schedule results. The reason is two fold:

1. EVM Units of Measure Are Usually Currency, Not Time Units

EVM metrics are measured in units of currency, typically dollars, and that produces variances in dollars, which is useful from a budget regaining perspective, but not necessarily the schedule.

SV($)=EV($)-PV($)=$...

SPI & SV are very often misinterpreted as a time-based indicator, for example, are we early or late and by how much?

SPI & SV are not time-based indicators, but rather an indication of the physical status (how much of the work has been accomplished as compared to the planned work).

You cannot use cost ($) to speak about time units, the amount of delays (duration), or the reason for the delay.

That’s why the EVM scheduling metrics are not used to estimate the project completion date.

2. EVM Scheduling Metrics Are Not Reliable Toward the End of the Project

Another issue with the EVM scheduling metrics is that they fail toward the end of the project.

The schedule indicators initially appear to establish a trend at the beginning of the project. However, at some point around 2/3 into the project the SPI begins to become meaningless.

The reason is that at the end of the project the earned value will be equal to the planned value, which results in SPI of 1 and SV of zero.

EV= % x Budget (BAC)

At the end of the project, EV= 100%x BAC= BAC

At the end of the project, PV= BAC

Therefore, at the end of the project, EV= PV and as a result, SV=0 and SPI=1


This indicates that at the end of the project, regardless of how early or late the project completes, the EVM scheduling metrics shows perfect on-schedule performance.

This quirky behavior of SV and SPI occurs for every project approaching the finish line, no matter how early or late.

So, what can be done?

Ignore the EVM scheduling metrics all together?

Well, this is what most Project Managers do. They pay much more attention to cost metrics than they do for the schedule.

However, this ignoring the EVM scheduling metrics does not solve the problem either. There are several ways to enhance the reliability and accuracy of the EVM scheduling metrics.

One of the newly emerged methods is the “Earned Schedule.”

In this training, I am going to introduce you to the concept of “Earned Schedule”, so you know how you can use Earned Schedule metrics to assess and predict the schedule performance.

Earned Schedule

The earned schedule is a new concept developed by Walt Lipke in 2003. Now Earned Schedule (ES) is an appendix in PMI Practice Standard for Earned Value Management and is considered as an extension to the EVM practice.

Although the knowledge and use of ES have grown immensely and spread globally over the last decade, the method remains unknown to many EVM practitioners.

I believe the Earned Schedule is a very simple concept. It is not difficult to grasp. There is almost insignificant effort required to add and utilize the capabilities offered by the Earned Schedule.

I encourage you to use the Earned Schedule metrics in your next EVM project and evaluate the outcomes as compared to the traditional EVM scheduling metrics.

Earned Schedule vs. Earned Value

The idea of Earned Schedule is analogous to Earned Value. However, instead of using cost ($) for measuring schedule performance, it uses time.

Rather than just looking at schedule performance using the $ value of work accomplished as compared with the plan, the Earned Schedule looks at when the work was supposed to be completed.

Let’s examine the concept of the Earned Schedule through a simple example.

EV= $300

PV= $500

SV($)= EV-PV= -$200

SPI($)=EV/PV=0.6

Now, to measure Earned Schedule, we need to determine “when” the work was supposed to be earned.

In other words, at what point in time was the current Earned Value (EV) should have been occurred?

This is determined by crossing a horizontal line from the current cumulative EV to the PV curve. The intersection of this line with the PV curve is the Earned Schedule.

In this example, Earned Schedule is 2 months.

Therefore, Earned schedule (ES) is the point in time when the current earned value was to be accomplished. It is the point at which the project PV supposed to be equal to the current EV.

There are other terms that you need to know:

Actual Time (AT):

The other new parameter is the Actual Time (AT), which is the number of periods executed since the time the project started.

In our example, the total number of periods executed from the beginning of the project is 3 months. Therefore, Actual Time (AT) is 3 months.

Planned Duration (PD):

Another new terminology is the Planned Duration (PD), which is the “original duration of the project”.

What is the PD in our example?

That’s right. It is 6 months.

Now we have 3 key elements to assess the schedule status in units of time:

  • Earned Schedule (ES)
  • Actual Time (AT)
  • Planned Duration (PD)

Similar to the traditional EVM metrics, new ones can be generated for schedule performance.

SV(t)= ES- AT

SPI(t)= ES/AT

To distinguish between the traditional EVM metrics and Earned Schedule metrics, a “t” representing time is added in Earned Schedule metrics.

Going back to the example used, let’s examine the schedule variance and schedule performance index:

SV(t)= ES-AT= 2-3= -1 month

SPI(t)= ES/AT= 2/3= 0.67

Like our traditional SV & SPI, a negative SV and a less than 1 SPI shows a behind schedule status.

However, here you measure the Schedule Variance with units of time instead of $.

In this example, we are one month behind schedule, and the schedule performance index shows that for every hour worked on the job, we were only 0.67 hours (40 min) productive in accomplishing the work planned.

Do you recall the issue with the SPI($) and SV($) at the end of the project?

Do you think this issue is resolved with the SPI(t) and SV(t)?

Let’s assume that our project completes in the month of September (month 9) and our total approved budget is $1M at the time of project completion.

According to this information:

At the end of the project:

EV=100%x Budget= $1M

PV= Budget (BAC)= $1M

ES=PD=6 months

AT= 9 months

Therefore…

SV($)= EV-PV=0                     SV(t)= ES-AT=6-9=-3 month

SPI($)=EV/PV=1                    SPI(t)= ES/AT= 6/9= 0.67

The important observation is that SPI(t) & SV(t) remained good indicators of project status while the SPI($) & SV($) ended up at 1.0 & zero respectively regardless of 3-month late completion of the project.

In addition to schedule performance metric, similar to the cost forecasting metrics, schedule forecasting metrics can be utilized to forecast the schedule completion date (e.g. To Complete Schedule Performance Index (TSPI), Estimated Time at Completion (EAC(t)) and Variance at Completion (VAC(t)).

More information on the Earned Schedule metrics and formulas will be covered in another training.

In summary, use of Earned Schedule enhances the earned value management’s ability to represent and forecast schedule information accurately.

I hope this training raised your curiosity in the use and application of the Earned Schedule in your projects and provided you a new means to justify your misbehaving SPI ($) and SV($) toward the end of the project.

 --------

Thank You Note

Thanks for reviewing this post. I regularly shoot videos or write articles on Project Controls. If you would like to have access to my future posts simply click "Follow." Also feel free to connect with me on FacebookLinkedIn, and Instagram.

You might also be interested in receiving my 10-day free online video training series on Earned Value Management and how to unleash its amazing power in effectively managing your projects.

As the founder & director of Project Control Academy, I am committed to adding value to Project Control community not only through our comprehensive training programs in Project Controls but also by delivering these free training videos and resources on a regular and consistent basis. I hope you find these training resources helpful.

For More Project Controls Resources:

----------------------------------

Please share whether you have used Earned Schedule method in your projects and how accurate the results were. I’d be interested in hearing your thoughts and comments that would promote a healthy and positive discussion.

David McNamara

Passionate about program planning / cost

6 年

This would require more effective and accurate schedule update process. Last week I met a scheduler that said she updated her weekly progress simply by subtracting five days to remaining durations!

Jordy Watson, PMP, P.E.

Consultant - Project Controls at Sand Hill, Inc.

7 年

Good post. It should be pretty intuitive that providing schedule metrics in terms of currency rather than time based units, is not ideal (among the other quirks). This has been a recognized practice from PMI for over a decade. I hope it catches more traction in the industry and more use it to compliment traditional EVM metrics.

Dimitris Kafiris

Director-Delay, at Analyzer, MEng - SP, RMP, PMP

7 年

In particular, the Earned Value Curve, consists of the values of the “Completed” and “In-Progress” activities that proved to be critical as of the Data Date (DD). These values “take” their position along the time axis according to the Actual Dates of the respective tasks. The Planned Value curve consists of exactly the same values plus the ones related to the remaining activities or the remaining portion of the In-Progress tasks that currently appear to be critical and obviously are planned to take place past the DD. All these values “take” their position along the time axis according to the Planned Dates of the respective tasks being apparent in the Baseline Programme. Hence, on the same graph, we have again two figures to compare. The PV and the EV curve. The great difference, as compared to the initial concept, is that the PV and EV curves are now dynamically formatted over the course of the project by taking into account the values, partially or as a whole, that correspond to the critical tasks or any critical portion of them, the way they unfold and get known to us from initiation to completion. Now the ES metrics can be reliably applied, as the sole tasks participating in the calculations are the Critical.

Dimitris Kafiris

Director-Delay, at Analyzer, MEng - SP, RMP, PMP

7 年

The concept here is not to use a pair of fixed (PV,EV) curves produced through the respective values of the activities falling on the BL Critical Path, which soon turns obsolete, but re-define instead these sets of values based on the actualized tasks or the actualized portion of them that turns out to be critical as the project progresses as well as on the remaining tasks that appear to be critical on each update. Thus, a rolling wave approach is suggested in replacement of the static one of the original method. Both the Planned and the Earned curve are being shaped on a continuous basis over the course of the project. Their components are the values of the critical tasks the way I described above.

Dimitris Kafiris

Director-Delay, at Analyzer, MEng - SP, RMP, PMP

7 年

Well, to overcome the riddle, I attempted to take the initial concept one step further and develop a technique able to transcend all the drawbacks of the original method and at the same time, to provide an alternative approach whereby the time forecasts become much more reliable. The following paragraph delineates in brief what the proposed technique is all about. My thought was to exclusively use the PV & EV of the activities on the Critical Path. Then the question of which CP I should use came naturally in my mind. If the CP was remaining constant throughout the project duration, there would be no problem, since the principles of the ES Management could be applied, not on the entire schedule, but on the activities comprising the Baseline Critical Path only. Unfortunately, that’s not the case in real life. The CP once the project commences keeps changing. So, the question remains and needs to be answered. Which Critical Path should I select? The one being apparent in the BL Programme or maybe one of those CP’s emerging along the way? The straightforward answer is: All of them. Let me explain.

要查看或添加评论,请登录

社区洞察

其他会员也浏览了