REG NASA-LLIS-1341-2003 Lessons Learned Risk Management Lack of a Formal Risk Management Plan (RMP) and Process.pdf

《REG NASA-LLIS-1341-2003 Lessons Learned Risk Management Lack of a Formal Risk Management Plan (RMP) and Process.pdf》由会员分享，可在线阅读，更多相关《REG NASA-LLIS-1341-2003 Lessons Learned Risk Management Lack of a Formal Risk Management Plan (RMP) and Process.pdf（3页珍藏版）》请在麦多课文档分享上搜索。

1、Lessons Learned Entry: 1341Lesson Info:a71 Lesson Number: 1341a71 Lesson Date: 2003-01-01a71 Submitting Organization: ARCa71 Submitted by: Donald R. MendozaSubject: Risk Management: Lack of a Formal Risk Management Plan (RMP) and Process Description of Driving Event: The Project was required to deve

2、lop and deliver a major scientific instrument. However, the team was predominately made up by a small group of research scientists and engineers such that most of their planning and management experience had been gained while working on academic type activities in which the main deliverables were da

3、ta and research publications. While several members did have experience with other instruments, including a similar one used on a previous project, they had never developed an instrument of the required size nor had they developed anything requiring FAA flight certification. Thus there were signific

4、ant knowledge gaps that were not addressed during the Projects formulation and implementation phases. The situation was made worse since none of the Project personnel had any formal training or experience in risk management and did not have adequate Center support/oversight to aid the risk reduction

5、 process. The original proposal identified major technical risks and described corresponding risk mitigation plans. However, the project did not develop a formal Risk Management Plan (RMP) or a process to identify their risks and corresponding mitigation philosophies.As a result, the Project operate

6、d in a reactionary mode rather than a strategic one and was cancelled after it became clear it was not going to meet its programmatic requirements within a reasonably enlarged budget.Lesson(s) Learned: The Project learned that without a risk management process and accompanying plan:1. Knowledge gaps

7、 in a project will be unknown.2. The uncertainty in a projects schedule and budget will not be known to sufficient accuracy.3. A project will not have adequate information/policies to prioritize its requirements, develop Provided by IHSNot for ResaleNo reproduction or networking permitted without li

8、cense from IHS-,-,-descope plans, and quantify the consequences of their proposed control measures. Therefore a project will have considerable difficulty gaining support from its stakeholders when deviations from the baseline plan occur.Recommendation(s): 1. Start risk management planning as early a

9、s possible and ensure that it is implemented throughout the projects life cycle. The uncertainty and knowledge gaps associated with the project should be captured in the RMP such that an accurate assessment of the projects risk can be made.2. Enlist the expertise of other Center resources such as th

10、e System Safety & Mission Assurance, Systems Management, Acquisitions, and Resource Management organizations to help minimize project knowledge gaps and identify risk.3. Ensure the RMP defines top-level metrics that can be used to assess the effectiveness, efficiency, and collateral consequences of

11、risk management efforts. These metrics along with those identified for each specific risk should be used as tools to gain stakeholder support when trying to maintain the projects baseline against problems or especially when trying to adjust the projects baseline.4. The RMP should be used to ensure a

12、ll stakeholders are aware of the consequences of actions taken to manage the project.5. The project should not be approved for Implementation if theres no RMP and active process in place.6. Evidence of Recurrence Control Effectiveness: N/ADocuments Related to Lesson: N/AMission Directorate(s): a71 E

13、xploration Systemsa71 Sciencea71 Space Operationsa71 Aeronautics ResearchAdditional Key Phrase(s): a71 Risk Management/AssessmentProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Additional Info: Approval Info: a71 Approval Date: 2003-07-18a71 Approval Name: Andrew Hockera71 Approval Organization: ARCa71 Approval Phone Number: 650-604-4120Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-