<?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: Step 6: Sprint!</title>
	<atom:link href="http://www.allaboutagile.com/how-to-implement-scrum-in-10-easy-steps-step-6-sprint/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.allaboutagile.com/how-to-implement-scrum-in-10-easy-steps-step-6-sprint/</link>
	<description>Agile Development Made Easy!</description>
	<lastBuildDate>Sun, 19 May 2013 08:16:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: About pictures</title>
		<link>http://www.allaboutagile.com/how-to-implement-scrum-in-10-easy-steps-step-6-sprint/#comment-134</link>
		<dc:creator>About pictures</dc:creator>
		<pubDate>Wed, 24 Oct 2007 14:02:00 +0000</pubDate>
		<guid isPermaLink="false">http://allaboutagile.com/uncategorized/how-to-implement-scrum-in-10-easy-steps-step-6-sprint/#comment-134</guid>
		<description><![CDATA[I think SCRUM is great in many ways and we can benefit from this management practise but there might also be some confusions and wrong assumptions about it.&lt;br/&gt;If I had to prepare a list, I would tell the list below. These are not true of course but people might be thinking or practising them.&lt;br/&gt;- SCRUM is an agile process for everything including engineering practises.&lt;br/&gt;- Having the product backlog is enough for development and requirement gathering is not something in SCRUM&lt;br/&gt;- Develop as much as possible; don’t need to leave much time for analysis&lt;br/&gt;- Writing test methods is very heavy and cannot be afforded to spend time for it&lt;br/&gt;- Develop first, change it later approach might start to happen&lt;br/&gt;- Giving exact estimates for tasks and not to rest the development team over the sprints or between the tasks.&lt;br/&gt;- Short SCRUM meetings are everyday but the teams might be missing longer meetings needed with more technical details&lt;br/&gt;- Unplanning becomes the agile process itself.&lt;br/&gt;- Estimates for a very similar task become different among the development teams]]></description>
		<content:encoded><![CDATA[<p>I think SCRUM is great in many ways and we can benefit from this management practise but there might also be some confusions and wrong assumptions about it.<br />If I had to prepare a list, I would tell the list below. These are not true of course but people might be thinking or practising them.<br />- SCRUM is an agile process for everything including engineering practises.<br />- Having the product backlog is enough for development and requirement gathering is not something in SCRUM<br />- Develop as much as possible; don’t need to leave much time for analysis<br />- Writing test methods is very heavy and cannot be afforded to spend time for it<br />- Develop first, change it later approach might start to happen<br />- Giving exact estimates for tasks and not to rest the development team over the sprints or between the tasks.<br />- Short SCRUM meetings are everyday but the teams might be missing longer meetings needed with more technical details<br />- Unplanning becomes the agile process itself.<br />- Estimates for a very similar task become different among the development teams</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Artem Marchenko</title>
		<link>http://www.allaboutagile.com/how-to-implement-scrum-in-10-easy-steps-step-6-sprint/#comment-133</link>
		<dc:creator>Artem Marchenko</dc:creator>
		<pubDate>Sun, 21 Oct 2007 20:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://allaboutagile.com/uncategorized/how-to-implement-scrum-in-10-easy-steps-step-6-sprint/#comment-133</guid>
		<description><![CDATA[While I fully agree that the teams must be empowered, I also believe that in quite many organizational contexts teams just starting Scrum might not know what to do with this power. &lt;br/&gt;&lt;br/&gt;It is certainly a Scrum Master responsibility to help them learn. During the transitional it might be a good idea to tell the team what other teams find useful in the similar situations. Whenever people start something new, some amount of instructions in the beginning can be not just useful, but even welcome. Though it&#039;s sometimes tough to include exactly as much recommendations as team is eager to take without feeling a command&#039;n&#039;controlled one.]]></description>
		<content:encoded><![CDATA[<p>While I fully agree that the teams must be empowered, I also believe that in quite many organizational contexts teams just starting Scrum might not know what to do with this power. </p>
<p>It is certainly a Scrum Master responsibility to help them learn. During the transitional it might be a good idea to tell the team what other teams find useful in the similar situations. Whenever people start something new, some amount of instructions in the beginning can be not just useful, but even welcome. Though it&#8217;s sometimes tough to include exactly as much recommendations as team is eager to take without feeling a command&#8217;n'controlled one.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
