<?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: Outcomes and Sync Steps</title>
	<atom:link href="http://availagility.co.uk/2009/11/05/outcomes-and-sync-steps/feed/" rel="self" type="application/rss+xml" />
	<link>http://availagility.co.uk/2009/11/05/outcomes-and-sync-steps/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=outcomes-and-sync-steps</link>
	<description>Karl Scotland - Using Agile to Deliver Value</description>
	<lastBuildDate>Mon, 14 May 2012 03:22:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Karl</title>
		<link>http://availagility.co.uk/2009/11/05/outcomes-and-sync-steps/comment-page-1/#comment-367</link>
		<dc:creator>Karl</dc:creator>
		<pubDate>Tue, 10 Nov 2009 12:24:35 +0000</pubDate>
		<guid isPermaLink="false">http://availagility.co.uk/?p=437#comment-367</guid>
		<description>Thanks Rowan :)</description>
		<content:encoded><![CDATA[<p>Thanks Rowan <img src='http://availagility.co.uk/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rowan Bunning</title>
		<link>http://availagility.co.uk/2009/11/05/outcomes-and-sync-steps/comment-page-1/#comment-363</link>
		<dc:creator>Rowan Bunning</dc:creator>
		<pubDate>Tue, 10 Nov 2009 09:08:54 +0000</pubDate>
		<guid isPermaLink="false">http://availagility.co.uk/?p=437#comment-363</guid>
		<description>Jeff Sutherland describes SynchSteps in this paper: &quot;Inventing and Reinventing SCRUM in Five Companies&quot; http://www.agilealliance.org/system/article/file/888/file.pdf</description>
		<content:encoded><![CDATA[<p>Jeff Sutherland describes SynchSteps in this paper: &#8220;Inventing and Reinventing SCRUM in Five Companies&#8221; <a href="http://www.agilealliance.org/system/article/file/888/file.pdf" rel="nofollow">http://www.agilealliance.org/system/article/file/888/file.pdf</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl</title>
		<link>http://availagility.co.uk/2009/11/05/outcomes-and-sync-steps/comment-page-1/#comment-305</link>
		<dc:creator>Karl</dc:creator>
		<pubDate>Thu, 05 Nov 2009 21:16:09 +0000</pubDate>
		<guid isPermaLink="false">http://availagility.co.uk/?p=437#comment-305</guid>
		<description>Thanks Lasse. I agree that modern Scrum teams will use individual backlog items as sub Outcomes. I was primarily referring to the original thinking behind Scrum.</description>
		<content:encoded><![CDATA[<p>Thanks Lasse. I agree that modern Scrum teams will use individual backlog items as sub Outcomes. I was primarily referring to the original thinking behind Scrum.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lasse Koskela</title>
		<link>http://availagility.co.uk/2009/11/05/outcomes-and-sync-steps/comment-page-1/#comment-304</link>
		<dc:creator>Lasse Koskela</dc:creator>
		<pubDate>Thu, 05 Nov 2009 17:40:55 +0000</pubDate>
		<guid isPermaLink="false">http://availagility.co.uk/?p=437#comment-304</guid>
		<description>Hi Karl,

Thanks for the blog - nice and concise expression of agility.

Regarding Scrum, some Scrum teams also have multiple Outcomes. Or maybe I should say, there&#039;s one Outcome and a number of intermediate steps towards that Outcome that are smaller Outcomes in their own right.
 
Those intermediate steps would be individual backlog items/user stories/features that may or may not be delivered at the same point in time. That is, while a Scrum team might have a sprint goal (Outcome) of &quot;Charge Our Subscribers&quot; they might deploy the ability to charge credit cards into production four days into the sprint, electronic invoicing a couple of days later, etc.

What I describe here isn&#039;t canonical Scrum, perhaps, but it&#039;s not exactly against the dogma either.</description>
		<content:encoded><![CDATA[<p>Hi Karl,</p>
<p>Thanks for the blog &#8211; nice and concise expression of agility.</p>
<p>Regarding Scrum, some Scrum teams also have multiple Outcomes. Or maybe I should say, there&#8217;s one Outcome and a number of intermediate steps towards that Outcome that are smaller Outcomes in their own right.</p>
<p>Those intermediate steps would be individual backlog items/user stories/features that may or may not be delivered at the same point in time. That is, while a Scrum team might have a sprint goal (Outcome) of &#8220;Charge Our Subscribers&#8221; they might deploy the ability to charge credit cards into production four days into the sprint, electronic invoicing a couple of days later, etc.</p>
<p>What I describe here isn&#8217;t canonical Scrum, perhaps, but it&#8217;s not exactly against the dogma either.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

