1 Schedule Risk Assessment (SRA) Overview July 2013 NAVY CEVM.

Slides:



Advertisements
Similar presentations
Project Management Concepts
Advertisements

Roadmap for Sourcing Decision Review Board (DRB)
PROJECT RISK MANAGEMENT
Schedule Margin July 2013 NAVY CEVM 2 Outline Definition Program Management Perspective Background Policy/Standards Managing/monitoring Summary.
Project Management Shuffle Directions: take the definitions from the following cards and write a song using the tune from “Cupid Shuffle”
TITLE OF PROJECT PROPOSAL NUMBER Principal Investigator PI’s Organization ESTCP Selection Meeting DATE.
Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
1 EVM Policy July 2013 NAVY CEVM 2 Outline DoDI DFARS DFARS DFARS June 2012 AT&L Policy Letter.
Project Management Workshop. Nick Cook  Citigroup Corporate and Investment Bank  European Technology Business Office Manager Edinburgh University April.
Project Management.
Full Monte Cost and Schedule Risk Analysis
Project Change Management
National Aeronautics and Space Administration ANSI/EIA-748-B Earned Value Management Systems (EVMS) 32 Guidelines ANSI/EIA-748-B Earned Value.
ANSI/EIA -748 EVMS 32 Guidelines National Aeronautics and Space Administration.
1 Overview of Compliance, Surveillance, and Integrated Baseline Reviews August 2013 NAVY CEVM.
Chapter 9. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
Opportunity Engineering Harry Larsen The Boeing Company SCEA 2000 Conference.
Module 8: Risk Management, Monitoring and Project Control We would like to acknowledge the support of the Project Management Institute and the International.
Initiating and Planning Systems Development projects
Project Management Process Overview
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Chapter 11. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
I n t e g r i t y - S e r v i c e - E x c e l l e n c e Business & Enterprise Systems The Integrated Master Plan (IMP) and the Integrated Master Schedule.
8-1 Establish Cost/Schedule Performance Impacts Program Requirements Assess Risks Evaluate Risk Handling Options Evaluate Subcontractor Risks Establish.
Systems Analysis and Design in a Changing World, Fourth Edition
<Contract # or Subproject Name> IBR In-brief
Introducing Project Management Update December 2011.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design.
Project Management Basics
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
Evaluate Phase Pertemuan Matakuliah: A0774/Information Technology Capital Budgeting Tahun: 2009.
Roll the Dice with Confidence: Play to Win By Bill Carswell Adjunct Professor Embry Riddle Aeronautical University.
Managing programs that promote personal effectiveness.
Team-Based Development ISYS321 Managing the Information Systems Project.
Project Management Processes for a Project Chapter 3 PMBOK® Fourth Edition.
ILC 2007 Global Design Effort 1 Planning Damping Rings Activities in the Engineering Design Phase Andy Wolski Cockcroft Institute/University of Liverpool.
1 Chapter 8 karvaytMélKMerag nig kareFVIr)aykarN_ nig karbiTKMerag Project Evaluation, Reporting, and Termination.
SOFTWARE PROJECT MANAGEMENT
1 1 Effective Administration of Commercial Contracts Breakout Session # Session D06 Name: Holly Walker, CPCM Corporate Learning Solutions and Contract.
Develop Schedule is the Process of analyzing activity sequences, durations, resource requirements, and schedule constraints to create the project schedule.
Develop Schedule is the Process of analyzing activity sequences, durations, resource requirements, and schedule constraints to create the project schedule.
Project Management PTM721S
Principal Investigator ESTCP Selection Meeting
Chapter 11 Project Management.
ANSI/EIA-748-B Earned Value Management Systems (EVMS)
Schedule Margin July 2013 NAVY CEVM
Establishing and Managing a Schedule Baseline
Principal Investigator ESTCP Selection Meeting
Project Management Lifecycle Phases
September 2016 EVM 202—Lesson 8 Integrated Product Team (IPT) Analysis and Performance Case.
Hyper-V Cloud Proof of Concept Kickoff Meeting <Customer Name>
Mastering Change Control
Schedule Risk Assessment (SRA) Overview
Cost Health Checks NAVY CEVM
Schedule Risk Assessment (SRA) Overview
Schedule Margin July 2013 NAVY CEVM
Schedule Risk Assessment (SRA) Overview
Overview of Compliance, Surveillance, and Integrated Baseline Reviews
Schedule Margin July 2013 NAVY CEVM
Principal Investigator ESTCP Selection Meeting
Cost Health Checks NAVY CEVM
Schedule Risk Assessment (SRA) Overview
Evaluating the Estimate at Completion (EAC)
Project Overview.
Time Scheduling and Project management
Project Kick-off <Customer Name> <Project Name>
Agile Project Management and Quantitative Risk Analysis
Principal Investigator ESTCP Selection Meeting
Presentation transcript:

