<?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>Unbound DNA &#187; Motivation</title>
	<atom:link href="http://www.unbounddna.com/category/motivation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.unbounddna.com</link>
	<description></description>
	<lastBuildDate>Fri, 20 Aug 2021 09:00:00 +0000</lastBuildDate>
	<language>en-US</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=3.9.40</generator>
	<item>
		<title>Agile transformations: Process model or thinking model shift?</title>
		<link>http://agileforest.com/2013/07/12/agile-transformations-process-model-or-thinking-model-shift/</link>
		<comments>http://agileforest.com/2013/07/12/agile-transformations-process-model-or-thinking-model-shift/#comments</comments>
		<pubDate>Fri, 12 Jul 2013 11:53:45 +0000</pubDate>
		<dc:creator><![CDATA[Renee Troughton]]></dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[Culture]]></category>
		<category><![CDATA[Kanban]]></category>
		<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[Motivation]]></category>
		<category><![CDATA[Stoos]]></category>

		<guid isPermaLink="false">http://agileforest.com/?p=743</guid>
		<description><![CDATA[For those that have been on the Agile journey for a while this post will hopefully come as no surprise, but if you are fairly new on the journey I wanted to take the opportunity to clarify what I feel is a common misconception about Agile. In the early days of Agile we made it [&#8230;]<img alt="" border="0" src="http://pixel.wp.com/b.gif?host=agileforest.com&#38;blog=18989035&#38;post=743&#38;subd=agileforest&#38;ref=&#38;feed=1" width="1" height="1">]]></description>
				<content:encoded><![CDATA[<p>For those that have been on the Agile journey for a while this post will hopefully come as no surprise, but if you are fairly new on the journey I wanted to take the opportunity to clarify what I feel is a common misconception about Agile.</p>
<p>In the early days of Agile we made it a Waterfall versus Agile war. It was one or the other. One over the other. This when &#8216;x&#8217;, that when &#8216;y&#8217;. We spent time explaining the pitfalls of Waterfall and why Agile was better. Maybe that was right at the time. Maybe we did it because we didn&#8217;t know better. Whatever the reason the concept of an Agile transformation being replace old process with Agile has stuck around.</p>
<p>But I don&#8217;t think that the point of an Agile transformation is a process shift.</p>
<p>I have a suspicion that where Agile has succeeded, it did so not because of the process shift but because of something else &#8211; a thinking model shift.</p>
<p>What was the problem that we were trying to fix with Agile? Was it really the process or the mindsets that people had? The manifesto articulates it somewhat &#8211; &#8220;Individuals and interactions over processes and tools&#8221;. It isn&#8217;t that process isn&#8217;t important it is that the thinking model that process should always trump was broken and that some slack should be given to humans who may have felt that the process didn&#8217;t make sense given the complexity of the situation.</p>
<p>Somehow, despite the manifesto, when we began Agile transformations we ignored the &#8220;over processes and tools&#8221; somewhere along the line. Frameworks and certifications are springing up everywhere &#8211; SAFe, Kanban certification, Disciplined Agile Certification, ICAgile, Scrum, etc. How many of these are focused on process and technique over the ability to shift thinking models?</p>
<p>What I feel Agile should be is different now than it once was. What I feel the manifesto should be now, is more along the lines of:</p>
<blockquote><p>We are uncovering better ways of working together as human beings to deliver value  to shareholders and delight to customers whilst at the same time improving the engagement of employees. Through this we have come to value:</p>
<ol>
<li>Synergistic thinking over mechanistic/analytic thinking</li>
<li>Servant and situational leadership over command and control management (alt: unleashed human potential over apathetic or toxic environments)</li>
<li>Full value stream optimization over sub process optimization</li>
<li>Process experimentation over defined process</li>
<li>Aggressive feedback controls over prolonged feedback controls</li>
<li>Stimulated neurological pathways over stagnant neurological pathways (alt: learning culture over sole focus on delivery culture)</li>
<li>Breathing space to enable creativity and innovation over 100%(+) utilization</li>
</ol>
<p>That is to say whilst the things on the right are our current behaviours, we want to shift to the items on the left</p>
<p>&nbsp;</p></blockquote><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/agileforest.wordpress.com/743/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/agileforest.wordpress.com/743/" /></a> <img alt="" border="0" src="http://pixel.wp.com/b.gif?host=agileforest.com&#038;blog=18989035&%23038;post=743&%23038;subd=agileforest&%23038;ref=&%23038;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://agileforest.com/2013/07/12/agile-transformations-process-model-or-thinking-model-shift/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
<enclosure url="http://0.gravatar.com/avatar/035e0749e7963c84320b255067ae9e9a?s=96&#038;d=monsterid&#038;r=G" length="0" type="" />
		</item>
	</channel>
</rss>
