<?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 for Wizewerx</title>
	<atom:link href="http://wizewerx.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://wizewerx.com</link>
	<description>helping you get awesome.</description>
	<lastBuildDate>Mon, 23 Jan 2012 02:22:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>Comment on We want to be agile. by Wes Williams</title>
		<link>http://wizewerx.com/blog/2012/we-want-to-be-agile/#comment-1220</link>
		<dc:creator>Wes Williams</dc:creator>
		<pubDate>Mon, 23 Jan 2012 02:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://wizewerx.com/?p=1266#comment-1220</guid>
		<description>Hey Mike, Most places I have coached at, either as an employee or a consultant, do know what they want. They want a process that is more predictable for a fixed budget and fixed schedule. Well, that is, groups that seem to be the type you are talking about where some senior manager is trying to push agile. They here agile will make them faster, which we both is not quite correct. They are looking for a better way to manage them out of the mess they are in. In most cases the business people and upper management are not happy with the speed at which they deliver software.
Picking agile to make software delivery faster usually leads them down a wrong path and they end up disliking agile because it did not make them faster and more predictable. They end up in a semi-iterative mess.

First of all their goal was wrong. The goal rarely mentions the customer and making them happy or it is a side note. Since the main goal is to go faster they usually appear to get this at the beginning, because everyone knows what is really wanted, but they cannot sustain it.

Secondly they do not have a quality focus. By quality I mean delivering a solution that meets the customers needs, is maintainable and allow them to continue to move forward at a sustainable pace. My first point deals with the lack of customer focus but they also do not have development and testing teams with the skill set or mindset required to deliver software iteratively. Developers are not trained do TDD and/or they write minimal unit tests. Testers and developers (and customers/product owners) do not work closely together to create a common understanding and then automate the verification of that understanding. e.g. Agile become purely a planning and management initiative.

Of course there are several mindset changes that do not happen at the organization level in order to allow the previous two items to happen. It is rarely admitted that quality starts at the top and senior leaders have set the expectations that drive a lot of the behaviors that lead to bad quality and unhappy customers. Budgeting is usually done in a way that encourages teams to continue a funded project even when it clearly becomes a bad direction. Organizations are setup to pit developers, testers and business people against each other. And many more.

I have seem many, even most, coaches identify and work to correct all of these issues but a coach can usually only guide and influence and changing an organization is difficult. Add to that difficulty the fact that most corporations reward senior leaders for short term profits and meeting wall streets predictions it becomes even more difficult.

