Show simple item record

Lessons Learned – Conflicting Requirements From Multiple Management/Customer Entities

contributor authorNASA - National Aeronautics and Space Administration (NASA)
date accessioned2017-09-04T16:49:22Z
date available2017-09-04T16:49:22Z
date copyright01/01/2002
date issued2002
identifier otherWKVEQCAAAAAAAAAA.pdf
identifier urihttps://yse.yabesh.ir/std/handle/yse/112866
description abstractDescription of Driving Event:
Often Programs/projects, especially highly visible ones, must deal with the reality of being accountable to multiple entities, such as Center Senior Staff, Headquarters/ Enterprise Management, External Partner Management (FAA, DOE, NSF, etc.) who may have conflicting requirements. In addition, the Program/project has the main responsibility of fulfilling customer requirements, which may not be entirely compatible with the direction levied by these other "bosses." Programs/projects must balance the requirements of these bosses with that of their customers. It is in the best interest of the Program/project if the customer requirements take priority over all others.
languageEnglish
titleNASA-LLIS-1285num
titleLessons Learned – Conflicting Requirements From Multiple Management/Customer Entitiesen
typestandard
page2
statusActive
treeNASA - National Aeronautics and Space Administration (NASA):;2002
contenttypefulltext
subject keywordsAdministration/Organization
subject keywordsPolicy & Planning


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record