W12.2_Anton_Schedule Risk Assessment

1.      Problem Recognition, Definition, and Evaluation

Activities and duration estimate base on productivity and volume of work for earth work job as shown on table 1.

Risks for those activities are identified and quantitative as shown on table2.



Need to develop schedule contingency refer to risk identified, percentile desired is 90%.

2.      Development of the Feasible Alternative

Need to develop schedule prior develop schedule contingency. US GAO (2005) recommendation for establishing the duration of all activities in schedule:


Confirmed by US GAO (2005), “Schedule contingency should be calculated by performing a schedule risk analysis and comparing the schedule date with that of the simulation result at a desired level of certainty” (p. 113).1

In this blog, desired level of certainty is 90%.

3.      Development of the Outcomes and Cash flows for Each Alternative

3.1   Schedule Development

 Follow recommend best practices, to develop schedule, break the activities until duration max. 2 working month


Then develop schedule with total duration 197.75 day as shown below:


3.2   Calculate Schedule Contingency

–        Using PERT method to defined te (Expected Time), σ (Standard Deviation) and σ2 (Variance).

–        Using Standard Normal Distribution to defined Percentile 90% (P90)

z = (P90 – te) / σ

Photo0280 - Copy

Source: http://www.stat.tamu.edu/~lzhou/stat302/standardnormaltable.pdf2

From table standard normal distribution, got z = 0.8159

P90 = z * σ + te


 Plot duration P 90 to schedule, with duration 256.03 day:


4.      Selection of Criterion (or Criteria)

Schedule duration is 197.75 days. To have probability 90% completed on time (within 197.75 days), need to have contingency:

Contingency       = P90 – P50

= 256.03 – 197.75

= 58.28 days

5.      Analysis and Comparison of the Alternative

Schedule contingency may appear as a single activity just prior to finish milestone or it may dispersed throughout the schedule as multiple activities prior to main milestone1.

6.      Selection of the Preferred Alternative

In what percentile applied as contingency on the schedule is management decision, it depend on factor such as contract type, project type and technology maturity1

7.      Performance Monitoring and Post Evaluation of Result

Even with a well-disciplined risk analysis, management may make bad decision with good information and bad result can happen even from good decision3.

8.      References :

  1. GOA Schedule Assessment Guide (2012), United States Government Accountability Office. Retrieved from: http://www.gao.gov/products/GAO-12-120G
  2. Standard Normal Distribution Table (2005), Texas A&M University, Department of Statistics. Retrieved from:  http://www.stat.tamu.edu/~lzhou/stat302/standardnormaltable.pdf2
  3. Humphrey and Associates (2012), Project Management Using Earned Value, Chapter 17. Pp. 325 – 334, Second Editions, Humphreys & Associates, Inc.
  4. John K. Hollman (2012), Total Cost Management Framework, Section 7.6 pp. 163-176, 1st edition revised, AACE International.
  5. Scott, Dr. Amos, PE (2012). Skills and knowlage of Cost Engineering, chapter 31 pp 31.1 – 31.8,  5th edition,  AACE International, Createspace.
  6.        Sullivan W.G., Wicks E.M., Koelling C.P, (2012), Engineering Economics, Chapter 3 pp. 92 – 93, 15th edition, Prentice Hall.
This entry was posted in Anton. Bookmark the permalink.

1 Response to W12.2_Anton_Schedule Risk Assessment

  1. drpdg says:

    ALMOST, Pak Anton……. So close……. You did an AWESOME job except for one VERY important (and fatal) mistake……. What you have shown is P81% and NOT P90…..

    You are reading your Z tables incorrectly……… The PROBABILITY is NOT read on the left column….. You see where you have 0.8159? Well you need to look down a couple of rows and find 0.89973 and 0.90147. Then matching them up, you can see that in order to get a P90. you need between 1.28 and 1.29 sigma. What you are proposing is 0.9 sigma which is totally wrong…..

    You need to make this 5 minute fix and REPOST as W12.3……….. BUT, I can only urge you to take the time to ASK FOR HELP from some of your team members…….. Eli, Bu Lita, Delano, Pak Agus……. There are PLENTY of team members who understand how to use these tables and if you would only take the time to ask one of them to help you BEFORE you publish your blog, it would avoid a lot of malu, not to mention wasted time and effort on your part……..

    Other than that one very big error, the rest of your blog looked fine!!!

    Dr. PDG, Jakarta

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s