<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" 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/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>It's a Delivery Thing</title>
	
	<link>http://itsadeliverything.com</link>
	<description>Steven Thomas on the art of leading software development teams, projects and programmes</description>
	<lastBuildDate>Mon, 13 May 2013 05:30:53 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/ItsADeliveryThing" /><feedburner:info uri="itsadeliverything" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:emailServiceId>ItsADeliveryThing</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><item>
		<title>No walls: What to do when you’ve no Walls for your Informative Workspace</title>
		<link>http://feedproxy.google.com/~r/ItsADeliveryThing/~3/LLWT71YDJBg/no-walls-what-to-do-when-youve-no-walls-for-your-informative-workspace</link>
		<comments>http://itsadeliverything.com/no-walls-what-to-do-when-youve-no-walls-for-your-informative-workspace#comments</comments>
		<pubDate>Mon, 13 May 2013 05:30:53 +0000</pubDate>
		<dc:creator>Steven Thomas</dc:creator>
				<category><![CDATA[Experience]]></category>
		<category><![CDATA[Musing]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[monitoring and control]]></category>
		<category><![CDATA[what do I do when]]></category>

		<guid isPermaLink="false">http://itsadeliverything.com/?p=1805</guid>
		<description>You move into a lovely new office. Lots of light and open spaces. Beautiful. Modern. But no walls. Agile kind of assumes you&amp;#8217;ve got walls. Whiteboards. Sprint Plan. Product Backlog. Burn down Charts. Kanban boards. Cumulative Flow Diagrams. All prominently &amp;#8230; &lt;a href="http://itsadeliverything.com/no-walls-what-to-do-when-youve-no-walls-for-your-informative-workspace"&gt;Continue reading &lt;span class="meta-nav"&gt;&amp;#8594;&lt;/span&gt;&lt;/a&gt;&lt;img src="http://feeds.feedburner.com/~r/ItsADeliveryThing/~4/LLWT71YDJBg" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://itsadeliverything.com/no-walls-what-to-do-when-youve-no-walls-for-your-informative-workspace/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://itsadeliverything.com/no-walls-what-to-do-when-youve-no-walls-for-your-informative-workspace</feedburner:origLink></item>
		<item>
		<title>Manage All Assumptions as Risks</title>
		<link>http://feedproxy.google.com/~r/ItsADeliveryThing/~3/WYVClOhZf3w/manage-all-assumptions-as-risks</link>
		<comments>http://itsadeliverything.com/manage-all-assumptions-as-risks#comments</comments>
		<pubDate>Mon, 06 May 2013 05:00:21 +0000</pubDate>
		<dc:creator>Steven Thomas</dc:creator>
				<category><![CDATA[Experience]]></category>
		<category><![CDATA[Musing]]></category>
		<category><![CDATA[programme management]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[risk management]]></category>

		<guid isPermaLink="false">http://itsadeliverything.com/?p=1478</guid>
		<description>Assuming something means taking it for granted. In other words you&amp;#8217;ve got a more or less conscious theory (or, less charitably, a guess) that something is going to happen. The trouble is that the assumption might not be true. That &amp;#8230; &lt;a href="http://itsadeliverything.com/manage-all-assumptions-as-risks"&gt;Continue reading &lt;span class="meta-nav"&gt;&amp;#8594;&lt;/span&gt;&lt;/a&gt;&lt;img src="http://feeds.feedburner.com/~r/ItsADeliveryThing/~4/WYVClOhZf3w" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://itsadeliverything.com/manage-all-assumptions-as-risks/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://itsadeliverything.com/manage-all-assumptions-as-risks</feedburner:origLink></item>
		<item>
		<title>Epics: My Love Hate Relationship with Large User Stories</title>
		<link>http://feedproxy.google.com/~r/ItsADeliveryThing/~3/77XrF-k3M5Y/epics-my-love-hate-relationship-with-large-user-stories</link>
		<comments>http://itsadeliverything.com/epics-my-love-hate-relationship-with-large-user-stories#comments</comments>
		<pubDate>Mon, 29 Apr 2013 05:30:47 +0000</pubDate>
		<dc:creator>Steven Thomas</dc:creator>
				<category><![CDATA[Musing]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[monitoring and control]]></category>
		<category><![CDATA[scope and requirements]]></category>

		<guid isPermaLink="false">http://itsadeliverything.com/?p=1864</guid>
		<description>Epics aren&amp;#8217;t very good for driving the development team because Epics lack sufficient detail and will take too long to complete anyway. But Epics are, like their smaller relatives the user story, great as a place holder for a conversation. &amp;#8230; &lt;a href="http://itsadeliverything.com/epics-my-love-hate-relationship-with-large-user-stories"&gt;Continue reading &lt;span class="meta-nav"&gt;&amp;#8594;&lt;/span&gt;&lt;/a&gt;&lt;img src="http://feeds.feedburner.com/~r/ItsADeliveryThing/~4/77XrF-k3M5Y" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://itsadeliverything.com/epics-my-love-hate-relationship-with-large-user-stories/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://itsadeliverything.com/epics-my-love-hate-relationship-with-large-user-stories</feedburner:origLink></item>
		<item>
		<title>User Story Format Should Not Be a Straight Jacket</title>
		<link>http://feedproxy.google.com/~r/ItsADeliveryThing/~3/CQICCD1vJNE/user-story-format-should-not-be-a-straight-jacket</link>
		<comments>http://itsadeliverything.com/user-story-format-should-not-be-a-straight-jacket#comments</comments>
		<pubDate>Mon, 22 Apr 2013 05:30:51 +0000</pubDate>
		<dc:creator>Steven Thomas</dc:creator>
				<category><![CDATA[Musing]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[scope and requirements]]></category>

		<guid isPermaLink="false">http://itsadeliverything.com/?p=1723</guid>
		<description>I use the formal &amp;#8220;As &amp;#60;user role&amp;#62; I want to &amp;#60;action&amp;#62; so that &amp;#60;goal&amp;#62;&amp;#8221; format when it helps. The main value of the format is it puts the focus on the users rather than on technology components. So if the &amp;#8230; &lt;a href="http://itsadeliverything.com/user-story-format-should-not-be-a-straight-jacket"&gt;Continue reading &lt;span class="meta-nav"&gt;&amp;#8594;&lt;/span&gt;&lt;/a&gt;&lt;img src="http://feeds.feedburner.com/~r/ItsADeliveryThing/~4/CQICCD1vJNE" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://itsadeliverything.com/user-story-format-should-not-be-a-straight-jacket/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://itsadeliverything.com/user-story-format-should-not-be-a-straight-jacket</feedburner:origLink></item>
		<item>
		<title>4 Objectives for an Automated Test Strategy</title>
		<link>http://feedproxy.google.com/~r/ItsADeliveryThing/~3/Pt0c88-UMTI/4-objectives-for-an-automated-test-strategy</link>
		<comments>http://itsadeliverything.com/4-objectives-for-an-automated-test-strategy#comments</comments>
		<pubDate>Mon, 15 Apr 2013 05:30:27 +0000</pubDate>
		<dc:creator>Steven Thomas</dc:creator>
				<category><![CDATA[Experience]]></category>
		<category><![CDATA[Musing]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[quality]]></category>
		<category><![CDATA[specification by example]]></category>
		<category><![CDATA[technical practices]]></category>

		<guid isPermaLink="false">http://itsadeliverything.com/?p=1925</guid>
		<description>I recently explained to my team the objectives our automated test strategy had to fulfil: Provides &amp;#8220;living&amp;#8221; requirements documentation Results in a comprehensive regression test suite Ensures high functional coverage Runs fast for developers Provides &amp;#8220;living&amp;#8221; requirements documentation Stale requirements &amp;#8230; &lt;a href="http://itsadeliverything.com/4-objectives-for-an-automated-test-strategy"&gt;Continue reading &lt;span class="meta-nav"&gt;&amp;#8594;&lt;/span&gt;&lt;/a&gt;&lt;img src="http://feeds.feedburner.com/~r/ItsADeliveryThing/~4/Pt0c88-UMTI" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://itsadeliverything.com/4-objectives-for-an-automated-test-strategy/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://itsadeliverything.com/4-objectives-for-an-automated-test-strategy</feedburner:origLink></item>
		<item>
		<title>When Meeting Madness Strikes</title>
		<link>http://feedproxy.google.com/~r/ItsADeliveryThing/~3/YI1IHUSVYZg/when-meeting-madness-strikes</link>
		<comments>http://itsadeliverything.com/when-meeting-madness-strikes#comments</comments>
		<pubDate>Mon, 08 Apr 2013 05:30:58 +0000</pubDate>
		<dc:creator>Steven Thomas</dc:creator>
				<category><![CDATA[Musing]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[heartbeat]]></category>
		<category><![CDATA[what do I do when]]></category>

		<guid isPermaLink="false">http://itsadeliverything.com/?p=1687</guid>
		<description>Some people and some organisations like meetings. If you drop Agile with its Agile Heartbeat into the mix then you might find that meeting madness strikes. I&amp;#8217;m a Kiwi living in the UK and I&amp;#8217;ve noticed the British will form &amp;#8230; &lt;a href="http://itsadeliverything.com/when-meeting-madness-strikes"&gt;Continue reading &lt;span class="meta-nav"&gt;&amp;#8594;&lt;/span&gt;&lt;/a&gt;&lt;img src="http://feeds.feedburner.com/~r/ItsADeliveryThing/~4/YI1IHUSVYZg" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://itsadeliverything.com/when-meeting-madness-strikes/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://itsadeliverything.com/when-meeting-madness-strikes</feedburner:origLink></item>
		<item>
		<title>Agile Requirements Snail: Feature to User Story to Scenario</title>
		<link>http://feedproxy.google.com/~r/ItsADeliveryThing/~3/pAj7W0dJJeI/agile-requirements-snail-feature-to-user-story-to-scenario</link>
		<comments>http://itsadeliverything.com/agile-requirements-snail-feature-to-user-story-to-scenario#comments</comments>
		<pubDate>Tue, 02 Apr 2013 05:30:50 +0000</pubDate>
		<dc:creator>Steven Thomas</dc:creator>
				<category><![CDATA[Musing]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[estimating]]></category>
		<category><![CDATA[quality]]></category>
		<category><![CDATA[scope and requirements]]></category>
		<category><![CDATA[specification by example]]></category>
		<category><![CDATA[technical practices]]></category>

		<guid isPermaLink="false">http://itsadeliverything.com/?p=1570</guid>
		<description>The Iterative Incremental approach inherent in Agile applies to delivered functionality but also to the requirements elicitation part of the process. I like to refine requirements over time. Start high level, just enough to remind us to have a conversation, &amp;#8230; &lt;a href="http://itsadeliverything.com/agile-requirements-snail-feature-to-user-story-to-scenario"&gt;Continue reading &lt;span class="meta-nav"&gt;&amp;#8594;&lt;/span&gt;&lt;/a&gt;&lt;img src="http://feeds.feedburner.com/~r/ItsADeliveryThing/~4/pAj7W0dJJeI" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://itsadeliverything.com/agile-requirements-snail-feature-to-user-story-to-scenario/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://itsadeliverything.com/agile-requirements-snail-feature-to-user-story-to-scenario</feedburner:origLink></item>
		<item>
		<title>“Small” is an Estimate</title>
		<link>http://feedproxy.google.com/~r/ItsADeliveryThing/~3/DEZEuvIq_hI/small-is-an-estimate</link>
		<comments>http://itsadeliverything.com/small-is-an-estimate#comments</comments>
		<pubDate>Mon, 25 Mar 2013 05:30:30 +0000</pubDate>
		<dc:creator>Steven Thomas</dc:creator>
				<category><![CDATA[Musing]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[estimating]]></category>

		<guid isPermaLink="false">http://itsadeliverything.com/?p=1843</guid>
		<description>One of the ironies of the discussion on no-estimates is that the no-estimate proponents do in fact estimate. In a small way. Like all Agilists the no-estimation guys focus on delivering small user stories frequently. They rightly want to maximise &amp;#8230; &lt;a href="http://itsadeliverything.com/small-is-an-estimate"&gt;Continue reading &lt;span class="meta-nav"&gt;&amp;#8594;&lt;/span&gt;&lt;/a&gt;&lt;img src="http://feeds.feedburner.com/~r/ItsADeliveryThing/~4/DEZEuvIq_hI" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://itsadeliverything.com/small-is-an-estimate/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://itsadeliverything.com/small-is-an-estimate</feedburner:origLink></item>
		<item>
		<title>Agile Programme Roles and Responsibilities</title>
		<link>http://feedproxy.google.com/~r/ItsADeliveryThing/~3/I6AJH_8fgOg/agile-programme-roles-and-responsibilities</link>
		<comments>http://itsadeliverything.com/agile-programme-roles-and-responsibilities#comments</comments>
		<pubDate>Mon, 18 Mar 2013 05:30:56 +0000</pubDate>
		<dc:creator>Steven Thomas</dc:creator>
				<category><![CDATA[Experience]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[programme management]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[roles and responsibilities]]></category>

		<guid isPermaLink="false">http://itsadeliverything.com/?p=1319</guid>
		<description>To go with my typical programme organisation I thought I&amp;#8217;d describe the roles and responsibilities I expect on an Agile programme. Remember I&amp;#8217;m interested in software delivery so I&amp;#8217;m talking about programmes that have software development at the core. Non-software &amp;#8230; &lt;a href="http://itsadeliverything.com/agile-programme-roles-and-responsibilities"&gt;Continue reading &lt;span class="meta-nav"&gt;&amp;#8594;&lt;/span&gt;&lt;/a&gt;&lt;img src="http://feeds.feedburner.com/~r/ItsADeliveryThing/~4/I6AJH_8fgOg" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://itsadeliverything.com/agile-programme-roles-and-responsibilities/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://itsadeliverything.com/agile-programme-roles-and-responsibilities</feedburner:origLink></item>
		<item>
		<title>What do I do when There is More Than One Product Owner</title>
		<link>http://feedproxy.google.com/~r/ItsADeliveryThing/~3/YAfo52tVOro/what-do-i-do-when-there-is-more-than-one-product-owner</link>
		<comments>http://itsadeliverything.com/what-do-i-do-when-there-is-more-than-one-product-owner#comments</comments>
		<pubDate>Mon, 11 Mar 2013 05:30:56 +0000</pubDate>
		<dc:creator>Steven Thomas</dc:creator>
				<category><![CDATA[Musing]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[product management]]></category>
		<category><![CDATA[programme management]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[roles and responsibilities]]></category>
		<category><![CDATA[what do I do when]]></category>

		<guid isPermaLink="false">http://itsadeliverything.com/?p=1679</guid>
		<description>The product owner defines what the development team is meant to build and the order in which it is built. What should you do when the Product Owner responsibilities lie with more than one person? The short answer, that works &amp;#8230; &lt;a href="http://itsadeliverything.com/what-do-i-do-when-there-is-more-than-one-product-owner"&gt;Continue reading &lt;span class="meta-nav"&gt;&amp;#8594;&lt;/span&gt;&lt;/a&gt;&lt;img src="http://feeds.feedburner.com/~r/ItsADeliveryThing/~4/YAfo52tVOro" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://itsadeliverything.com/what-do-i-do-when-there-is-more-than-one-product-owner/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://itsadeliverything.com/what-do-i-do-when-there-is-more-than-one-product-owner</feedburner:origLink></item>
	</channel>
</rss>
