<?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: Does an organisation need to be fully committed to agile/lean/scrum?</title>
	<atom:link href="http://www.markhneedham.com/blog/2010/03/11/does-an-organisation-need-to-be-fully-committed-to-agileleanscrum/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.markhneedham.com/blog/2010/03/11/does-an-organisation-need-to-be-fully-committed-to-agileleanscrum/</link>
	<description>Thoughts on Software Development</description>
	<lastBuildDate>Sat, 11 Feb 2012 23:17:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Luke Stubbles</title>
		<link>http://www.markhneedham.com/blog/2010/03/11/does-an-organisation-need-to-be-fully-committed-to-agileleanscrum/comment-page-1/#comment-33504</link>
		<dc:creator>Luke Stubbles</dc:creator>
		<pubDate>Tue, 16 Mar 2010 05:27:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=2246#comment-33504</guid>
		<description>Tools and practises are generally easier to teach and and easier to learn (not to mention measure), so many companies adopt them at a faster rate than the principles. This leaves a dangerous situation where you know how to use tools and practises but you don&#039;t know why you&#039;re using them. 

In this situation, teams will find it hard to adjust them to their unique project situation or understand how to challenge/adapt their use and thus continuously improve.</description>
		<content:encoded><![CDATA[<p>Tools and practises are generally easier to teach and and easier to learn (not to mention measure), so many companies adopt them at a faster rate than the principles. This leaves a dangerous situation where you know how to use tools and practises but you don&#8217;t know why you&#8217;re using them. </p>
<p>In this situation, teams will find it hard to adjust them to their unique project situation or understand how to challenge/adapt their use and thus continuously improve.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Garry</title>
		<link>http://www.markhneedham.com/blog/2010/03/11/does-an-organisation-need-to-be-fully-committed-to-agileleanscrum/comment-page-1/#comment-33269</link>
		<dc:creator>Garry</dc:creator>
		<pubDate>Fri, 12 Mar 2010 09:24:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=2246#comment-33269</guid>
		<description>The management at my company don&#039;t know the first thing about agile/lean, so we are certainly not an agile company. Having said that, I am slowly introducing the other devs to unit testing, code coverage and continuous integration. Hopefully bit by bit we can get the benefits of being at least partly agile.</description>
		<content:encoded><![CDATA[<p>The management at my company don&#8217;t know the first thing about agile/lean, so we are certainly not an agile company. Having said that, I am slowly introducing the other devs to unit testing, code coverage and continuous integration. Hopefully bit by bit we can get the benefits of being at least partly agile.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

