• Is able to identify and explain how risks can be identified, quantified and how this information be incorporated into the CPM schedule
• Be able to explain how Monte Carlo simulations works and be able to read and understand the outputs from a Monte Carlo simulation
• Be able to explain the difference between risk and uncertainty and how both can be incorporated into a project plan through choosing the appropriate logic or modifying the existing logic
• Be able to define what "Merge Bias" is, how it is calculated, and how to measure or assess the impact of merge bias

• Is able to identify and explain how risks can be identified, quantified and how this information be incorporated into the CPM schedule
• Be able to explain how Monte Carlo simulations works and be able to read and understand the outputs from a Monte Carlo simulation
• Be able to explain the difference between risk and uncertainty and how both can be incorporated into a project plan through choosing the appropriate logic or modifying the existing logic
• Be able to define what "Merge Bias" is, how it is calculated, and how to measure or assess the impact of merge bias

• Can identify and explain the various types of interfaces that can and do exist between work packages and activities to ensure that we have horizontal traceability
• Can identify and explain the various tools/techniques that we can use between work packages and activities to ensure that we have vertical traceability and that our schedules can "roll up" or "roll down" without losing activities or work packages

Can identify and explain the various types of interfaces that can and do exist between work packages and activities to ensure that we have horizontal traceability

Can identify and explain the various tools/techniques that we can use between work packages and activities to ensure that we have vertical traceability and that our schedules can "roll up" or "roll down" without losing activities or work packages

• Can identify and explain the various types of interfaces that can and do exist between work packages and activities to ensure that we have horizontal traceability
• Can identify and explain the various tools/techniques that we can use between work packages and activities to ensure that we have vertical traceability and that our schedules can "roll up" or "roll down" without losing activities or work packages

• Can identify and explain the various types of interfaces that can and do exist between work packages and activities to ensure that we have horizontal traceability
• Can identify and explain the various tools/techniques that we can use between work packages and activities to ensure that we have vertical traceability and that our schedules can "roll up" or "roll down" without losing activities or work packages

• Be able to define what a "reliable" schedule looks like, what attributes can or should be used as a quality assurance/quality control function and what  "best tested and proven" standards should we be adopting
• Be able to define and explain the various tools/techniques and how to use them to validate the critical path and completion dates
• Be able to define and explain what tools/techniques can be used to optimize a schedule in terms of time, cost and/or resource utilization
• Is able to identify and explain the various type of constraints that can be imposed,

• Be able to define what a "reliable" schedule looks like, what attributes can or should be used as a quality assurance/quality control function and what  "best tested and proven" standards should we be adopting
• Be able to define and explain the various tools/techniques and how to use them to validate the critical path and completion dates
• Be able to define and explain what tools/techniques can be used to optimize a schedule in terms of time, cost and/or resource utilization
• Is able to identify and explain the various type of constraints that can be imposed,

• Be able to define what a "reliable" schedule looks like, what attributes can or should be used as a quality assurance/quality control function and what  "best tested and proven" standards should we be adopting
• Be able to define and explain the various tools/techniques and how to use them to validate the critical path and completion dates
• Be able to define and explain what tools/techniques can be used to optimize a schedule in terms of time, cost and/or resource utilization
• Is able to identify and explain the various type of constraints that can be imposed,

• Be able to define what a "reliable" schedule looks like, what attributes can or should be used as a quality assurance/quality control function and what  "best tested and proven" standards should we be adopting
• Be able to define and explain the various tools/techniques and how to use them to validate the critical path and completion dates
• Be able to define and explain what tools/techniques can be used to optimize a schedule in terms of time, cost and/or resource utilization
• Is able to identify and explain the various type of constraints that can be imposed,