REG NASA-LLIS-1560--2005 Lessons Learned Management Reviews Reporting and Technical Publications.pdf

1、Lessons Learned Entry: 1560Lesson Info:a71 Lesson Number: 1560a71 Lesson Date: 2005-01-01a71 Submitting Organization: ARCa71 Submitted by: Ronald C. Winterlina71 Authored by: Ronald C. WinterlinSubject: Management Reviews, Reporting and Technical Publications Abstract: A- Reviews: General feedback r

2、eceived from all levels of project participants- There are too many reviews without clear definition of their purpose. As a result, reviews tended to overlap in their charters and often provided conflicting recommendations. Those involved in projects would be more motivated to support reviews if the

3、y could see and experience distinct and valuable purposes that each review served. Independent review committees are not slowed (or do not take) adequate review time to understand the projects work, accomplishments, etc. and alignment with schedule and budget. As a result, many of the findings are i

4、ncorrect or misleading as a result of misunderstandings or lack of knowledge about the project. B- Reporting: General feedback received Too much disconnected upward reporting with little downward direction where the Program and/or Headquarters express direct interest or understanding in the work of

5、the project and helping to make it successful. AATT spent a lot of time and resources dealing with high-level issues throughout the life of the project. C- Technical Publications: The AATT Project Office made a special point to request and remind technical and sub-project managers that project recog

6、nition be appropriately documented in technical publications. This was a recurring problem throughout the 9-year life of the project. Description of Driving Event: Additional Key Words: AATT, Reviews, Reporting, General Feedback, Technical Publications, Schedule, Budget Provided by IHSNot for Resale

7、No reproduction or networking permitted without license from IHS-,-,-Lesson(s) Learned: Too many reviews and reports that often times are repetitive and redundant providing the same information in different formats to different managers and teams, is costly in time, resources and moral. Every minute

8、 taken to put together and prepare huge packages of information that does not seem to be read and/or understood, takes away from a managers time and resources to assure the work of the project is successfully accomplished. Recommendation(s): A. It is recommended that there be fewer independent revie

9、ws, each with more time allotted to the project under review. There should be adequate time provided for discussion of the draft findings with the project manager, for a feedback loop that may lead to the committee modifying or refining its findings. Related to the above is up-front accurate communi

10、cation to the projects exactly what the reviewer wants covered in terms of content. Too often AATT Project personnel were trying to determine what the reviewers wanted to see and hear. A reasonable and practical amount of format/content standardization would be helpful in preventing waste of time an

11、d having to scramble to get what the review committee decides it really wants to see on site during the review itself. B. The obvious ideal reporting scenario is one that minimizes duplicative, redundant and multiple ways of providing the same information. A single Agency-wide reporting/information

12、system should be developed and carefully thought out with the input of those having to provide the information. Project managers should only have to deal with this kind of thing once a month (at most) and it should suffice for all organizations and levels of management including Program Management C

13、ouncils. The only thing that might be different is the level of detail, but in no case should detailed project level information be required that is not really necessary for upper level managers to have. This becomes micro-management at its worst and can result in inefficient waste of scarce resourc

14、es and time. Project managers usually end up spending valuable time away from managing their projects in order to answer questions and explain to those not knowledgeable or involved in the specific needsand day-to-day operations of the projects work. C. The AATT Project recommends that project recog

15、nition in publications be brought up and made a written policy to all involved individuals and managers from the very beginning. The appropriate standards, including place and format should be discussed and agreed to as part of this policy arrangement. The AATT Project also recommends that future pr

16、ojects have a common process and format for technical documents to ensure easy retrieval from a database. A simple summary sheet and key words similar tot the Report Documentation Page, as specified in NASA Publications Guide for Authors, NASA/SP -1999-7602, November 1999, is proposed. Provided by I

17、HSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Evidence of Recurrence Control Effectiveness: NA Documents Related to Lesson: N/AMission Directorate(s): N/AAdditional Key Phrase(s): a71 Air-Traffic Managementa71 Configuration Managementa71 Facilitiesa71 Independent Verification and Validationa71 Policy & Planninga71 Program and Project ManagementAdditional Info: Approval Info: a71 Approval Organization: ARCProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-