<?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: Work Naked.</title>
	<atom:link href="http://www.implementingscrum.com/2007/04/02/work-naked/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.implementingscrum.com/2007/04/02/work-naked/</link>
	<description>Starting Tough Conversations about Software Development</description>
	<lastBuildDate>Wed, 18 Jan 2012 21:57:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: mvizdos</title>
		<link>http://www.implementingscrum.com/2007/04/02/work-naked/comment-page-1/#comment-3544</link>
		<dc:creator>mvizdos</dc:creator>
		<pubDate>Wed, 18 Jan 2012 18:18:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.implementingscrum.com/blog/2007/04/02/work-naked/#comment-3544</guid>
		<description>Hi Gustavo,

Thanks for the comment.  If you are really using Scrum -- and your bosses are buying into it -- try to have a conversation with them about keeping the time and budget fixed.  Then, talk about Scope.  As you start delivering what you commit to (as a Scrum Team), these questions usually go away.  Ironically people hear Scrum and want it better - cheaper - faster and that is not the case.  Tough Conversation.  Good luck!

</description>
		<content:encoded><![CDATA[<p>Hi Gustavo,</p>
<p>Thanks for the comment.  If you are really using Scrum &#8212; and your bosses are buying into it &#8212; try to have a conversation with them about keeping the time and budget fixed.  Then, talk about Scope.  As you start delivering what you commit to (as a Scrum Team), these questions usually go away.  Ironically people hear Scrum and want it better &#8211; cheaper &#8211; faster and that is not the case.  Tough Conversation.  Good luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gustavo</title>
		<link>http://www.implementingscrum.com/2007/04/02/work-naked/comment-page-1/#comment-3502</link>
		<dc:creator>Gustavo</dc:creator>
		<pubDate>Thu, 12 Jan 2012 20:28:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.implementingscrum.com/blog/2007/04/02/work-naked/#comment-3502</guid>
		<description>Hi, these posts are great. I&#039;m from Argentina and I&#039;m tryinig to implement SCRUM (or something like that) in my organization.

The question that comes up as soon as i read articles about the Scrum Master Role is this: how do you keep your company bosses and owners quiet regarding the &quot;control&quot; over the times &quot;planned&quot; and &quot;comitted&quot; releases? I know this is not a &quot;scrum question&quot; but it would be great to know how can i manage this situations as a scrum master &quot;ex PMBOK project manager&quot;. Thanks</description>
		<content:encoded><![CDATA[<p>Hi, these posts are great. I&#8217;m from Argentina and I&#8217;m tryinig to implement SCRUM (or something like that) in my organization.</p>
<p>The question that comes up as soon as i read articles about the Scrum Master Role is this: how do you keep your company bosses and owners quiet regarding the &#8220;control&#8221; over the times &#8220;planned&#8221; and &#8220;comitted&#8221; releases? I know this is not a &#8220;scrum question&#8221; but it would be great to know how can i manage this situations as a scrum master &#8220;ex PMBOK project manager&#8221;. Thanks</p>
]]></content:encoded>
	</item>
</channel>
</rss>

