<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Agile as a Marketing tool?</title>
	<atom:link href="http://darksidemarketing.com/2009/12/30/agile-as-a-marketing-tool/feed/" rel="self" type="application/rss+xml" />
	<link>http://darksidemarketing.com/2009/12/30/agile-as-a-marketing-tool/</link>
	<description>An Engineer&#039;s Guide to Marketing</description>
	<lastBuildDate>Wed, 26 Jan 2011 18:24:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Tweets that mention Agile as a Marketing tool? « The Dark Side -- Topsy.com</title>
		<link>http://darksidemarketing.com/2009/12/30/agile-as-a-marketing-tool/#comment-50</link>
		<dc:creator><![CDATA[Tweets that mention Agile as a Marketing tool? « The Dark Side -- Topsy.com]]></dc:creator>
		<pubDate>Tue, 26 Jan 2010 09:58:09 +0000</pubDate>
		<guid isPermaLink="false">http://darksidemarketing.com/?p=137#comment-50</guid>
		<description><![CDATA[[...] This post was mentioned on Twitter by Agilebuddy, Scott Duncan. Scott Duncan said: Agile as a Marketing Tool? http://bit.ly/8rNiHZ [...]]]></description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Agilebuddy, Scott Duncan. Scott Duncan said: Agile as a Marketing Tool? <a href="http://bit.ly/8rNiHZ" rel="nofollow">http://bit.ly/8rNiHZ</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Dark Side: Agile as a Marketing Tool? &#124; Marketbright Blog</title>
		<link>http://darksidemarketing.com/2009/12/30/agile-as-a-marketing-tool/#comment-49</link>
		<dc:creator><![CDATA[The Dark Side: Agile as a Marketing Tool? &#124; Marketbright Blog]]></dc:creator>
		<pubDate>Mon, 25 Jan 2010 16:11:18 +0000</pubDate>
		<guid isPermaLink="false">http://darksidemarketing.com/?p=137#comment-49</guid>
		<description><![CDATA[[...] Check out the article.  [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Check out the article.  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Dunn</title>
		<link>http://darksidemarketing.com/2009/12/30/agile-as-a-marketing-tool/#comment-42</link>
		<dc:creator><![CDATA[Dan Dunn]]></dc:creator>
		<pubDate>Thu, 31 Dec 2009 02:10:12 +0000</pubDate>
		<guid isPermaLink="false">http://darksidemarketing.com/?p=137#comment-42</guid>
		<description><![CDATA[I think a key concept is that scrum doesn&#039;t solve your problems, but it makes  visible in a timely fashion.  Scrum doesn&#039;t save you from screwups, but it forces you to confront them.  That means you get to correct them more quickly and helps you keep avoiding them.

Take the external contractor example.  Say the agency fails to deliver on time.  At the sprint retrospective meeting you sit around and say &quot;what can we do to keep that from happening again?&quot;  You might decide to pay more money (be more responsive), or hire someone in house, or just decide to write a more forgiving schedule the next time.  Whatever the choice, you&#039;ve made progress for the next time.

Sales is the same way.  At the sprint kickoff, the team outlines what external dependencies there are.  If sales can&#039;t commit their resources that you need to get your user story done, then you need to pick a different user story.  Or maybe they commit but fail to follow through - you&#039;re back to the retrospective meeting, and you realize &quot;we missed this story because sales didn&#039;t deliver.&quot;  Scrum isn&#039;t going to solve your sales communication problem, but it will make it visible.]]></description>
		<content:encoded><![CDATA[<p>I think a key concept is that scrum doesn&#8217;t solve your problems, but it makes  visible in a timely fashion.  Scrum doesn&#8217;t save you from screwups, but it forces you to confront them.  That means you get to correct them more quickly and helps you keep avoiding them.</p>
<p>Take the external contractor example.  Say the agency fails to deliver on time.  At the sprint retrospective meeting you sit around and say &#8220;what can we do to keep that from happening again?&#8221;  You might decide to pay more money (be more responsive), or hire someone in house, or just decide to write a more forgiving schedule the next time.  Whatever the choice, you&#8217;ve made progress for the next time.</p>
<p>Sales is the same way.  At the sprint kickoff, the team outlines what external dependencies there are.  If sales can&#8217;t commit their resources that you need to get your user story done, then you need to pick a different user story.  Or maybe they commit but fail to follow through &#8211; you&#8217;re back to the retrospective meeting, and you realize &#8220;we missed this story because sales didn&#8217;t deliver.&#8221;  Scrum isn&#8217;t going to solve your sales communication problem, but it will make it visible.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

