Project Objective

From Risk Engineering
Revision as of 15:01, 29 November 2025 by Pooyan (talk | contribs) (Restored “Project Objective” from archived RiskEngineering.org (Wayback, 2017).)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Basic considerations

Given the discussion on requirements, the question arises as to what is the relationship between project requirements and project objectives?

PMIBoK

PMI defines "objective" as:

"Something toward which work is to be directed, a strategic position to be attained, a purpose to be achieved, a result to be obtained, a product to be produced, or a service to be performed."

(PMBOK® Guide, p. 575)

ISO

(Under construction.)

Limitations of the definition

(Under construction.)

Working definition of the term

Conditions or capabilities in the form of material assumptions, dependencies, and constraints that are to be met by the project or present in the product, service, or result to satisfy an agreement or other formally imposed specification and includes the needs and expectations of the project sponsor, customer, and other stakeholders in adequate and detailed quantification and documentation to be totally satisfactory as a basis for establishing the project scope baseline and to be measured once project execution begins.
(What documentation issues are there?)

See also

Wiki article on Project management.

Notes

(Under construction.)