<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://riskengineering.org/index.php?action=history&amp;feed=atom&amp;title=Project_Objective</id>
	<title>Project Objective - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://riskengineering.org/index.php?action=history&amp;feed=atom&amp;title=Project_Objective"/>
	<link rel="alternate" type="text/html" href="https://riskengineering.org/index.php?title=Project_Objective&amp;action=history"/>
	<updated>2026-09-15T08:54:18Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.42.3</generator>
	<entry>
		<id>https://riskengineering.org/index.php?title=Project_Objective&amp;diff=245&amp;oldid=prev</id>
		<title>Pooyan: Restored “Project Objective” from archived RiskEngineering.org (Wayback, 2017).</title>
		<link rel="alternate" type="text/html" href="https://riskengineering.org/index.php?title=Project_Objective&amp;diff=245&amp;oldid=prev"/>
		<updated>2025-11-29T19:01:01Z</updated>

		<summary type="html">&lt;p&gt;Restored “Project Objective” from archived RiskEngineering.org (Wayback, 2017).&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;== Basic considerations ==&lt;br /&gt;
&lt;br /&gt;
Given the discussion on requirements, the question arises as to what is the relationship between project requirements and project objectives?&lt;br /&gt;
&lt;br /&gt;
=== PMIBoK ===&lt;br /&gt;
&lt;br /&gt;
PMI defines &amp;quot;objective&amp;quot; as:&lt;br /&gt;
&lt;br /&gt;
:&amp;quot;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.&amp;quot;  &lt;br /&gt;
(PMBOK® Guide, p. 575)&lt;br /&gt;
&lt;br /&gt;
=== ISO ===&lt;br /&gt;
&lt;br /&gt;
(Under construction.)&lt;br /&gt;
&lt;br /&gt;
== Limitations of the definition ==&lt;br /&gt;
&lt;br /&gt;
(Under construction.)&lt;br /&gt;
&lt;br /&gt;
== Working definition of the term ==&lt;br /&gt;
&lt;br /&gt;
: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.&lt;br /&gt;
&lt;br /&gt;
:(What documentation issues are there?)&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
&lt;br /&gt;
Wiki article on [[wikipedia:Project_management|Project management]].&lt;br /&gt;
&lt;br /&gt;
== Notes ==&lt;br /&gt;
&lt;br /&gt;
(Under construction.)&lt;br /&gt;
&lt;br /&gt;
[[Category:Definition]]&lt;/div&gt;</summary>
		<author><name>Pooyan</name></author>
	</entry>
</feed>