<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>PMServicesNW &#187; project constraints</title>
	<atom:link href="http://www.pmservicesnw.com/tag/project-constraints/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pmservicesnw.com</link>
	<description>Free project management information and downloads</description>
	<lastBuildDate>Tue, 03 May 2011 02:22:21 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
		<item>
		<title>Competing Project Constraints</title>
		<link>http://www.pmservicesnw.com/2010/12/competing-project-constraints/</link>
		<comments>http://www.pmservicesnw.com/2010/12/competing-project-constraints/#comments</comments>
		<pubDate>Thu, 30 Dec 2010 05:01:10 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Project Management]]></category>
		<category><![CDATA[competing project constaints]]></category>
		<category><![CDATA[project constraints]]></category>
		<category><![CDATA[triple triangle]]></category>

		<guid isPermaLink="false">http://www.pmservicesnw.com/?p=2289</guid>
		<description><![CDATA[By Ray Myers, Jr., PMP Schedule, Scope and Budget are the traditional competing project constraints.  Some project managers have added Quality as a fourth 4 constraint.  But PMBOK changed that by stating anything that limits the team’s option.  (PMBOK V4 paragraph 5.2.3.1) Here are a few examples of competing project constraints: Scope Quality Time Cost Resources Stakeholder requirements and expectations Identified needs &#8211; requirements Unidentified needs &#8211; expectations Contractual provisions Imposed dates Predefined budgets Imposed dates About the Author: Ray Myers, Jr. is a PMP certified project manager with over 20 years’ experience planning and managing technology projects.  Contact Ray at www.pmservicesnw.com Article source: www.pmservicesnw.com &#169;2012 PMServicesNW. All Rights Reserved..]]></description>
		<wfw:commentRss>http://www.pmservicesnw.com/2010/12/competing-project-constraints/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Project Constraints Redefined</title>
		<link>http://www.pmservicesnw.com/2010/10/project-constraints-redefined/</link>
		<comments>http://www.pmservicesnw.com/2010/10/project-constraints-redefined/#comments</comments>
		<pubDate>Fri, 22 Oct 2010 10:12:29 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Project Management]]></category>
		<category><![CDATA[project constraints]]></category>
		<category><![CDATA[project constraints redefined]]></category>
		<category><![CDATA[project triange]]></category>
		<category><![CDATA[updated project constraints]]></category>

		<guid isPermaLink="false">http://www.pmservicesnw.com/?p=43</guid>
		<description><![CDATA[By: Ray Myers, Jr., PMP Traditionally, project managers have managed projects using the triple constraints of scope, time, or cost, where scope refers to what must be done to produce the project deliverables, time refers to the time available to complete the project, and cost refers to budget allocated to complete the project.  These constraints are called the project triangle.  Scope, time and cost are competing constraints because a change to one of the three often throws the other legs of the triangle out of balance.  For example, increasing scope may increase the cost or time needed to complete the project. Many project managers when asked if they could make changes to the project assumptions, would typically respond with something like, “we have scope, time, and cost, choose 2, you can’t have all 3,” or “which two do you want.”  Quality, a fourth constraint, was added to the triangle and refers to how closely the project deliverables conform to the documented scope.  So the project triangle became four-sided and would usually be drawn something like this:     Figure 1 The Project Triangle The long-established project triangle has now been redefined by the Fourth Edition of the Project Management Institute’s [...]]]></description>
		<wfw:commentRss>http://www.pmservicesnw.com/2010/10/project-constraints-redefined/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

