ImageVerifierCode 换一换
格式:PDF , 页数:3 ,大小:14.92KB ,
资源ID:1018980      下载积分:10000 积分
快捷下载
登录下载
邮箱/手机:
温馨提示:
如需开发票,请勿充值!快捷下载时,用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)。
如填写123,账号就是123,密码也是123。
特别说明:
请自助下载,系统不会自动发送文件的哦; 如果您已付费,想二次下载,请登录后访问:我的下载记录
支付方式: 支付宝扫码支付 微信扫码支付   
注意:如需开发票,请勿充值!
验证码:   换一换

加入VIP,免费下载
 

温馨提示:由于个人手机设置不同,如果发现不能下载,请复制以下地址【http://www.mydoc123.com/d-1018980.html】到电脑端继续下载(重复下载不扣费)。

已注册用户请登录:
账号:
密码:
验证码:   换一换
  忘记密码?
三方登录: 微信登录  

下载须知

1: 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。
2: 试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。
3: 文件的所有权益归上传用户所有。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 本站仅提供交流平台,并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

版权提示 | 免责声明

本文(REG NASA-LLIS-1341-2003 Lessons Learned Risk Management Lack of a Formal Risk Management Plan (RMP) and Process.pdf)为本站会员(terrorscript155)主动上传,麦多课文库仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文库(发送邮件至master@mydoc123.com或直接QQ联系客服),我们立即给予删除!

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

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-,-,-

copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
备案/许可证编号:苏ICP备17064731号-1