1 Schedule Risk Assessment (SRA) Overview July 2013 NAVY CEVM

2 Outline Why is an SRA required? How does it work? Who performs the SRA? Setting the Target and Probability Reviewing the Results and Identifying Tradeoffs Documenting the Results

3 Why the SRA Requirement? With hundreds if not thousands of similar relationships in a schedule, SRA helps evaluate the probability of completing the effort by a given deadline Task 1 50% Probability Task 2 50% Probability Task 3 25% Probability

4 How Does it Work? Monte Carlo Simulation is run to determine the probability of completion for a desired SRA target milestone(s) by a desired date(s): –Completed for a specified number of iterations –Increased number of iterations increases prediction accuracy –Based upon a random sampling of outcomes bounded by user provided best case, worst case, and most likely outcomes for each task in the IMS –Individual estimate ranges are required for each critical, near critical, and high risk task. These estimates should be developed by the responsible Control Account Manager (CAM) or technical lead –Remainder of tasks may be assessed in groups or globally Results of the simulation may either be used to prompt changes in the schedule or to revise expectations and/or contract terms.

5 Who performs the SRA? The government sets the target milestone for the assessment (typically a program event) The contractor PM sets the desired probability (often with input from the government) and oversees the effort Contractor CAMs and technical leads are responsible for developing the best case, worst case, and most likely duration estimates Contractor scheduler is responsible for coordinating the effort and performing the Monte Carlo simulation. All parties participate in: Reviewing the results and correcting errors Identifying tradeoffs Documenting the results

6 Setting the Target for the SRA The government is responsibile for setting the SRA target date. The target date selected depends on the objective Typically it is recommended that both the end milestone and the current baseline be selected as SRA targets –This allows for overall optimization Examples –IBRs – End of contract and first milestone –Rolling Wave – End of contract and detailed period end milestone –OTB – End of contract

7 Setting the Probability What does the Government deem an acceptable level of risk that delivery may be late? Is the project technical, schedule, or cost driven? Typically strict schedule or cost objectives drive the probability higher. General Guidance –> 90% is not cost effective –< 50% is very risky –For most contracts, a probability of 50-80% strikes a reasonable balance between risk vs cost

8 Review the Results - Histogram This histogram plots the number of iterations which predict completion by any given date, as well as the associated probability of completion by that date

9 Review the Results – Tornado Charts Tornado Charts identify (by decreasing significance), the tasks whose duration estimates and logic are most likely to impact the target milestone completion date The two examples above demonstrate different but related metrics plotted for this purpose

10 Identifying Tradeoffs SRA analysis is an iterative process. After each simulation, the program team must identify the problem or risk areas, evaluate cost/schedule/technical tradeoffs of alternate solutions, implement the fix, and re-run the simulation until it can produce a schedule that achieves an acceptable level of probability by an acceptable completion date. Options include: –Addition of resources to enable earlier task completion –Task logic and sequencing may be reconsidered –Risk mitigation activities may be funded in order to reduce task durations –Revised expectations or contractual milestone dates

11 Documenting Results Document final probability of the target completion date Ensure the risk list is updated for any newly identified risk items and associated mitigations and ensure that the mitigation activities are properly labeled and tracked in the IMS Document any additional requested schedule refinement or adjustments to be addressed post-SRA If the SRA is conducted during initial baselining, rebaselining, or rolling wave activity, take the opportunity to baseline the results if possible

12 Point of Contact Navy Center for Earned Value Management (703)