REG NASA-LLIS-1567--2005 Lessons Learned Stability of Project Technical Content Focus and Milestone Creep.pdf

《REG NASA-LLIS-1567--2005 Lessons Learned Stability of Project Technical Content Focus and Milestone Creep.pdf》由会员分享，可在线阅读，更多相关《REG NASA-LLIS-1567--2005 Lessons Learned Stability of Project Technical Content Focus and Milestone Creep.pdf（3页珍藏版）》请在麦多课文档分享上搜索。

1、Lessons Learned Entry: 1567Lesson Info:a71 Lesson Number: 1567a71 Lesson Date: 2005-05-24a71 Submitting Organization: ARCa71 Authored by: Ronald. C. WinterlinSubject: Stability of Project Technical Content/Focus and Milestone Creep Abstract: A number of times, the Advanced Air Transportation Technol

2、ogies (AATT) Project was directed to add, delete, and/or change the project focus of research, not only on existing agreed-to ATM products (tools and concepts), but in some cases, change of direction to develop totally new tools. It is understood that flexibility in research must be maintained in or

3、der 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 setting must be maintained to assure prudent management planning and decision-making. Excessive c

4、ontrol 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 the implementation phase can be very costly as contractual planning and funds obligations limit th

5、e scope and/or task requirement changes that can bemade after the fact. Directly related to the above is what we refer to as milestone creep. Project management shifts, along with changing (sometimes mandated) project priorities, resulted in too many milestones that grew in number all the way into t

6、he 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 and resultant work than others and the milestones becoming somewhat jumbled and not following the mo

7、st logical sequencing. This caused a significant amount of work to support programmatic/administrative management, documentation and configuration control, tracking, etc. across organizations (including 3 centers and multiple directorates and divisions). Description of Driving Event: There is no sin

8、gle “driving event.” Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-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 rel

9、ated milestones. A strong Systems Management function will go a long was to maintain this perspective and advise management accordingly. Recommendation(s): Upper level management at Program, Center and Headquarters levels need to control the tendency to pass down mandatory shifts in project research

10、 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 on detailed planning during formulation phase way before a project receives the go-ahead after a suc

11、cessful 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. This is costly, inefficient and can result in significant waste of scarce project resources to deliver wh

12、at 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 to maintain manageable milestones that efficiently represent at the appropriate level, work accomplishe

13、d 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 clear distinction and crosswalk relationship between these is also very important. Evidence of Recurrence Co

14、ntrol Effectiveness: N/ADocuments Related to Lesson: NPG 7120.5Mission Directorate(s): a71 Exploration Systemsa71 Sciencea71 Aeronautics Researcha71 Space OperationsAdditional Key Phrase(s): Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-a71 Air-Tra

15、ffic Managementa71 Aircrafta71 Risk Management/Assessmenta71 Safety & Mission AssuranceAdditional Info: Approval Info: a71 Approval Date: 2006-06-30a71 Approval Name: tmasona71 Approval Organization: HQProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-