<?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: Agile Development</title>
	<atom:link href="http://lostechies.com/jasonmeridth/2007/09/10/agile-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://lostechies.com/jasonmeridth/2007/09/10/agile-development/</link>
	<description>Just another LosTechies site</description>
	<lastBuildDate>Thu, 29 Mar 2012 20:33:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Jason Meridth</title>
		<link>http://lostechies.com/jasonmeridth/2007/09/10/agile-development/#comment-84</link>
		<dc:creator>Jason Meridth</dc:creator>
		<pubDate>Mon, 10 Sep 2007 12:36:24 +0000</pubDate>
		<guid isPermaLink="false">/blogs/jason_meridth/archive/2007/09/09/agile-development.aspx#comment-84</guid>
		<description>Excellent extension to this post Josh.  I had heard all the history, but your summary does it justice.  Hope you are doing well bro.

Keeping the fight. :)</description>
		<content:encoded><![CDATA[<p>Excellent extension to this post Josh.  I had heard all the history, but your summary does it justice.  Hope you are doing well bro.</p>
<p>Keeping the fight. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jlockwood</title>
		<link>http://lostechies.com/jasonmeridth/2007/09/10/agile-development/#comment-83</link>
		<dc:creator>jlockwood</dc:creator>
		<pubDate>Mon, 10 Sep 2007 12:28:14 +0000</pubDate>
		<guid isPermaLink="false">/blogs/jason_meridth/archive/2007/09/09/agile-development.aspx#comment-83</guid>
		<description>Nice post...
Just a couple of quick notes (and history):

The addition of &#039;humility&#039; to the team&#039;s core values was inspired by the earlier writings of Scott Ambler as he was developing the concept of Agile Modeling (see Agile Modeling: Effective Practices for Extreme Programming and the Unified Process - Ambler).  We thought that humility was a key (and often missing) element in the typical approaches toward team development and threw it in once discovered.

Bellware and I were first trying to help the World Savings team we worked with (and that you work with now) move from a disfuntional water fall-based process to an agile approach (namely XP).  I think that we both lacked humility (and respect for that matter) at first when trying to sell the idea, largely due to our frustration with heavy resistance from team members on both development and business sides.  Had humility and respect been among our watchwords during the process things may have (may have I stress) gone a bit smoother.

At the time of the addition of &#039;humility&#039; to our XP-base core values, the XP core values were (initiated circa 1999):
1. Communication
2. Simplicity
3. Feedback
4. Courage

Over time, I think that the concept of humility has become integral to the team and part of its very culture.  I was quite impressed when seeing you guys work recently; the business and developers where playing quite well together and productivity was such that Wachovia has been forced to take notice in the post-merger environment.

As I saw on the link you provided, &#039;Respect&#039; has now been added to the list of XP core values.  &#039;Respect&#039; and &#039;Humility&#039; are not synonyms, but do seem to have a bit of mutual interdependence.  Without either, it&#039;s quite difficult to develop a cohesive team.  Agile development approaches, like many sports, rely heavily on team cohesion and good &#039;sportsmanship&#039; among the team&#039;s players in order for teams to &#039;win&#039;.

Finally, we did have Feathers come and he was helpful and inspirational (I want to be like him when I grow up...if I grow up).  He helped mainly with TDD in C# and introduced us to Fitnesse (this focused on the Simplicity and Feedback values).  The team building part, unfortunately, we had to figure out on our own.  

We brought our own Courage, figured out (through much trial and error) how to improve Communication and Feedback in a way that worked for us, and along the way learned just how important Humility is along the way in helping assure the first four values.

Keep up the good fight team Wachovia!</description>
		<content:encoded><![CDATA[<p>Nice post&#8230;<br />
Just a couple of quick notes (and history):</p>
<p>The addition of &#8216;humility&#8217; to the team&#8217;s core values was inspired by the earlier writings of Scott Ambler as he was developing the concept of Agile Modeling (see Agile Modeling: Effective Practices for Extreme Programming and the Unified Process &#8211; Ambler).  We thought that humility was a key (and often missing) element in the typical approaches toward team development and threw it in once discovered.</p>
<p>Bellware and I were first trying to help the World Savings team we worked with (and that you work with now) move from a disfuntional water fall-based process to an agile approach (namely XP).  I think that we both lacked humility (and respect for that matter) at first when trying to sell the idea, largely due to our frustration with heavy resistance from team members on both development and business sides.  Had humility and respect been among our watchwords during the process things may have (may have I stress) gone a bit smoother.</p>
<p>At the time of the addition of &#8216;humility&#8217; to our XP-base core values, the XP core values were (initiated circa 1999):<br />
1. Communication<br />
2. Simplicity<br />
3. Feedback<br />
4. Courage</p>
<p>Over time, I think that the concept of humility has become integral to the team and part of its very culture.  I was quite impressed when seeing you guys work recently; the business and developers where playing quite well together and productivity was such that Wachovia has been forced to take notice in the post-merger environment.</p>
<p>As I saw on the link you provided, &#8216;Respect&#8217; has now been added to the list of XP core values.  &#8216;Respect&#8217; and &#8216;Humility&#8217; are not synonyms, but do seem to have a bit of mutual interdependence.  Without either, it&#8217;s quite difficult to develop a cohesive team.  Agile development approaches, like many sports, rely heavily on team cohesion and good &#8216;sportsmanship&#8217; among the team&#8217;s players in order for teams to &#8216;win&#8217;.</p>
<p>Finally, we did have Feathers come and he was helpful and inspirational (I want to be like him when I grow up&#8230;if I grow up).  He helped mainly with TDD in C# and introduced us to Fitnesse (this focused on the Simplicity and Feedback values).  The team building part, unfortunately, we had to figure out on our own.  </p>
<p>We brought our own Courage, figured out (through much trial and error) how to improve Communication and Feedback in a way that worked for us, and along the way learned just how important Humility is along the way in helping assure the first four values.</p>
<p>Keep up the good fight team Wachovia!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Ocampo</title>
		<link>http://lostechies.com/jasonmeridth/2007/09/10/agile-development/#comment-82</link>
		<dc:creator>Joe Ocampo</dc:creator>
		<pubDate>Mon, 10 Sep 2007 04:13:53 +0000</pubDate>
		<guid isPermaLink="false">/blogs/jason_meridth/archive/2007/09/09/agile-development.aspx#comment-82</guid>
		<description>I prefer the term coach over Manager... :-)

Managers manage -- A coach leads!

Nice post.</description>
		<content:encoded><![CDATA[<p>I prefer the term coach over Manager&#8230; :-)</p>
<p>Managers manage &#8212; A coach leads!</p>
<p>Nice post.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
