The original version of this paper was published here in May 2009:
See S-curve/intro.htm

This 4th Edition was submitted for publication in January 2019.
It is copyright © Midori Media.
Published here October 2019.

PART 3 | Why Use S-curves? | S-curve Analysis
Generating S-curves | Conclusion

S-curve Analysis

Initial analysis of the S-curves generated in the last section reveal the following about the status of the Project:

  • The progress of the Project is behind target
    The Actual S‑curve sits below the Target S‑curve at the Cut Off Date.
  • The Project has grown in Man Hours
    The Target S‑curve finishes above the Baseline S‑curve.
  • The Project has grown in Duration
    The Target S‑curve Duration is longer than the Baseline S‑curve Duration.
  • The Project has experienced Start Slippage, and thus started later than planned
    The Target S‑curve starts to the right of the Baseline S‑curve.
  • The Project has experienced Finish Slippage, and thus will finish later than planned
    The Target S‑curve finishes to the right of the Baseline S‑curve.

Project Progress

According to MS Project, based on the Production Schedule the Project is 31% complete. MS Project calculates % Complete based on Duration, and does not take into account Man Hours and/or Cost assigned to each Task. Analysis of the Actual and Target S‑curve data reveals the Project is 40.00% complete as of the Cut Off Date, while the Project should be 51.05% complete.

Actual % Complete
      = Actual YTD Man Hours @ Cut Off Date / Target Man Hours x 100%
      = 38.0 / 95.0 x 100%
      = 40.00%

Target % Complete
      = Target YTD Man Hours @ Cut Off Date / Target Man Hours x 100%
      = 48.5 / 95.0 x 100%
      = 51.05%

Project Growth (Man Hours and/or Cost, Duration)

The Project may grow (or contract) in terms of Man Hours and/or Cost, and in Duration.

Project Growth (Man Hours)

Analysis of the Baseline and Target S‑curve data at Project Completion reveals the Project has grown in scope by 5.0 Man Hours, or 5.56% as compared to the Baseline Schedule.

Project Growth (Man Hours)
      = Total Target Man Hours – Total Baseline Man Hours
      = 95.0 – 90.0
      = 5.0

Project % Growth (Man Hours)
      = ((Target Man Hours / Baseline Man Hours) – 1) x 100%
      = ((95.0 / 90.0) – 1) x 100%
      = 5.56%

Project Growth (Duration)

Growth in the Project's Duration may be determined by comparing the Baseline Duration with the Target Duration.

Analysis of the Baseline and Target S‑curve data reveals the Project has experience a growth in Duration of 1 Day, or 20.00% as compared to the Baseline Schedule.

Project Growth (Duration)
      = Target Duration – Baseline Duration
      = 6 Days – 5 Days
      = 1 Day

Project % Growth (Duration)
      = ((Target Duration / Baseline Duration) – 1) x 100%)
      = ((6 Days / 5 Days) – 1) x 100%)
      = 20.00%

Project Slippage

The Project may experience Start Slippage (starting later than planned) and/or Finish Slippage (finishing later than planned).

Project Start Slippage

Analysis of the Baseline and Target S‑curve data reveals the Project has a Start Slippage of 1 Day, or 20.00% as compared to the Baseline Schedule.

Start Slippage
      = Target Start Date – Baseline Start Date
      = 2nd Feb 2016 – 1st Feb 2016
      = 1 Day

Start Slippage %
      = Start Slippage / Baseline Duration x 100%
      = 1 Day / 5 Days x 100%
      = 20.00%

Project Finish Slippage

Analysis of the Baseline and Target S‑curve data reveals the Project has a Finish Slippage of 2 Days, or 40.00% as compared to the Baseline Schedule.

Finish Slippage
      = Target Finish Date – Baseline Finish Date
      = 7th Feb 2016 – 5th Feb 2016
      = 2 Days

Finish Slippage %
      = Finish Slippage / Baseline Duration x 100%
      = 2 Days / 5 Days x 100%
      = 40.00%

Project Summary

The Project's progress to date (i.e. the Cut Off Date) is behind target compared to both the Production and Baseline Schedules. The Production Schedule may need to be reviewed to ensure Tasks have been updated accurately (especially with respect to true % Complete values), and ongoing and future Tasks may require rescheduling.

The Project has grown in scope and will finish over budget. Project growth may be due to a number of factors, including underestimation of effort in the Baseline Schedule, low productivity, rework, variations (approved or not), unexpected weather or other delays, etc. In this example, variations may need to be raised to account for the extra Man Hours.

The Project has grown in Duration, started late, and will finish late compared to the Baseline Schedule. Project Duration growth, and Start / Finish Slippage may be due to a number of factors, including unexpected delays, low productivity, rework, variations (approved or not), etc. In this example, a Claim for an Extension Of Time and/or Excusable Delay may need to be raised for the later than planned start and/or completion dates.

In summary a detailed analysis of the Project is required to determine why the Project will be completed late and over budget as currently scheduled.

Why Use S-curves  Why Use S-curves

Home | Issacons | PM Glossary | Papers & Books | Max's Musings
Guest Articles | Contact Info | Search My Site | Site Map | Top of Page