UNLIMITED FREE
ACCESS
TO THE WORLD'S BEST IDEAS

SUBMIT
Already a GlobalSpec user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your GlobalSpec Experience

Finish!
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

NASA-LLIS-1285

Lessons Learned – Conflicting Requirements From Multiple Management/Customer Entities

active, Most Current
Organization: NASA
Publication Date: 1 January 2002
Status: active
Page Count: 2
scope:

Description 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.

Document History

NASA-LLIS-1285
January 1, 2002
Lessons Learned – Conflicting Requirements From Multiple Management/Customer Entities
Description 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,...
Advertisement