<?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: SCRUM Agile Web Application Development: Pigs and Chickens</title>
	<atom:link href="http://www.stonethorn.com/archive/scrum-agile-web-application-development-pigs-and-chickens/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.stonethorn.com/archive/scrum-agile-web-application-development-pigs-and-chickens/</link>
	<description>Portland Oregon Interactive, New Media, Web Producer, Interactive Brand Marketing Strategist</description>
	<lastBuildDate>Tue, 05 May 2009 08:25:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Lynn Twiss</title>
		<link>http://www.stonethorn.com/archive/scrum-agile-web-application-development-pigs-and-chickens/comment-page-1/#comment-1660</link>
		<dc:creator>Lynn Twiss</dc:creator>
		<pubDate>Tue, 21 Oct 2008 00:28:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.stonethorn.com/?p=383#comment-1660</guid>
		<description>Hey Zack,

It is indeed intense. What SCRUM does is places the responsibility of a deployable build into the hands of the team with little to no support from Managers. Some development teams prefer this model as the PMs are not doing thier job (IMHO) and so want to cut out overhead and meaningless meetings.

However, there is little support for the team when needed. 

SCRUM runs against the new model of conversational development. Other agencies like &lt;a href=&quot;http://www.motherlondon.com/&quot; rel=&quot;nofollow&quot;&gt;Mother&lt;/a&gt; or &lt;a href=&quot;http://findsubstance.com/&quot; rel=&quot;nofollow&quot;&gt;Substance&lt;/a&gt; call this the Long Table process. Everyone is involved in all portions of the development so that appropriate support is available to team members that need it.

&lt;blockquote&gt;&quot;The “long table” is a physical manifestation of networked culture. Information is less driven by hierarchy and process and more driven through connections, collaboration, transparency and as Noah aptly put it in his blog, moments of serrendipity. Long table work environments help achieve this. Regardless of title, everyone sits together, pitches in, hears everything and can be inspired by seemingly unrelated moments or conversations around them.&quot;&lt;/blockquote&gt;

Overall, all processes have flaws dependent on the project at hand, but it&#039;s great that there is more than just the PMI/PMP waterfall methodology.

[&lt;a href=&quot;http://www.psfk.com/2007/03/long_table_agen.html&quot; rel=&quot;nofollow&quot;&gt;additional&lt;/a&gt;]</description>
		<content:encoded><![CDATA[<p>Hey Zack,</p>
<p>It is indeed intense. What SCRUM does is places the responsibility of a deployable build into the hands of the team with little to no support from Managers. Some development teams prefer this model as the PMs are not doing thier job (IMHO) and so want to cut out overhead and meaningless meetings.</p>
<p>However, there is little support for the team when needed. </p>
<p>SCRUM runs against the new model of conversational development. Other agencies like <a href="http://www.motherlondon.com/" rel="nofollow">Mother</a> or <a href="http://findsubstance.com/" rel="nofollow">Substance</a> call this the Long Table process. Everyone is involved in all portions of the development so that appropriate support is available to team members that need it.</p>
<blockquote><p>&#8220;The “long table” is a physical manifestation of networked culture. Information is less driven by hierarchy and process and more driven through connections, collaboration, transparency and as Noah aptly put it in his blog, moments of serrendipity. Long table work environments help achieve this. Regardless of title, everyone sits together, pitches in, hears everything and can be inspired by seemingly unrelated moments or conversations around them.&#8221;</p></blockquote>
<p>Overall, all processes have flaws dependent on the project at hand, but it&#8217;s great that there is more than just the PMI/PMP waterfall methodology.</p>
<p>[<a href="http://www.psfk.com/2007/03/long_table_agen.html" rel="nofollow">additional</a>]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zack</title>
		<link>http://www.stonethorn.com/archive/scrum-agile-web-application-development-pigs-and-chickens/comment-page-1/#comment-1659</link>
		<dc:creator>Zack</dc:creator>
		<pubDate>Fri, 17 Oct 2008 15:20:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.stonethorn.com/?p=383#comment-1659</guid>
		<description>Hey Lynn.  It&#039;s quite the coincidence that you&#039;ve been looking into that development model.  I&#039;ve recently applied to a new position that strictly follows that model on 3 to 4 week development cycles.  I&#039;ve been reading up on this development methodology and it appears quite more intense but also allows for faster deliverables as opposed to the waterfall methodology.  I hope everything is going well, drop me a line sometime.</description>
		<content:encoded><![CDATA[<p>Hey Lynn.  It&#8217;s quite the coincidence that you&#8217;ve been looking into that development model.  I&#8217;ve recently applied to a new position that strictly follows that model on 3 to 4 week development cycles.  I&#8217;ve been reading up on this development methodology and it appears quite more intense but also allows for faster deliverables as opposed to the waterfall methodology.  I hope everything is going well, drop me a line sometime.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

