<?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: Where Agile sucks</title>
	<atom:link href="http://www.klocwork.com/blog/2010/03/where-agile-sucks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.klocwork.com/blog/2010/03/where-agile-sucks/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=where-agile-sucks</link>
	<description>&#62;kloctalk is a blog and a community for software development professionals who create and maintain mission-critical software and the challenges they face on a daily basis.</description>
	<lastBuildDate>Tue, 24 Jan 2012 14:57:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: John Quincy</title>
		<link>http://www.klocwork.com/blog/2010/03/where-agile-sucks/comment-page-1/#comment-6862</link>
		<dc:creator>John Quincy</dc:creator>
		<pubDate>Sat, 29 Oct 2011 16:38:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.klocwork.com/blog/?p=935#comment-6862</guid>
		<description>It&#039;s been my experience that any true development (i.e. more than a toy project like an iPhone app) quickly surfaces all the shortcomings of SCRUM — and there are too many shortcomings to name here.

This video, although hilarious, has a serious message. It shows why companies are choosing to waste money on Agile:

http://www.youtube.com/watch?v=nvks70PD0Rs

John</description>
		<content:encoded><![CDATA[<p>It&#8217;s been my experience that any true development (i.e. more than a toy project like an iPhone app) quickly surfaces all the shortcomings of SCRUM — and there are too many shortcomings to name here.</p>
<p>This video, although hilarious, has a serious message. It shows why companies are choosing to waste money on Agile:</p>
<p><a href="http://www.youtube.com/watch?v=nvks70PD0Rs" rel="nofollow">http://www.youtube.com/watch?v=nvks70PD0Rs</a></p>
<p>John</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Where Agile development shines &#124; &#62;kloctalk</title>
		<link>http://www.klocwork.com/blog/2010/03/where-agile-sucks/comment-page-1/#comment-1852</link>
		<dc:creator>Where Agile development shines &#124; &#62;kloctalk</dc:creator>
		<pubDate>Tue, 23 Mar 2010 22:22:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.klocwork.com/blog/?p=935#comment-1852</guid>
		<description>[...] my previous post I discussed where I thought Agile really falls flat.  The problem I have is working remotely.  [...]</description>
		<content:encoded><![CDATA[<p>[...] my previous post I discussed where I thought Agile really falls flat.  The problem I have is working remotely.  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alen Zukich</title>
		<link>http://www.klocwork.com/blog/2010/03/where-agile-sucks/comment-page-1/#comment-1768</link>
		<dc:creator>Alen Zukich</dc:creator>
		<pubDate>Wed, 17 Mar 2010 19:38:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.klocwork.com/blog/?p=935#comment-1768</guid>
		<description>Chris, you have hit the nail on the head.  Agile does give visibility to this problem much much faster.  That is the exact idea of my next post ;)</description>
		<content:encoded><![CDATA[<p>Chris, you have hit the nail on the head.  Agile does give visibility to this problem much much faster.  That is the exact idea of my next post ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Bernard</title>
		<link>http://www.klocwork.com/blog/2010/03/where-agile-sucks/comment-page-1/#comment-1765</link>
		<dc:creator>Chris Bernard</dc:creator>
		<pubDate>Wed, 17 Mar 2010 19:24:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.klocwork.com/blog/?p=935#comment-1765</guid>
		<description>I&#039;ve done a fair amount of PMing remote agile projects.  Sounds like you have a fundamental communication problem with your project manager (or maybe you call them the Scrum Master).  Care to elaborate on that relationship?  :-)  Remoteness adds new challenges, but doesn&#039;t explain your problem.  Agile highlights this problem much faster than waterfall would.  I&#039;d suggest focusing on that problem rather than trying to blame agile.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve done a fair amount of PMing remote agile projects.  Sounds like you have a fundamental communication problem with your project manager (or maybe you call them the Scrum Master).  Care to elaborate on that relationship?  :-)  Remoteness adds new challenges, but doesn&#8217;t explain your problem.  Agile highlights this problem much faster than waterfall would.  I&#8217;d suggest focusing on that problem rather than trying to blame agile.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn Crosby</title>
		<link>http://www.klocwork.com/blog/2010/03/where-agile-sucks/comment-page-1/#comment-1759</link>
		<dc:creator>Shawn Crosby</dc:creator>
		<pubDate>Wed, 17 Mar 2010 12:01:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.klocwork.com/blog/?p=935#comment-1759</guid>
		<description>I&#039;m pretty new to agile too, but I think it answers many problems evident in software projects nowadays.  Our team is small and local so I don&#039;t have experiences to share with you on remote agile, but what seems to work for us is to make sure that each sprint has a theme...this way the entire team has part of a shared vision that keeps everyone on track.  We usually work with the product owner to come up with stories for a sprint that allows the team to focus on a particular area of the application that isn&#039;t too disjointed...already there have been times when this isn&#039;t possible, but I always search for a common thread up front that gets everyone focussed and moving in the same direction.</description>
		<content:encoded><![CDATA[<p>I&#8217;m pretty new to agile too, but I think it answers many problems evident in software projects nowadays.  Our team is small and local so I don&#8217;t have experiences to share with you on remote agile, but what seems to work for us is to make sure that each sprint has a theme&#8230;this way the entire team has part of a shared vision that keeps everyone on track.  We usually work with the product owner to come up with stories for a sprint that allows the team to focus on a particular area of the application that isn&#8217;t too disjointed&#8230;already there have been times when this isn&#8217;t possible, but I always search for a common thread up front that gets everyone focussed and moving in the same direction.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

