<?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: Roles In Scrum Are Not Only For Team Members	</title>
	<atom:link href="https://www.scrumexpert.com/knowledge/roles-in-scrum-are-not-only-for-team-members/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.scrumexpert.com/knowledge/roles-in-scrum-are-not-only-for-team-members/</link>
	<description></description>
	<lastBuildDate>Tue, 22 Apr 2014 16:49:22 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Adam Russell		</title>
		<link>https://www.scrumexpert.com/knowledge/roles-in-scrum-are-not-only-for-team-members/#comment-21592</link>

		<dc:creator><![CDATA[Adam Russell]]></dc:creator>
		<pubDate>Sat, 01 Mar 2014 23:55:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=1824#comment-21592</guid>

					<description><![CDATA[I often wonder about how people expect agile in general (and scrum in the particular) to actually work if they don&#039;t follow the core practices - not slavishly, but because they understand how projects work.  

the user story structure, as simple as it is, contains three elements which are all critical to the success of the technique: persona (or type of user), goal and reason.  

Most often i see the &quot;reason&quot; being ditched, and the next item is the &quot;persona&quot;, leaving pretty much a list of features, untraceable back to whoever is asking for it, and without any particular rationale against which to determine value.

a team of people working together need a framework to guide its organisation and endeavours.  we all know how waterfall does this and the problems associated with these approaches.  in agile we replace just about all those frameworks with more humanistic and flexible techniques, but they are still needed.

why a process would work if it&#039;s not fully implemented is beyond me.]]></description>
			<content:encoded><![CDATA[<p>I often wonder about how people expect agile in general (and scrum in the particular) to actually work if they don&#8217;t follow the core practices &#8211; not slavishly, but because they understand how projects work.  </p>
<p>the user story structure, as simple as it is, contains three elements which are all critical to the success of the technique: persona (or type of user), goal and reason.  </p>
<p>Most often i see the &#8220;reason&#8221; being ditched, and the next item is the &#8220;persona&#8221;, leaving pretty much a list of features, untraceable back to whoever is asking for it, and without any particular rationale against which to determine value.</p>
<p>a team of people working together need a framework to guide its organisation and endeavours.  we all know how waterfall does this and the problems associated with these approaches.  in agile we replace just about all those frameworks with more humanistic and flexible techniques, but they are still needed.</p>
<p>why a process would work if it&#8217;s not fully implemented is beyond me.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
