<?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>Effectual Working &#187; agile</title>
	<atom:link href="http://effectualworking.com/tag/agile/feed/" rel="self" type="application/rss+xml" />
	<link>http://effectualworking.com</link>
	<description>ef·fec·tu·al adj. Producing or sufficient to produce a desired effect; fully adequate.</description>
	<lastBuildDate>Thu, 08 Apr 2010 19:58:14 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Is Agile like No-Huddle?</title>
		<link>http://effectualworking.com/2009/05/is-agile-like-no-huddle/</link>
		<comments>http://effectualworking.com/2009/05/is-agile-like-no-huddle/#comments</comments>
		<pubDate>Thu, 28 May 2009 01:28:16 +0000</pubDate>
		<dc:creator>Mike</dc:creator>
				<category><![CDATA[Getting Things Done]]></category>
		<category><![CDATA[agile]]></category>

		<guid isPermaLink="false">http://effectualworking.com/?p=42</guid>
		<description><![CDATA[Perhaps smaller teams in coordinated efforts will improve speed to market?]]></description>
			<content:encoded><![CDATA[<p>If you are an industry underdog, then:</p>
<ul>
<li><em>&#8220;If you’re outmatched by the competition, isn’t it silly not to take a chance?&#8221;</em></li>
</ul>
<p>If you are the niche leader, then:</p>
<ul>
<li><em>&#8220;Right now, great teams (such as the Colts and Patriots) use the no-huddle selectively, as a way to maximize their dominance.&#8221;</em></li>
</ul>
<p>Hmmm…  <a href="http://www.37signals.com/svn/posts/1735-why-underdogs-should-take-more-chances" target="_self">Is agile software development, kinda like the no-huddle offense?</a></p>
<ul>
<li><em>&#8220;Why not put together a lighter, better-conditioned offensive line and a radically simplified playbook and see what happens?&#8221;</em></li>
</ul>
<p>Perhaps smaller teams in coordinated efforts will improve speed to market?</p>
<ul>
<li><em>&#8220;The strategy that’s right for heavyweights has nothing to do with how welterweights should fight.&#8221;</em></li>
</ul>
<p>Something to aspire to:</p>
<ul>
<li><em>&#8220;Generally, he’s doing so much more with so much less.&#8221;</em></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://effectualworking.com/2009/05/is-agile-like-no-huddle/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Beyond Functional Requirements</title>
		<link>http://effectualworking.com/2008/09/beyond-functional-requirements/</link>
		<comments>http://effectualworking.com/2008/09/beyond-functional-requirements/#comments</comments>
		<pubDate>Sat, 20 Sep 2008 01:38:18 +0000</pubDate>
		<dc:creator>Mike</dc:creator>
				<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Software Development]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[requirements]]></category>

		<guid isPermaLink="false">http://effectualworking.wordpress.com/?p=22</guid>
		<description><![CDATA[
Dr. Dobb&#8217;s Journal has an article called Beyond        Functional Requirements On Agile Projects in its October 2008        issue.  I think that it is not only worth reading for the subject        matter contained in [...]]]></description>
			<content:encoded><![CDATA[<div>
<div>Dr. Dobb&#8217;s Journal has an article called <a href="http://www.ddj.com/architect/210601918;jsessionid=HLTTN0S250EV4QSNDLOSKHSCJUNN2JVN" target="_blank">Beyond        Functional Requirements On Agile Projects</a> in its October 2008        issue.  I think that it is not only worth reading for the subject        matter contained in the title, but also for the view you will get of agile        software development.</div>
<div>Figure 1, in the article, shows the full system lifecycle when using        agile software development.  I especially appreciated the mention of        Iteration -1 and Iteration 0.  These two iterations are completed        before starting the Construction Lifecycle.  They include        pre-project activities (Iteration -1) and the Inception        Phase (Iteration 0).  The Inception Phase includes the work required        to get the project started, including initial modeling and planning.</div>
<div>The article makes mention of disciplined agile.  This        implies that you can also have undisciplined agile.  It&#8217;s all about        mastering your craft and this is important enough that the article        concludes with a strategy of Developer Education.</div>
<div>There is more to the article and it is well worth the        read.</div>
</div>
]]></content:encoded>
			<wfw:commentRss>http://effectualworking.com/2008/09/beyond-functional-requirements/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Prep. Work</title>
		<link>http://effectualworking.com/2008/03/prep-work/</link>
		<comments>http://effectualworking.com/2008/03/prep-work/#comments</comments>
		<pubDate>Tue, 04 Mar 2008 08:40:47 +0000</pubDate>
		<dc:creator>Mike</dc:creator>
				<category><![CDATA[Project Management]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[scrum]]></category>

		<guid isPermaLink="false">http://effectualworking.com/?p=5</guid>
		<description><![CDATA[Today, I am concentrating on prep. work for three planning sessions I have scheduled for Wed., Fri., and Mon.  The        goal for these sessions is to identify the remaining tasks that we know of, for interfaces and forms, on our project.  Next, we are going to [...]]]></description>
			<content:encoded><![CDATA[<p>Today, I am concentrating on prep. work for three planning sessions I have scheduled for Wed., Fri., and Mon.  The        goal for these sessions is to identify the remaining tasks that we know of, for interfaces and forms, on our project.  Next, we are going to prioritize and schedule these tasks into 4-week sprints.  Once this is done, I will add any new tasks into the project plan.</p>
]]></content:encoded>
			<wfw:commentRss>http://effectualworking.com/2008/03/prep-work/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
