NASA-LLIS-1564
Lessons Learned – Management Reviews, Reporting and Technical Publications
Year: 2005
Abstract: Abstract:
A. Reviews: General Feedback Received 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 they 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 project's work, accomplishments, etc. and alignment with schedule and budget. As a result, many of the findings are incorrect 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 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 recognition be appropriately documented in technical publications. This was a recurring problem throughout the 9-year life of the project.
A. Reviews: General Feedback Received 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 they 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 project's work, accomplishments, etc. and alignment with schedule and budget. As a result, many of the findings are incorrect 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 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 recognition be appropriately documented in technical publications. This was a recurring problem throughout the 9-year life of the project.
Subject: Independent Verification and Validation
Show full item record
contributor author | NASA - National Aeronautics and Space Administration (NASA) | |
date accessioned | 2017-09-04T18:39:03Z | |
date available | 2017-09-04T18:39:03Z | |
date copyright | 01/01/2005 | |
date issued | 2005 | |
identifier other | AKXCQCAAAAAAAAAA.pdf | |
identifier uri | http://yse.yabesh.ir/std;query=authoCA5893FD081D49A96159DD6EFDEC014A/handle/yse/220695 | |
description abstract | Abstract: A. Reviews: General Feedback Received 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 they 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 project's work, accomplishments, etc. and alignment with schedule and budget. As a result, many of the findings are incorrect 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 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 recognition be appropriately documented in technical publications. This was a recurring problem throughout the 9-year life of the project. | |
language | English | |
title | NASA-LLIS-1564 | num |
title | Lessons Learned – Management Reviews, Reporting and Technical Publications | en |
type | standard | |
page | 3 | |
status | Active | |
tree | NASA - National Aeronautics and Space Administration (NASA):;2005 | |
contenttype | fulltext | |
subject keywords | Independent Verification and Validation | |
subject keywords | Policy & Planning | |
subject keywords | Program and Project Management |