<?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 for The Agile Forest</title>
	<atom:link href="http://agileforest.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://agileforest.com</link>
	<description>Enter the forest to find your path to agility.</description>
	<lastBuildDate>Sat, 30 Mar 2013 05:28:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on Purpose Driven Versus Opportunistic Agile Coaching by Ian G</title>
		<link>http://agileforest.com/2013/03/08/purpose-driven-versus-opportunistic-agile-coaching/#comment-839</link>
		<dc:creator><![CDATA[Ian G]]></dc:creator>
		<pubDate>Sat, 30 Mar 2013 05:28:39 +0000</pubDate>
		<guid isPermaLink="false">http://agileforest.com/?p=699#comment-839</guid>
		<description><![CDATA[Why does it have to be Purpose or Opportunistic coaching, couldn&#039;t you do both?  Many people advocate a Contingent Leadership style based upon flexing the appraoch to meet the needs of the monent but doing that within an overall guiding framework or direction.  Moss Beth Kanter, the organisational academic talks about Teachable Moments as a way keeping Leaders open to opportunities to develop their staff that occur randomly.  Its not that far from the appraoch Andrew mentions.]]></description>
		<content:encoded><![CDATA[<p>Why does it have to be Purpose or Opportunistic coaching, couldn&#8217;t you do both?  Many people advocate a Contingent Leadership style based upon flexing the appraoch to meet the needs of the monent but doing that within an overall guiding framework or direction.  Moss Beth Kanter, the organisational academic talks about Teachable Moments as a way keeping Leaders open to opportunities to develop their staff that occur randomly.  Its not that far from the appraoch Andrew mentions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Short cut for hiring the right type of leader? by Ian G</title>
		<link>http://agileforest.com/2013/03/23/short-cut-for-hiring-the-right-type-of-leader/#comment-837</link>
		<dc:creator><![CDATA[Ian G]]></dc:creator>
		<pubDate>Fri, 29 Mar 2013 04:22:03 +0000</pubDate>
		<guid isPermaLink="false">http://agileforest.com/?p=711#comment-837</guid>
		<description><![CDATA[I agree with Erwin, the question could have the opposite effect and attract someone who would enjoy the challenge of changing that organisation.  Some organisations also work on the premises that interviews should be challenging and hard so that people who lack persistence don&#039;t get through, McKinsey is one organisation like this that springs to mind.]]></description>
		<content:encoded><![CDATA[<p>I agree with Erwin, the question could have the opposite effect and attract someone who would enjoy the challenge of changing that organisation.  Some organisations also work on the premises that interviews should be challenging and hard so that people who lack persistence don&#8217;t get through, McKinsey is one organisation like this that springs to mind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Short cut for hiring the right type of leader? by Erwin van der Koogh (@evanderkoogh)</title>
		<link>http://agileforest.com/2013/03/23/short-cut-for-hiring-the-right-type-of-leader/#comment-834</link>
		<dc:creator><![CDATA[Erwin van der Koogh (@evanderkoogh)]]></dc:creator>
		<pubDate>Wed, 27 Mar 2013 15:44:27 +0000</pubDate>
		<guid isPermaLink="false">http://agileforest.com/?p=711#comment-834</guid>
		<description><![CDATA[It also wouldn&#039;t work as an interview question.
I was asked exactly this question for an IT manager position. A department of 30 lazy, unmotivated developers who did whatever they damn well pleased. They needed a strong leader to set the vision and get people to follow it. Someone that wasn&#039;t afraid to make difficult choices and do whatever was necessary to get the IT department back on track.

I said yes immediately. Would have been a great challenge. It wasn&#039;t of course about changing all the developers, but the mindset of management of the company.
Too bad in the end they did choose a &#039;real&#039; hardliner :(]]></description>
		<content:encoded><![CDATA[<p>It also wouldn&#8217;t work as an interview question.<br />
I was asked exactly this question for an IT manager position. A department of 30 lazy, unmotivated developers who did whatever they damn well pleased. They needed a strong leader to set the vision and get people to follow it. Someone that wasn&#8217;t afraid to make difficult choices and do whatever was necessary to get the IT department back on track.</p>
<p>I said yes immediately. Would have been a great challenge. It wasn&#8217;t of course about changing all the developers, but the mindset of management of the company.<br />
Too bad in the end they did choose a &#8216;real&#8217; hardliner <img src='http://s0.wp.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Short cut for hiring the right type of leader? by Renee Troughton</title>
		<link>http://agileforest.com/2013/03/23/short-cut-for-hiring-the-right-type-of-leader/#comment-826</link>
		<dc:creator><![CDATA[Renee Troughton]]></dc:creator>
		<pubDate>Sat, 23 Mar 2013 10:52:24 +0000</pubDate>
		<guid isPermaLink="false">http://agileforest.com/?p=711#comment-826</guid>
		<description><![CDATA[Good point Robert.]]></description>
		<content:encoded><![CDATA[<p>Good point Robert.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Short cut for hiring the right type of leader? by Robert Watkins</title>
		<link>http://agileforest.com/2013/03/23/short-cut-for-hiring-the-right-type-of-leader/#comment-825</link>
		<dc:creator><![CDATA[Robert Watkins]]></dc:creator>
		<pubDate>Sat, 23 Mar 2013 07:54:07 +0000</pubDate>
		<guid isPermaLink="false">http://agileforest.com/?p=711#comment-825</guid>
		<description><![CDATA[No. An Agile leader wouldn&#039;t want to work for an organisation that played that sort of game in the interview process.]]></description>
		<content:encoded><![CDATA[<p>No. An Agile leader wouldn&#8217;t want to work for an organisation that played that sort of game in the interview process.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sprint 0: The Goal, Activities and the Term by Vin D'Amico</title>
		<link>http://agileforest.com/2013/03/13/sprint-0-the-goal-activities-and-the-term/#comment-817</link>
		<dc:creator><![CDATA[Vin D'Amico]]></dc:creator>
		<pubDate>Thu, 14 Mar 2013 16:29:05 +0000</pubDate>
		<guid isPermaLink="false">http://agileforest.com/?p=704#comment-817</guid>
		<description><![CDATA[Excellent post! I&#039;ve written about sprint zero too. I think it makes the most sense in enterprise environments. Large, complex problems need additional up-front analysis and definition. Diving in too soon results in lots of refactoring or worse, throw-away code.

It&#039;s not just about delivering production software. The software we deliver needs to have staying power. It needs to survive until the final release. If you&#039;re doing too much refactoring, you&#039;re on the path to failure.]]></description>
		<content:encoded><![CDATA[<p>Excellent post! I&#8217;ve written about sprint zero too. I think it makes the most sense in enterprise environments. Large, complex problems need additional up-front analysis and definition. Diving in too soon results in lots of refactoring or worse, throw-away code.</p>
<p>It&#8217;s not just about delivering production software. The software we deliver needs to have staying power. It needs to survive until the final release. If you&#8217;re doing too much refactoring, you&#8217;re on the path to failure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sprint 0: The Goal, Activities and the Term by postagilist</title>
		<link>http://agileforest.com/2013/03/13/sprint-0-the-goal-activities-and-the-term/#comment-816</link>
		<dc:creator><![CDATA[postagilist]]></dc:creator>
		<pubDate>Wed, 13 Mar 2013 18:18:48 +0000</pubDate>
		<guid isPermaLink="false">http://agileforest.com/?p=704#comment-816</guid>
		<description><![CDATA[When I started out, software was an R&amp;D process.

Research and Development.

A &quot;sprint 0&quot; is research.... and there should be plenty of it.

Modern software development in general, and scrum in particular, is far too focussed on D, D, D and little to no R.

Doing the right R can help with the D quite a bit.

We need more research, prototyping, analysis, etc, up front --- people who deny that are simply impulsive and not well rounded.

We really need to move to prototyping -- not potentially shipping things. Once the requirements have been narrowed down then you can start worry about making the features that survive the prototyping process (eg are wanted) into production level code.

Making the prototype be potentially shippable from the onset is madness.

PA]]></description>
		<content:encoded><![CDATA[<p>When I started out, software was an R&amp;D process.</p>
<p>Research and Development.</p>
<p>A &#8220;sprint 0&#8243; is research&#8230;. and there should be plenty of it.</p>
<p>Modern software development in general, and scrum in particular, is far too focussed on D, D, D and little to no R.</p>
<p>Doing the right R can help with the D quite a bit.</p>
<p>We need more research, prototyping, analysis, etc, up front &#8212; people who deny that are simply impulsive and not well rounded.</p>
<p>We really need to move to prototyping &#8212; not potentially shipping things. Once the requirements have been narrowed down then you can start worry about making the features that survive the prototyping process (eg are wanted) into production level code.</p>
<p>Making the prototype be potentially shippable from the onset is madness.</p>
<p>PA</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sprint 0: The Goal, Activities and the Term by Tom Howlett</title>
		<link>http://agileforest.com/2013/03/13/sprint-0-the-goal-activities-and-the-term/#comment-814</link>
		<dc:creator><![CDATA[Tom Howlett]]></dc:creator>
		<pubDate>Wed, 13 Mar 2013 09:27:23 +0000</pubDate>
		<guid isPermaLink="false">http://agileforest.com/?p=704#comment-814</guid>
		<description><![CDATA[In my experience you don&#039;t really find out what you need to enable delivery until you try to do it and the idea of a Sprint 0 by any name makes me very uncomfortable. Surely the purpose of your first sprint should be to deliver something, however small. Most of that first sprint might be spent removing the initial impediments to delivery and hopefully learning about each others needs on your cross functional team,  but at least you start with the same purpose as every other sprint, to deliver some value to the customer, rather than guessing what you will need to enable that.]]></description>
		<content:encoded><![CDATA[<p>In my experience you don&#8217;t really find out what you need to enable delivery until you try to do it and the idea of a Sprint 0 by any name makes me very uncomfortable. Surely the purpose of your first sprint should be to deliver something, however small. Most of that first sprint might be spent removing the initial impediments to delivery and hopefully learning about each others needs on your cross functional team,  but at least you start with the same purpose as every other sprint, to deliver some value to the customer, rather than guessing what you will need to enable that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Purpose Driven Versus Opportunistic Agile Coaching by Andrew Rusling</title>
		<link>http://agileforest.com/2013/03/08/purpose-driven-versus-opportunistic-agile-coaching/#comment-811</link>
		<dc:creator><![CDATA[Andrew Rusling]]></dc:creator>
		<pubDate>Sat, 09 Mar 2013 08:43:13 +0000</pubDate>
		<guid isPermaLink="false">http://agileforest.com/?p=699#comment-811</guid>
		<description><![CDATA[In my most recent role, I was able to achieve a good mix of the two approaches.

Working with the management team, we would identified a team or group or practice that needed my focused attention. This would receive most of my attention (Purpose Driven). 

However I was never expected to put everything I had into the Purpose Driven item. This allowed me to observe other teams, people, etc and to spot issues that needed addressing. I could apply Opportunistic Coaching when the time was right. 

Sometimes the items that I identified in an Opportunistic way, changed to be my main focus.

This approach, closely matches my preferred working style. Strong Focus in one area to deliver solid results. However keeping my eyes open to other opportunities. I suspect I would feel a bit constrained if I had to work purely in a Purpose Driven Approach.]]></description>
		<content:encoded><![CDATA[<p>In my most recent role, I was able to achieve a good mix of the two approaches.</p>
<p>Working with the management team, we would identified a team or group or practice that needed my focused attention. This would receive most of my attention (Purpose Driven). </p>
<p>However I was never expected to put everything I had into the Purpose Driven item. This allowed me to observe other teams, people, etc and to spot issues that needed addressing. I could apply Opportunistic Coaching when the time was right. </p>
<p>Sometimes the items that I identified in an Opportunistic way, changed to be my main focus.</p>
<p>This approach, closely matches my preferred working style. Strong Focus in one area to deliver solid results. However keeping my eyes open to other opportunities. I suspect I would feel a bit constrained if I had to work purely in a Purpose Driven Approach.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A quick reflection on Agile Australia 2011 by Agile Australia June 2011 &#124; The Agile Revolution</title>
		<link>http://agileforest.com/2011/06/17/a-quick-reflection-on-agile-australia-2011/#comment-810</link>
		<dc:creator><![CDATA[Agile Australia June 2011 &#124; The Agile Revolution]]></dc:creator>
		<pubDate>Sat, 09 Mar 2013 01:02:44 +0000</pubDate>
		<guid isPermaLink="false">http://agileforest.com/?p=116#comment-810</guid>
		<description><![CDATA[[...] you can checkout Renee&#8217;s blog of the event and Craig&#8217;s at day 1 and day [...]]]></description>
		<content:encoded><![CDATA[<p>[...] you can checkout Renee&#8217;s blog of the event and Craig&#8217;s at day 1 and day [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
