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

加入VIP,免费下载
 

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

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

下载须知

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

版权提示 | 免责声明

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

REG NASA-LLIS-1554- Lessons Learned AATT Project.pdf

1、Lessons Learned Entry: 1554Lesson Info:a71 Submitting Organization: ARCAbstract: A number of times, the AATT Project was directed to add, delete, and/or change the projects focus of research, not only on existing agreed-to ATM products (tools and concepts), but in some cases, change of direction to

2、develop totally new tools. It is understood that flexibility in research must be maintained in order that concepts that do not prove worthwhile can be dropped allowing for focus and priority shifts to more promising ones. However, both realistic and reasonable controls on project scope and priority

3、setting must be maintained to assure prudent management planning and decision-making. Excessive control and redirection of focus/priorities late into a projects life leads to wasteful use of resources and hampers the projects ability to manage and deliver effectively. Significant changes well into t

4、he implementation phase can be very costly as contractual planning and funds obligations limit the scope and/or task requirement changes that can be made after the fact. Directly related to the above is what we refer to as “milestone creep”. Project management shifts, along with changing (sometimes

5、mandated) project priorities, resulted in too many milestones that grew in number all the way into the last trimester of the project. This also made it difficult to adhere to a uniform, consistent milestone organization and management system, resulting in some sub-projects with many more milestones

6、and resultant work than others and the milestones becoming somewhat jumbled and not following the most logical sequencing. This caused a significant amount of work to support programmatic/administrative management, documentation and configuration control, tracking, etc. across organizations (includi

7、ng 3 centers and multiple directorates and divisions). Description of Driving Event: This is no single “driving event.“ Lesson(s) Learned: It is easy to lose sight of the big picture and overall historical evolution with continual guidance to change direction/focus and/or project deliverables and re

8、lated milestones. A strong Systems Management function will go a long way to maintain this perspective and advise management accordingly. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Recommendation(s): Upper level management at Program, Center and

9、 Headquarters levels need to “control” the tendency to pass down mandatory shifts in project research work and deliverables after a project has gone thru formulation and is going into implementation. They need to remember and respect that the whole Program/Project Management process in NASA is based

10、 on detailed planning during formulation phase way before a project receives the “go head” after a successful Non-advocate Review (NAR). The budgets, resource commitments and procurement planning and strategy are all negatively impacted when such significant changes in direction and focus occur. Thi

11、s is costly, inefficient and can result in significant waste of scarce project resources to deliver what they signed up to deliver. Project managers and their support staff need to be sensitive to “Milestone Creep” and make a concerted effort to carefully plan and control from the beginning in order

12、 to maintain manageable milestones that efficiently represent at the appropriate level, work accomplished for products and deliverables. Carefully thought-out identification and definition of each product and/or supportive milestones/deliverables will go a long way in this effort. Maintaining a clea

13、r distinction and cross walk relationship between these is also very important. Evidence of Recurrence Control Effectiveness: N/ADocuments Related to Lesson: N/AMission Directorate(s): N/AAdditional Key Phrase(s): N/AAdditional Info: Approval Info: Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-

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