<?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: Customer Development &#8211; The Missing Piece!</title>
	<atom:link href="http://wattf.com/wp/2009/03/16/customer-development-the-missing-piece/feed/" rel="self" type="application/rss+xml" />
	<link>http://wattf.com/wp/2009/03/16/customer-development-the-missing-piece/</link>
	<description>{It's Safer to be Risky}</description>
	<lastBuildDate>Sat, 05 Feb 2011 23:11:32 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: final test pingback from &#171; End Year 2012</title>
		<link>http://wattf.com/wp/2009/03/16/customer-development-the-missing-piece/comment-page-1/#comment-1145</link>
		<dc:creator>final test pingback from &#171; End Year 2012</dc:creator>
		<pubDate>Thu, 06 May 2010 06:34:02 +0000</pubDate>
		<guid isPermaLink="false">http://wattf.com/wp/2009/03/16/customer-development-the-missing-piece/#comment-1145</guid>
		<description>[...] http://wattf.com/wp/2009/03/16/customer-development-the-missing-piece/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://wattf.com/wp/2009/03/16/customer-development-the-missing-piece/" rel="nofollow">http://wattf.com/wp/2009/03/16/customer-development-the-missing-piece/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Are you doing &#8220;Real Agile&#8221;?</title>
		<link>http://wattf.com/wp/2009/03/16/customer-development-the-missing-piece/comment-page-1/#comment-877</link>
		<dc:creator>Are you doing &#8220;Real Agile&#8221;?</dc:creator>
		<pubDate>Mon, 30 Nov 2009 17:07:16 +0000</pubDate>
		<guid isPermaLink="false">http://wattf.com/wp/2009/03/16/customer-development-the-missing-piece/#comment-877</guid>
		<description>[...] stories are too open ended, or your product owner doesn&#8217;t have a vision (introduce them to Customer Development!), or that you can&#8217;t keep your standups focused, or that you don&#8217;t pair enough, or that [...]</description>
		<content:encoded><![CDATA[<p>[...] stories are too open ended, or your product owner doesn&#8217;t have a vision (introduce them to Customer Development!), or that you can&#8217;t keep your standups focused, or that you don&#8217;t pair enough, or that [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Murphy</title>
		<link>http://wattf.com/wp/2009/03/16/customer-development-the-missing-piece/comment-page-1/#comment-606</link>
		<dc:creator>Jim Murphy</dc:creator>
		<pubDate>Mon, 23 Mar 2009 15:45:45 +0000</pubDate>
		<guid isPermaLink="false">http://wattf.com/wp/2009/03/16/customer-development-the-missing-piece/#comment-606</guid>
		<description>I think your are getting to why I said XP/Scrum &quot;punt&quot; on that part.  They defer to someone else to figure out what should be built and why.  The problem with defering to &quot;the business people&quot; is that typically they don&#039;t have a clue what should be built either!  thats when product development devolves into &quot;He who has the compiler wins!&quot; which is so often the case - especially in startups.


In my experience its difficult to find someone with all the tools to approach this problem - the rare super-founder, but thats doesn&#039;t scale too well.  More often it becomes a group collaboration effort but the risk there is having too many people focused on the color of the bicycle shed instead of the primary mission.

In a startup, when YOU are &quot;the business people&quot; what do you do?

Thanks for your comments!</description>
		<content:encoded><![CDATA[<p>I think your are getting to why I said XP/Scrum &#8220;punt&#8221; on that part.  They defer to someone else to figure out what should be built and why.  The problem with defering to &#8220;the business people&#8221; is that typically they don&#8217;t have a clue what should be built either!  thats when product development devolves into &#8220;He who has the compiler wins!&#8221; which is so often the case &#8211; especially in startups.</p>
<p>In my experience its difficult to find someone with all the tools to approach this problem &#8211; the rare super-founder, but thats doesn&#8217;t scale too well.  More often it becomes a group collaboration effort but the risk there is having too many people focused on the color of the bicycle shed instead of the primary mission.</p>
<p>In a startup, when YOU are &#8220;the business people&#8221; what do you do?</p>
<p>Thanks for your comments!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DAR</title>
		<link>http://wattf.com/wp/2009/03/16/customer-development-the-missing-piece/comment-page-1/#comment-601</link>
		<dc:creator>DAR</dc:creator>
		<pubDate>Wed, 18 Mar 2009 21:01:47 +0000</pubDate>
		<guid isPermaLink="false">http://wattf.com/wp/2009/03/16/customer-development-the-missing-piece/#comment-601</guid>
		<description>Just a clarification:  XP doesn&#039;t exactly &quot;punt&quot; on deciding what goes on the product feature list.  Rather, it intentionally avoids making those decisions for good reason.  It puts those decisions where it belongs:  with the business people - aka the &quot;customer&quot; in XP terminology.  (&quot;Developers make development decisions; business people make business decisions.&quot;)

What this means for a starup then, since you have no customer, is that someone needs to play the role of the customer - deciding what features are most important right now, what &quot;functionality theme&quot; the current release will be offering the market, where to draw the line determining what set of features will make up the current release, etc.

It&#039;s ideally best if this person is not a member of the technical team (e.g.,  a &quot;product manager&quot; is ideal for this role).  But if it does have to be a member of the technical staff, then that staff member should try as hard as possible to &quot;take off their technical hat&quot; and &quot;put on their business hat&quot; when they make those decisions.</description>
		<content:encoded><![CDATA[<p>Just a clarification:  XP doesn&#8217;t exactly &#8220;punt&#8221; on deciding what goes on the product feature list.  Rather, it intentionally avoids making those decisions for good reason.  It puts those decisions where it belongs:  with the business people &#8211; aka the &#8220;customer&#8221; in XP terminology.  (&#8220;Developers make development decisions; business people make business decisions.&#8221;)</p>
<p>What this means for a starup then, since you have no customer, is that someone needs to play the role of the customer &#8211; deciding what features are most important right now, what &#8220;functionality theme&#8221; the current release will be offering the market, where to draw the line determining what set of features will make up the current release, etc.</p>
<p>It&#8217;s ideally best if this person is not a member of the technical team (e.g.,  a &#8220;product manager&#8221; is ideal for this role).  But if it does have to be a member of the technical staff, then that staff member should try as hard as possible to &#8220;take off their technical hat&#8221; and &#8220;put on their business hat&#8221; when they make those decisions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Software Quality Digest - 2009-03-18 &#124; No bug left behind</title>
		<link>http://wattf.com/wp/2009/03/16/customer-development-the-missing-piece/comment-page-1/#comment-600</link>
		<dc:creator>Software Quality Digest - 2009-03-18 &#124; No bug left behind</dc:creator>
		<pubDate>Wed, 18 Mar 2009 20:48:52 +0000</pubDate>
		<guid isPermaLink="false">http://wattf.com/wp/2009/03/16/customer-development-the-missing-piece/#comment-600</guid>
		<description>[...] Customer Development - The Missing Piece! - &#8220;I’ve spent a lot of time making agile development work in startups and it ain’t easy. Necessary but not easy.&#8221; and a response by Eric from Lesson Learned [...]</description>
		<content:encoded><![CDATA[<p>[...] Customer Development &#8211; The Missing Piece! &#8211; &#8220;I’ve spent a lot of time making agile development work in startups and it ain’t easy. Necessary but not easy.&#8221; and a response by Eric from Lesson Learned [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Murphy</title>
		<link>http://wattf.com/wp/2009/03/16/customer-development-the-missing-piece/comment-page-1/#comment-598</link>
		<dc:creator>Jim Murphy</dc:creator>
		<pubDate>Tue, 17 Mar 2009 12:43:49 +0000</pubDate>
		<guid isPermaLink="false">http://wattf.com/wp/2009/03/16/customer-development-the-missing-piece/#comment-598</guid>
		<description>My interest is definitely piqued!  I hope you intend on publishing more classes?  

I have Steve&#039;s book on order but in the meantime enjoy reading Eric Ries&#039; blog on the topic: http://startuplessonslearned.blogspot.com/</description>
		<content:encoded><![CDATA[<p>My interest is definitely piqued!  I hope you intend on publishing more classes?  </p>
<p>I have Steve&#8217;s book on order but in the meantime enjoy reading Eric Ries&#8217; blog on the topic: <a href="http://startuplessonslearned.blogspot.com/" rel="nofollow">http://startuplessonslearned.blogspot.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nivi</title>
		<link>http://wattf.com/wp/2009/03/16/customer-development-the-missing-piece/comment-page-1/#comment-597</link>
		<dc:creator>Nivi</dc:creator>
		<pubDate>Tue, 17 Mar 2009 01:50:13 +0000</pubDate>
		<guid isPermaLink="false">http://wattf.com/wp/2009/03/16/customer-development-the-missing-piece/#comment-597</guid>
		<description>All I can say to this is: YES! I&#039;m psyched you&#039;re excited to learn more.</description>
		<content:encoded><![CDATA[<p>All I can say to this is: YES! I&#8217;m psyched you&#8217;re excited to learn more.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

