<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
	>
<channel>
	<title>Comments on: Managing Project Scope</title>
	<atom:link href="http://www.pmhut.com/managing-project-scope-2/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/managing-project-scope-2</link>
	<description></description>
	<pubDate>Wed, 23 May 2012 15:21:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Steven Levy</title>
		<link>http://www.pmhut.com/managing-project-scope-2/comment-page-1#comment-16484</link>
		<dc:creator>Steven Levy</dc:creator>
		<pubDate>Fri, 05 Feb 2010 02:01:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4741#comment-16484</guid>
		<description>It's great to see recognition that -- especially in s/w projects -- scope changes are both a matter of course and not always anathema. It's not uncommon that as you learn more in an area where you cannot know it all at the start, scope will need to change. Bad PMs resist without investigating the ROI or cost/benefit analysis of change; it's a sign they're more concerned with personal project stats than delivering value. (Other bad PMs, of course, never learn to say No.) Good PMs -- perhaps it comes with maturity -- understand that scope changes are themselves part of the flow and build a plan to deal with them in a way that most benefits the customers, whether that means deferring a change, adding it, or trading something else out for it.
  -- Steven B. Levy
     Author, &lt;a href="https://www.createspace.com/3413940" rel="nofollow"&gt;&lt;em&gt;Legal Project Management: Control Costs, Meet Schedules, Manage Risks, and Maintain Sanity&lt;/em&gt;&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>It&#8217;s great to see recognition that &#8212; especially in s/w projects &#8212; scope changes are both a matter of course and not always anathema. It&#8217;s not uncommon that as you learn more in an area where you cannot know it all at the start, scope will need to change. Bad PMs resist without investigating the ROI or cost/benefit analysis of change; it&#8217;s a sign they&#8217;re more concerned with personal project stats than delivering value. (Other bad PMs, of course, never learn to say No.) Good PMs &#8212; perhaps it comes with maturity &#8212; understand that scope changes are themselves part of the flow and build a plan to deal with them in a way that most benefits the customers, whether that means deferring a change, adding it, or trading something else out for it.<br />
  &#8212; Steven B. Levy<br />
     Author, <a href="https://www.createspace.com/3413940" rel="nofollow"><em>Legal Project Management: Control Costs, Meet Schedules, Manage Risks, and Maintain Sanity</em></a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

