<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	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/"
	>

<channel>
	<title>Transient Technology &#187; product-owner</title>
	<atom:link href="http://martinaharris.com/tag/product-owner/feed/" rel="self" type="application/rss+xml" />
	<link>http://martinaharris.com</link>
	<description>changing minds - changing software</description>
	<lastBuildDate>Wed, 04 Aug 2010 10:22:34 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Tumble dried BDD from Studio Pragmatists</title>
		<link>http://martinaharris.com/2010/05/tumble-dried-bdd/</link>
		<comments>http://martinaharris.com/2010/05/tumble-dried-bdd/#comments</comments>
		<pubDate>Fri, 21 May 2010 22:02:32 +0000</pubDate>
		<dc:creator>Martin Harris</dc:creator>
				<category><![CDATA[java]]></category>
		<category><![CDATA[scrum and agile]]></category>
		<category><![CDATA[testing]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[annotation]]></category>
		<category><![CDATA[BDD]]></category>
		<category><![CDATA[behavior]]></category>
		<category><![CDATA[collaboration]]></category>
		<category><![CDATA[junit]]></category>
		<category><![CDATA[product-owner]]></category>
		<category><![CDATA[scrum]]></category>
		<category><![CDATA[spring]]></category>
		<category><![CDATA[teams]]></category>
		<category><![CDATA[test-specialist]]></category>

		<guid isPermaLink="false">http://martinaharris.com/?p=1027</guid>
		<description><![CDATA[On the 18th of May, 2010, the very new tumbler-glass project by Studio Pragmatists uploaded Tumbler 0.2.1 to Maven.  Having recently written about JBehave I found myself really liking the concept of behavior driven development.  So I decided to write a similar article about Tumbler. If you want the project code its available in my [...]]]></description>
		<wfw:commentRss>http://martinaharris.com/2010/05/tumble-dried-bdd/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Bad or Good? Behavior Driven Development within Scrum.</title>
		<link>http://martinaharris.com/2010/05/bad-or-good-bdd-within-scrum/</link>
		<comments>http://martinaharris.com/2010/05/bad-or-good-bdd-within-scrum/#comments</comments>
		<pubDate>Mon, 17 May 2010 17:46:35 +0000</pubDate>
		<dc:creator>Martin Harris</dc:creator>
				<category><![CDATA[java]]></category>
		<category><![CDATA[scrum and agile]]></category>
		<category><![CDATA[testing]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[annotation]]></category>
		<category><![CDATA[BDD]]></category>
		<category><![CDATA[behavior]]></category>
		<category><![CDATA[collaboration]]></category>
		<category><![CDATA[junit]]></category>
		<category><![CDATA[product-owner]]></category>
		<category><![CDATA[scrum]]></category>
		<category><![CDATA[spring]]></category>
		<category><![CDATA[teams]]></category>
		<category><![CDATA[test-specialist]]></category>

		<guid isPermaLink="false">http://martinaharris.com/?p=1001</guid>
		<description><![CDATA[I wanted to explore the possibility of using JBehave to formalise scrums definition of done. The idea being to encapsulate a definition of done as a JBehave scenario. So in true scrum style I decided to timebox 4 hours of work dedicated to JBehave. From a scrum point of view BDD can be used to [...]]]></description>
		<wfw:commentRss>http://martinaharris.com/2010/05/bad-or-good-bdd-within-scrum/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Scrum, where exactly do the managers go?</title>
		<link>http://martinaharris.com/2010/02/deletethepmo/</link>
		<comments>http://martinaharris.com/2010/02/deletethepmo/#comments</comments>
		<pubDate>Mon, 15 Feb 2010 05:00:18 +0000</pubDate>
		<dc:creator>Martin Harris</dc:creator>
				<category><![CDATA[scrum and agile]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[book]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[product-owner]]></category>
		<category><![CDATA[scrum]]></category>
		<category><![CDATA[scrum-master]]></category>
		<category><![CDATA[teams]]></category>

		<guid isPermaLink="false">http://martinaharris.com/?p=778</guid>
		<description><![CDATA[Project Management Offices serve no purpose in scrum. You are either a product owner, (not a manager), scrum master (not a manager either) or your in the team, (no technical leaders here either). How can an organisation migrate from central control to self directed scrum teams?  What are the challenges to our former project managers?]]></description>
		<wfw:commentRss>http://martinaharris.com/2010/02/deletethepmo/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Dancing to the tune of the Scrum Demo</title>
		<link>http://martinaharris.com/2010/01/dancing-to-the-tune-of-the-scrum-demo/</link>
		<comments>http://martinaharris.com/2010/01/dancing-to-the-tune-of-the-scrum-demo/#comments</comments>
		<pubDate>Mon, 18 Jan 2010 04:00:39 +0000</pubDate>
		<dc:creator>Martin Harris</dc:creator>
				<category><![CDATA[scrum and agile]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[collaboration]]></category>
		<category><![CDATA[delivery]]></category>
		<category><![CDATA[demo]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[product-owner]]></category>
		<category><![CDATA[scrum]]></category>
		<category><![CDATA[signoff]]></category>
		<category><![CDATA[teams]]></category>

		<guid isPermaLink="false">http://martinaharris.com/?p=624</guid>
		<description><![CDATA[As you achieve more experience with the scrum process, you come to realise that there is very little if anything you can afford to leave out.  If your conducting scrum and considering leaving out a practice, its worth considering what is to be gained and lost.  So continuing with the <a title="Scrum and Agile posts" href="http://martinaharris.com/category/development/scrum-and-agile/" target="_blank">scrum and agile theme</a> this year I plan review some of the scrum practices highlighting the benefits and some of the errors that are made.  The first of these focuses on the Sprint Review and within that in particular the Software Demo.]]></description>
		<wfw:commentRss>http://martinaharris.com/2010/01/dancing-to-the-tune-of-the-scrum-demo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Of Groundswell and Product Owners</title>
		<link>http://martinaharris.com/2010/01/groundswell-and-product-owners/</link>
		<comments>http://martinaharris.com/2010/01/groundswell-and-product-owners/#comments</comments>
		<pubDate>Thu, 14 Jan 2010 22:41:27 +0000</pubDate>
		<dc:creator>Martin Harris</dc:creator>
				<category><![CDATA[scrum and agile]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[backlog]]></category>
		<category><![CDATA[book]]></category>
		<category><![CDATA[collaboration]]></category>
		<category><![CDATA[crowdsourcing]]></category>
		<category><![CDATA[customer]]></category>
		<category><![CDATA[groundswell]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[product-owner]]></category>
		<category><![CDATA[requirements]]></category>
		<category><![CDATA[scrum]]></category>
		<category><![CDATA[social-technology]]></category>

		<guid isPermaLink="false">http://martinaharris.com/?p=657</guid>
		<description><![CDATA[I have just finished reading <a title="Groundswell link amazon" href="http://www.amazon.com/Groundswell-Winning-Transformed-Social-Technologies/dp/1422125009/ref=sr_1_1?ie=UTF8&#38;s=books&#38;qid=1263500927&#38;sr=8-1" target="_blank">Groundswell</a> by Josh Bernoff of Forrester Research.  The book has been around for awhile but its concepts are worth understanding.  Its a great book about how Social Technologies have changed the way companies relate to their customers.  Not only that but how companies can benefit from Social Technologies within their own organisation.  Its a good read, get hold of a copy.  The book is rich with Internet law, marketing tips, research and good practice.  It gave me some ideas on how Groundswell could be used to provide a product owner with some powerful tooling.]]></description>
		<wfw:commentRss>http://martinaharris.com/2010/01/groundswell-and-product-owners/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>6 Tips for Good Scrum</title>
		<link>http://martinaharris.com/2009/12/lsg-scrum-tips/</link>
		<comments>http://martinaharris.com/2009/12/lsg-scrum-tips/#comments</comments>
		<pubDate>Tue, 08 Dec 2009 22:31:32 +0000</pubDate>
		<dc:creator>Martin Harris</dc:creator>
				<category><![CDATA[scrum and agile]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[co-location]]></category>
		<category><![CDATA[collaboration]]></category>
		<category><![CDATA[delivery]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[pair-code]]></category>
		<category><![CDATA[product-owner]]></category>
		<category><![CDATA[retrospective]]></category>
		<category><![CDATA[scrum]]></category>
		<category><![CDATA[self-directed]]></category>
		<category><![CDATA[teams]]></category>

		<guid isPermaLink="false">http://martinaharris.com/?p=509</guid>
		<description><![CDATA[I went along to the London Scrum User Group Monday evening.  We decided to put together 15 tips for scrum that every team should try.  Its was an optimistically large number of tips given that the meeting is held in a pub.  Even so, we did produce 6 very good tips.  Read on to see what we came up with. ]]></description>
		<wfw:commentRss>http://martinaharris.com/2009/12/lsg-scrum-tips/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