I think what I just wrote sounds like there is no hope. :) Real agile however will take a general change of mindset and the bad economy may help with that but I am sure not going to say it will for sure. In the meantime we just need to keep pushing our ideas in hope that someone will get desperate enough to listen and really try them.</description>
		<content:encoded><![CDATA[<p>Hey Mike, Most places I have coached at, either as an employee or a consultant, do know what they want. They want a process that is more predictable for a fixed budget and fixed schedule. Well, that is, groups that seem to be the type you are talking about where some senior manager is trying to push agile. They here agile will make them faster, which we both is not quite correct. They are looking for a better way to manage them out of the mess they are in. In most cases the business people and upper management are not happy with the speed at which they deliver software.<br />
Picking agile to make software delivery faster usually leads them down a wrong path and they end up disliking agile because it did not make them faster and more predictable. They end up in a semi-iterative mess.</p>
<p>First of all their goal was wrong. The goal rarely mentions the customer and making them happy or it is a side note. Since the main goal is to go faster they usually appear to get this at the beginning, because everyone knows what is really wanted, but they cannot sustain it.</p>
<p>Secondly they do not have a quality focus. By quality I mean delivering a solution that meets the customers needs, is maintainable and allow them to continue to move forward at a sustainable pace. My first point deals with the lack of customer focus but they also do not have development and testing teams with the skill set or mindset required to deliver software iteratively. Developers are not trained do TDD and/or they write minimal unit tests. Testers and developers (and customers/product owners) do not work closely together to create a common understanding and then automate the verification of that understanding. e.g. Agile become purely a planning and management initiative.</p>
<p>Of course there are several mindset changes that do not happen at the organization level in order to allow the previous two items to happen. It is rarely admitted that quality starts at the top and senior leaders have set the expectations that drive a lot of the behaviors that lead to bad quality and unhappy customers. Budgeting is usually done in a way that encourages teams to continue a funded project even when it clearly becomes a bad direction. Organizations are setup to pit developers, testers and business people against each other. And many more.</p>
<p>I have seem many, even most, coaches identify and work to correct all of these issues but a coach can usually only guide and influence and changing an organization is difficult. Add to that difficulty the fact that most corporations reward senior leaders for short term profits and meeting wall streets predictions it becomes even more difficult.</p>
<p>I think what I just wrote sounds like there is no hope. <img src='http://wizewerx.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  Real agile however will take a general change of mindset and the bad economy may help with that but I am sure not going to say it will for sure. In the meantime we just need to keep pushing our ideas in hope that someone will get desperate enough to listen and really try them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on We want to be agile. by Anonymous</title>
		<link>http://wizewerx.com/blog/2012/we-want-to-be-agile/#comment-1219</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sat, 21 Jan 2012 21:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://wizewerx.com/?p=1266#comment-1219</guid>
		<description>Many of the coaches I have worked with also rock and help steer clients through what the outcomes the client is seeking.  There are a fair few coaches also who do not recognise this issue.

The ranty nature of this post is mostly because I haven&#039;t blogged in a while, the real aim of this was not to rage on coaches who don&#039;t work the way I do or value the things I value, instead it was really to highlight that organisations often don&#039;t know what they want in the process they ask for and it is the very essence of agility for the coach to collaborate with the customer to deliver a working process that delivers highest value and continuous feedback and help the customer organisation towards the outcomes they desire.

Thanks for your contribution and helping me think this through a bit more.</description>
		<content:encoded><![CDATA[<p>Many of the coaches I have worked with also rock and help steer clients through what the outcomes the client is seeking.  There are a fair few coaches also who do not recognise this issue.</p>
<p>The ranty nature of this post is mostly because I haven&#8217;t blogged in a while, the real aim of this was not to rage on coaches who don&#8217;t work the way I do or value the things I value, instead it was really to highlight that organisations often don&#8217;t know what they want in the process they ask for and it is the very essence of agility for the coach to collaborate with the customer to deliver a working process that delivers highest value and continuous feedback and help the customer organisation towards the outcomes they desire.</p>
<p>Thanks for your contribution and helping me think this through a bit more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on We want to be agile. by Agile Scout</title>
		<link>http://wizewerx.com/blog/2012/we-want-to-be-agile/#comment-1218</link>
		<dc:creator>Agile Scout</dc:creator>
		<pubDate>Sat, 21 Jan 2012 17:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://wizewerx.com/?p=1266#comment-1218</guid>
		<description>99% in agreement with you here. Not sure the caliber of coaches you&#039;ve worked with, but I&#039;d say that almost 80% of the coaches I&#039;ve worked with kick serious ass. 
I&#039;m glad your blogging about this and bringing this up. The more we talk about it, hopefully it&#039;ll get better. As with any type of business opportunity, there will be the zealots, the theorists, the pragmatists, the d0-ers, and the fakers. </description>
		<content:encoded><![CDATA[<p>99% in agreement with you here. Not sure the caliber of coaches you&#8217;ve worked with, but I&#8217;d say that almost 80% of the coaches I&#8217;ve worked with kick serious ass. <br />
I&#8217;m glad your blogging about this and bringing this up. The more we talk about it, hopefully it&#8217;ll get better. As with any type of business opportunity, there will be the zealots, the theorists, the pragmatists, the d0-ers, and the fakers. </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on We want to be agile. by Ola Hyltén</title>
		<link>http://wizewerx.com/blog/2012/we-want-to-be-agile/#comment-1217</link>
		<dc:creator>Ola Hyltén</dc:creator>
		<pubDate>Thu, 19 Jan 2012 13:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://wizewerx.com/?p=1266#comment-1217</guid>
		<description>Good one! Being a professional sometimes means that you recommend &quot;Don&#039;t go there&quot; and that may of course mean less income for you as a consultant so it can be difficult to stay honest. Being honest is on the other hand what we need to be if we wanna stay in business and sleep well at night! 
The buzz word problem is what it is. Agile is a great example. I bet you come across a lot of different expectations on &quot;Going Agile&quot; and various more or less poorly stated definitions of Agile at the ones who believe it&#039;s a silver bullet solution and very out &quot;Make us Agile please, oh great guru&quot;
Staying honest, to yourself and your clients, sometimes takes not only a solid backbone but also a lot of teaching!</description>
		<content:encoded><![CDATA[<p>Good one! Being a professional sometimes means that you recommend &#8220;Don&#8217;t go there&#8221; and that may of course mean less income for you as a consultant so it can be difficult to stay honest. Being honest is on the other hand what we need to be if we wanna stay in business and sleep well at night!<br />
The buzz word problem is what it is. Agile is a great example. I bet you come across a lot of different expectations on &#8220;Going Agile&#8221; and various more or less poorly stated definitions of Agile at the ones who believe it&#8217;s a silver bullet solution and very out &#8220;Make us Agile please, oh great guru&#8221;<br />
Staying honest, to yourself and your clients, sometimes takes not only a solid backbone but also a lot of teaching!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on My Ideas Tree by ALE2011 conference in Berlin &#8211; Status Updates &#171; OlafLewitz</title>
		<link>http://wizewerx.com/blog/2011/my-ideas-tree/#comment-1154</link>
		<dc:creator>ALE2011 conference in Berlin &#8211; Status Updates &#171; OlafLewitz</dc:creator>
		<pubDate>Wed, 18 May 2011 00:23:15 +0000</pubDate>
		<guid isPermaLink="false">http://wizewerx.com/?p=1234#comment-1154</guid>
		<description>[...] program will consist of 30 minute talks in the morning and open space in the afternoon. The idea farmer Mike Sutton will facilitate the Open Space, and the grumpy old skeptic coach Rachel Davies kindly committed to [...]</description>
		<content:encoded><![CDATA[<p>[...] program will consist of 30 minute talks in the morning and open space in the afternoon. The idea farmer Mike Sutton will facilitate the Open Space, and the grumpy old skeptic coach Rachel Davies kindly committed to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on My Ideas Tree by Ash Sheikh</title>
		<link>http://wizewerx.com/blog/2011/my-ideas-tree/#comment-1136</link>
		<dc:creator>Ash Sheikh</dc:creator>
		<pubDate>Thu, 07 Apr 2011 15:37:00 +0000</pubDate>
		<guid isPermaLink="false">http://wizewerx.com/?p=1234#comment-1136</guid>
		<description>Mike, i&#039;ve been engrossed in your posting and have taken inspiration with me and in it&#039;s place i leave thanks.
Ash</description>
		<content:encoded><![CDATA[<p>Mike, i&#8217;ve been engrossed in your posting and have taken inspiration with me and in it&#8217;s place i leave thanks.<br />
Ash</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A View on Tribes by Olaf Lewitz</title>
		<link>http://wizewerx.com/blog/2011/a-view-on-tribes/#comment-1053</link>
		<dc:creator>Olaf Lewitz</dc:creator>
		<pubDate>Tue, 08 Feb 2011 00:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://wizewerx.com/?p=1155#comment-1053</guid>
		<description>Mike,
love this post. Enlightening in multiple ways—thanks so much for sharing this.
take care
Olaf</description>
		<content:encoded><![CDATA[<p>Mike,<br />
love this post. Enlightening in multiple ways—thanks so much for sharing this.<br />
take care<br />
Olaf</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Shower Monologues: Software Craftsmanship and the Choir  &#8211; Part 1 by Tobias Mayer</title>
		<link>http://wizewerx.com/blog/2011/the-shower-monologues-software-craftsmanship-and-the-choir-part-1/#comment-1047</link>
		<dc:creator>Tobias Mayer</dc:creator>
		<pubDate>Mon, 24 Jan 2011 21:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://wizewerx.com/?p=1201#comment-1047</guid>
		<description>Nice distinction Mike. </description>
		<content:encoded><![CDATA[<p>Nice distinction Mike.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Shower Monologues: Software Craftsmanship and the Choir  &#8211; Part 1 by Michael Bedward</title>
		<link>http://wizewerx.com/blog/2011/the-shower-monologues-software-craftsmanship-and-the-choir-part-1/#comment-1046</link>
		<dc:creator>Michael Bedward</dc:creator>
		<pubDate>Thu, 20 Jan 2011 01:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://wizewerx.com/?p=1201#comment-1046</guid>
		<description>Very well put.

As someone with a deep passion for, and appreciation of, software craftmanship I couldn&#039;t give a toss about the upper case version or its manifesto.
</description>
		<content:encoded><![CDATA[<p>Very well put.</p>
<p>As someone with a deep passion for, and appreciation of, software craftmanship I couldn&#8217;t give a toss about the upper case version or its manifesto.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Shower Monologues: Software Craftsmanship and the Choir  &#8211; Part 1 by George Dinwiddie</title>
		<link>http://wizewerx.com/blog/2011/the-shower-monologues-software-craftsmanship-and-the-choir-part-1/#comment-1045</link>
		<dc:creator>George Dinwiddie</dc:creator>
		<pubDate>Wed, 19 Jan 2011 18:32:00 +0000</pubDate>
		<guid isPermaLink="false">http://wizewerx.com/?p=1201#comment-1045</guid>
		<description>Good questions, Mike.  I think the manifesto was an attempt to call attention to the need for more people to care about craftsmanship.  It if becomes a movement to certify who&#039;s a craftman and who&#039;s not--well, then it&#039;s missed the boat completely.

Who anoints someone as a master craftsman?

I say no one.  Being a master is what we may strive to achieve.  It&#039;s not a destination.  It&#039;s not an award bestowed on us. </description>
		<content:encoded><![CDATA[<p>Good questions, Mike.  I think the manifesto was an attempt to call attention to the need for more people to care about craftsmanship.  It if becomes a movement to certify who&#8217;s a craftman and who&#8217;s not&#8211;well, then it&#8217;s missed the boat completely.</p>
<p>Who anoints someone as a master craftsman?</p>
<p>I say no one.  Being a master is what we may strive to achieve.  It&#8217;s not a destination.  It&#8217;s not an award bestowed on us.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Served from: wizewerx.com @ 2012-02-06 07:35:37 -->
