<?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>The Project Shrink &#187; holistic</title>
	<atom:link href="http://www.projectshrink.com/tag/holistic/feed" rel="self" type="application/rss+xml" />
	<link>http://www.projectshrink.com</link>
	<description>Welcome To Shrinkonia.</description>
	<lastBuildDate>Thu, 17 May 2012 09:17:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>3 Steps Towards Becoming An Agile Project Manager</title>
		<link>http://www.projectshrink.com/become-agile-project-manager-217.html</link>
		<comments>http://www.projectshrink.com/become-agile-project-manager-217.html#comments</comments>
		<pubDate>Tue, 15 Apr 2008 19:07:25 +0000</pubDate>
		<dc:creator>Bas</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[concentration]]></category>
		<category><![CDATA[empathy]]></category>
		<category><![CDATA[holistic]]></category>
		<category><![CDATA[Leadership]]></category>
		<category><![CDATA[meditation]]></category>
		<category><![CDATA[project-management]]></category>
		<category><![CDATA[self-awareness]]></category>

		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=217</guid>
		<description><![CDATA[Change is the norm. Change is happening fast. The projects you are managing are not your daddy&#8217;s projects. To be able to handle the ever morphing environment, you need to become agile, flexible as you have never been before. &#8220;&#8221;If you are talking about &#8220;agile project managers&#8221;, this would be the key aspect of my &#8230;<p><a href="http://www.projectshrink.com/become-agile-project-manager-217.html">3 Steps Towards Becoming An Agile Project Manager</a> is a post from: <a href="http://www.projectshrink.com">Project Shrink</a>.

</p>
]]></description>
			<content:encoded><![CDATA[<p>Change is the norm. Change is happening fast. The projects you are managing are not your daddy&#8217;s projects. To be able to handle the ever morphing environment, you need to become agile, flexible as you have never been before. &#8220;&#8221;If you are talking about &#8220;agile project managers&#8221;, this would be the key aspect of my definition. A project manager that has a lot of mental models about projects available, and can adopt his mindset according the situation without problems, is what I call a true &#8220;agile&#8221; PM.&#8221; I wrote <a href="http://www.projectshrink.com/project-profiler-the-true-agile-pm-30.html">previously</a>.</p>
<p><img src="http://www.projectshrink.com/wp-content/uploads/2008/04/flexi.jpg" alt="" title="flexi" width="495" height="225" class="alignnone size-full wp-image-218" /><br />
<span id="more-217"></span></p>
<p><small>Photography by <a href="http://www.flickr.com/photos/angela7/75661005/">Angela7Dreams</a>.</small></p>
<p>To cope with the environment you need a brain that can use <a href="http://www.projectshrink.com/our-need-for-metaphors-139.html">many mental models to look at reality</a>. You need to be able to throw away your pre-programmed belief and adopt a different mindset in the blink of an eye.</p>
<p>The first part of becoming a flexible Project Manager therefor starts within the comfort of your own head. In this post I will outline the three steps that should guide your journey. In the next period each step will be explained in more detail.</p>
<p>These steps are similar to <a href="http://eq4pm.typepad.com/eq4pm/foundation-series-start-here.html">Emotional Intelligence</a>, however in this context it mostly relates to the actions you perform with the project.</p>
<p><strong>Self-Aware</strong></p>
<p>The first step is to become aware of <a href="http://www.projectshrink.com/project-management-code-214.html">why you do what you do</a>. Do you perform tasks because you are expected to do so, or do they really solve a problem or mitigate a risk? Are you aware of why you have <a href="http://www.softwareprojects.org/project_intake_organization211.htm">organized the project</a> in a certain way? Do you know the benefits and <a href="http://www.projectshrink.com/deviant-behavior-in-project-management-43.html">drawbacks of every procedure</a> you installed in your team?</p>
<p><strong>Emphatic</strong></p>
<p>After becoming self-aware you can start guessing why others are doing what they are doing. First you guess, later you ask. This is the same process to become self-aware, only this time you adopt different assumptions, take on a believe system that is not your own.</p>
<p>If you are used to run a country and you have a communist background, you probably are trying to regulate, centralize and formalize as much as possible. You want to control every individual behavior in order to control the whole system. When you are raised with a more laissez-faire world view, you can adopt a reign that is totally governed by the free market. Nothing is centrally controlled, everything will take care of itself. If you run one country, to become more emphatic, you will use the other mindset for a while.</p>
<p>This is the step where it is time you read up on your <a href="http://www.projectshrink.com/individual-behavior-what-i-want-120.html">psychology</a> and <a href="http://www.projectshrink.com/project-sociology-1-69.html">sociology</a> knowledge. This is were you defend the agile method point of view when you are a die-hard PMP.</p>
<p><strong>Holistic</strong></p>
<p>Free at last. Free at last.</p>
<p>In this final stage you are able to use all kind of mental models. You are aware of what triggers what. You can <a href="http://www.projectshrink.com/why-project-potion-9.html">mix and match</a> from different world views. You use an Agile planing within a Prince 2 organization. And you know why you use it! You get to know how to look at <a href="http://www.projectshrink.com/complexity-of-management-137.html">dynamic-complexity</a> without getting into a spasm. You come up with all new kind of weird mental models (like a <a href="http://www.projectshrink.com/introducing-the-fish-pond-196.html">Fish Pond</a> – eek).</p>
<p>This is the step where I get <a href="http://www.projectshrink.com/management-and-meditation-197.html">my little brass gong</a> out again&#8230; You are one! Ahum!</p>
<p><a href="http://www.projectshrink.com/become-agile-project-manager-217.html">3 Steps Towards Becoming An Agile Project Manager</a> is a post from: <a href="http://www.projectshrink.com">Project Shrink</a>.

</p>
]]></content:encoded>
			<wfw:commentRss>http://www.projectshrink.com/become-agile-project-manager-217.html/feed</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Reality Refuses To Follow Your Plan</title>
		<link>http://www.projectshrink.com/reality-refuses-to-follow-your-plan-76.html</link>
		<comments>http://www.projectshrink.com/reality-refuses-to-follow-your-plan-76.html#comments</comments>
		<pubDate>Fri, 14 Sep 2007 21:48:16 +0000</pubDate>
		<dc:creator>Bas</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Bertalanffy]]></category>
		<category><![CDATA[complexity]]></category>
		<category><![CDATA[cybernetics]]></category>
		<category><![CDATA[decarlo]]></category>
		<category><![CDATA[dynamic]]></category>
		<category><![CDATA[emergence]]></category>
		<category><![CDATA[fifth-discipline]]></category>
		<category><![CDATA[Freestyling]]></category>
		<category><![CDATA[holistic]]></category>
		<category><![CDATA[Models]]></category>
		<category><![CDATA[plan-driven]]></category>
		<category><![CDATA[predictions]]></category>
		<category><![CDATA[senge]]></category>
		<category><![CDATA[systems]]></category>
		<category><![CDATA[systems-theory]]></category>
		<category><![CDATA[systems-view]]></category>
		<category><![CDATA[wiener]]></category>

		<guid isPermaLink="false">http://blog.softwareprojects.org/reality-refuses-to-follow-your-plan-76.html</guid>
		<description><![CDATA[Project life can be quite frustrating when one day after another turns out not how you planned it. The software should be ready when you said it would. It has to. Otherwise you have people waiting, customers complaining and bosses getting annoyed. It is your reputation and ultimately your job on the line. If you &#8230;<p><a href="http://www.projectshrink.com/reality-refuses-to-follow-your-plan-76.html">Reality Refuses To Follow Your Plan</a> is a post from: <a href="http://www.projectshrink.com">Project Shrink</a>.

</p>
]]></description>
			<content:encoded><![CDATA[<div class="postimage">
<img src="http://www.projectshrink.com/images/what.jpg" border=0>
</div>
<p>Project life can be quite frustrating when one day after another turns out not how you planned it. The software should be ready when you said it would. It has to. Otherwise you have people waiting, customers complaining and bosses getting annoyed. It is your reputation and ultimately your job on the line. If you just plan harder, more detailed, than the plan must be correct. Right? Of course not. I know, it is becoming some kind of mantra for me, but, yes, it is a shocker for a lot of people, you can&#8217;t force reality in sticking to your plan. Forget it. It is not going to happen. Ever. Because it seems to be a habit hard to break, a state of mind hard to get rid of, it is worth spending a little closer look into this matter. Why can&#8217;t we predict project future?<br />
<span id="more-76"></span><br />
<b>Fifth Discipline</b></p>
<p>The answer starts with something called &#8220;The Fifth Discipline&#8221;. It sounds like some cult, some hush-hush society that guards a life-changing secret: the 5th Discipline. Although it was life changing for me, it is nothing like that. It is the title of a book by Peter Senge he wrote in the early 1990s [1]. He put forth the idea of &#8220;five disciplines&#8221; that have to be considered in improving business and organizations (Personal Mastery, Mental Models, Systems Thinking, Shared vision, and Team learning). Every discipline has its own merits, but for the topic at hand we will focus on one: systems thinking. For Senge an organization is viewed as multiple &#8220;systems&#8221; (or you may think about processes) that interact with each other. The systems are not viewed as linear, but more as loops that keep on repeating, until some change has been done. To give you an idea, consider the following example: A car repair shop has not much to do. So if a client comes with his car, he can be helped immediately. After a while worth of mouth about the speed of service, provides this repair shop with an increasing number of clients. As the number of clients grows, the waiting time for service also increases. When the service time takes to long, clients go away. Having fewer clients, again, the speed of service is up again.</p>
<p>In this short example, our main problem with reality becomes clear. It is called &#8220;dynamic complexity&#8221;. In our normal line of thinking, we think about an event A that happens, and that causes something else, say B. The occurrence of B might trigger some event C. A nice linear cause-and-effect chain. With dynamic complexity this is exactly what is not taking place: cause and effect are not close in space and time, and therefor, very difficult to see for us.</p>
<p>Another example: to increase productivity of a team, new fresh employees are added to the team. However, people need time to learn the ropes within the teams working environment, and with extra members to total communication overhead increases. Within small teams this may not have a large impact on the productivity of the individual team members, but as more and more new members are put to a team, the productivity gain will drop. It will probably plateau at a given moment, or, when teams are getting to large, too much new members are added simultaneously, etc. it may even drop.</p>
<p><b>Systems Theory</b></p>
<p>When you talk about it, it feels quite natural. It has a proper &#8220;yeah-this-is-how-it-works&#8221; touch to it. But mind you, it is quite a mental stretch for most of us. Between the great World Wars of the 20th century scientist Ludwig von Bertalanffy came up with a new way to look at things in physics, biology, economy, psychology, sociology and all other sciences; he formulated the General Systems Theory. In essence this view on the world consists of recognizing that independent elements make up something larger, something bigger, a unified whole. Although the elements are independent, they are influencing each other, the have a certain relation, they are related. This &#8220;whole&#8221; with its underlying elements is called &#8220;a system&#8221;.</p>
<p>Although the previous paragraph may throw your mind in a back flip, the concept of systems is quite an intuitive and natural thing; an organization consists of employees all working and communicating together, they make up the elements for the &#8220;whole&#8221; which in this case is the organization. Flows of air, the movements of water, the impact of sunshine are all the underlying elements that make up our weather system. Every individual buy or sell transaction make up our economy. You see, nothing to be scared here.</p>
<p>At a first glance this systems world view seems like an empty shell. You might wonder what it brings us? How can this help you and me? The answer is nicely formulated again by Senge [1]</p>
<blockquote><p>
&#8220;Business and other human endeavors are also systems. They, too, are bound by invisible fabrics of interrelated actions, which often take years to fully play out their effects on each other. Since we are part of that lacework ourselves, it&#8217;s doubly hard to see the whole pattern of change. Instead, we tend to focus on snapshots of isolated parts of the system, and wonder why our deepest problems never seem to get solved. Systems thinking is a conceptual framework (..) to make full patterns clearer and to help us see how to change them effectively.&#8221;
</p></blockquote>
<p>Another neat thing about systems is that across the whole spectrum of sciences, systems pop up that look the same or have similar behavior then systems in a different discipline. This allows is to beg-steal-and-borrow theories and models from different areas. Our toolbox to look at our own systems of interest has widely broadened.</p>
<p><b>Cybernetics</b></p>
<p>Closely related to the notion of systems is the concept of cybernetics, first formulated by the mathematician Wiener. This concept describes how a system communicates with its environment and based upon the feedback it gets from it, alters its behavior. If a group of animals will drink water from a well and one of the groups dies because of it, they entire group may search for a different well. If a company introduces a new product, and sees its stock plummeting because of it, it might change its strategy. The feedback mechanism comes in all sorts and shapes; they are the focus of cybernetics. The additional value this brings should be obvious; a system always lives within a context (a project within a larger organization for example) and this idea of communication/feedback provides us with an angle on how to look at this phenomena.</p>
<p>And new angles are precisely what we need to counter our idea of reality-following-the-plan. It is all a matter of changing our mindset. Doug DeCarlo almost dedicated half of his book Extreme Project Management [2] to convince us of this fact. In his opinion traditional managers hold a Newtonian view of the world, in the sense that events are linear, cause-and-effect can be nicely summed up in beautiful laws. In today&#8217;s world of dynamic complexity that model of the universe in your mind is not going to cut it for you: what you need is a quantum mindset. Exactly the kind of world view I am talking about!</p>
<p>If you are convinced that you cannot predict the future, your control loop becomes completely different. Traditional the thermostat model is used: reality is measured and compared against the plan. If reality is different than the plan, all effort is put into creating such a process that reality is in line with the plan again. If salespeople are not meeting their targets, they don&#8217;t get the bonus. This kind of carrot-stick management creates all kinds of unwanted behavior. Like people that are reporting what they are supposed the report to confirm the plan, regardless the actual real situation. Everything to avoid the stick.</p>
<p>When you have a quantum mindset, you know that reality cannot be planned. The thermostat model is therefore a ridiculous way of managing. More natural is the adoption of the scientific model: your forecast of the future is your expectation. If your forecasts are not in line with reality, your assumptions on which you based your expectations on, are not correct. You need to alter your mental model and try to come up with better forecasts.</p>
<p>[1] <a href="http://www.amazon.com/gp/product/0385517254?ie=UTF8&#038;tag=softwareproje-20&#038;linkCode=as2&#038;camp=1789&#038;creative=9325&#038;creativeASIN=0385517254">Senge, Peter, 5th Discipline</a><br />
[2] <a href="http://www.amazon.com/gp/product/0787974099?ie=UTF8&#038;tag=softwareproje-20&#038;linkCode=as2&#038;camp=1789&#038;creative=9325&#038;creativeASIN=0787974099">DeCarlo, Doug, Extreme Project Management</a></p>
<p><a href="http://www.projectshrink.com/reality-refuses-to-follow-your-plan-76.html">Reality Refuses To Follow Your Plan</a> is a post from: <a href="http://www.projectshrink.com">Project Shrink</a>.

</p>
]]></content:encoded>
			<wfw:commentRss>http://www.projectshrink.com/reality-refuses-to-follow-your-plan-76.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

