Show simple item record

Lessons Learned - Streamlining and Standardizing Project Planning Documents (prepared during formulation and into implementation phases)

contributor authorNASA - National Aeronautics and Space Administration (NASA)
date accessioned2017-09-04T17:53:39Z
date available2017-09-04T17:53:39Z
date copyright01/01/2005
date issued2005
identifier otherFFCAQCAAAAAAAAAA.pdf
identifier urihttp://yse.yabesh.ir/std/handle/yse/176827
description abstractAbstract:
Advanced Air Transportation Technologies (AATT) was a nine-year effort and experienced significant changes in documentation requirements from Headquarters and the lead center. This had an effect on the policies, procedures, formats, and content for project planning and formulation documents including the program, project and sub-project plans (or IBPDs), along with related other agreements and supportive plans (e.g. Program Commitment Agreements, Risk Management/ Mitigation Plans, Tech Transfer Plans, etc.) Examples include everything from title and formatting changes to basic content requirements including the program and project Work Breakdown Structure (WBS):
The WBS continues to be a key tool that is recognized as being one of the most important basic "building blocks" around which a program and project(s) should be developed. Its potential for being the central "structure", providing the basis for successful financial and Earned Value management and control, along with project metrics, technical and performance tracking, and schedule development cannot be denied. AATT experienced confusing and sometimes unclear guidance regarding the best way to develop a WBS for projects focused on concept exploration and development and demonstration. Both NASA and private sector training provide theory and emphasize the key role and importance of a good WBS, but do not provide "hands-on" real world applications and assistance in creating a WBS for these types of projects. The various types of WBS formats and approaches are offered (e.g. organizational versus product versus work, etc.), but clear guidance as to real world applications of the best approach and how to do it, within the constraints and limitations of the NASA financial management system and full cost accounting, is lacking.
languageEnglish
titleNASA-LLIS-1550num
titleLessons Learned - Streamlining and Standardizing Project Planning Documents (prepared during formulation and into implementation phases)en
typestandard
page3
statusActive
treeNASA - National Aeronautics and Space Administration (NASA):;2005
contenttypefulltext
subject keywordsProgram and Project Management


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record