<?xml version="1.0" encoding="UTF-8"?>
<!--Generated by Squarespace Site Server v5.11.81 (http://www.squarespace.com/) on Wed, 30 May 2012 01:07:26 GMT--><feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"><title>Blog</title><subtitle>Blog</subtitle><id>http://www.agilelifestream.com/blog/</id><link rel="alternate" type="application/xhtml+xml" href="http://www.agilelifestream.com/blog/"/><link rel="self" type="application/atom+xml" href="http://www.agilelifestream.com/blog/atom.xml"/><updated>2012-02-11T14:25:01Z</updated><generator uri="http://www.squarespace.com/" version="Squarespace Site Server v5.11.81 (http://www.squarespace.com/)">Squarespace</generator><entry><title>Agile Lean Europe Network</title><category term="Agile"/><category term="Scrum"/><id>http://www.agilelifestream.com/blog/2011/3/28/agile-lean-europe-network.html</id><link rel="alternate" type="text/html" href="http://www.agilelifestream.com/blog/2011/3/28/agile-lean-europe-network.html"/><author><name>Voranc</name></author><published>2011-03-28T12:11:02Z</published><updated>2011-03-28T12:11:02Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>As an Agile enthusiast I'm always prepared to support and promote good Agile initiatives. A few weeks ago I got involved in <a href="http://www.linkedin.com/groups/Agile-Lean-Europe-ALE-3786271">Agile Lean Europe Network</a>, which is a group on LinkedIn that aims to improve the collaboration between Agile fans in Europe. It was initiated by <a href="http://www.jurgenappelo.com/">Jurgen Appelo</a> who is trying to move the countries in Europe a little closer together. You can read more about his great idea on his <a href="http://www.noop.nl/2011/03/how-to-move-europe.html">blog</a>.</p>
<p>First pan-European Agile gathering will be organised at <a href="http://xp2011.org/">XP2011</a>&nbsp;conference in Madrid. But, before the gathering each country should self-organize and prepare their statement of what they want from Europe.&nbsp;All agilists from Europe are invited to join local Agile communities in your country to prepare for the ALE gathering in Madrid. You can find more information about emerging local communities&nbsp;<a href="http://www.linkedin.com/groups/ALE-Gathering-XP2011-3786271.S.47736844">here</a>.</p>
<p>In Slovenia we have already started a discussion about this topic on our local LinkedIn group <a href="http://www.linkedin.com/groups?gid=2412623">Skram.si</a>.</p>
<p>See you all at XP2011.</p>]]></content></entry><entry><title>How To Use A Constellation To Jell A Team?</title><category term="Agile"/><category term="Productivity"/><category term="Project management"/><category term="Scrum"/><category term="Team"/><id>http://www.agilelifestream.com/blog/2011/1/25/how-to-use-a-constellation-to-jell-a-team.html</id><link rel="alternate" type="text/html" href="http://www.agilelifestream.com/blog/2011/1/25/how-to-use-a-constellation-to-jell-a-team.html"/><author><name>Voranc</name></author><published>2011-01-25T10:46:15Z</published><updated>2011-01-25T10:46:15Z</updated><content type="html" xml:lang="en-US"><![CDATA[<div></div>
<div><span class="full-image-float-right ssNonEditable"><span><img src="http://www.agilelifestream.com/storage/blog-pictures/Fotolia_22810885_XS_Constellation.jpg?__SQUARESPACE_CACHEVERSION=1295951458890" alt="" /></span></span>When you start new project you assemble a group of people to work on this project...this is the easy part of the job. The really hard part is to transform this group of people into an effective team that run like a well-oiled machine and that will successfully finish the project. And here is where most of the managers fail.</div>
<div>&nbsp;</div>
<div>It takes time for a team to jell because it takes time for team members to get to know each other and build trust. And this is a prerequisite for effective communication which is imperative for the project success. That's why you must create many opportunities for team members to get to know each other better. And one such opportunity&nbsp;is a <strong>C</strong><strong>onstellation </strong>exercise?</div>
<div>&nbsp;</div>
<div>The main purpose of this exercise is that the team members learn more about one another, see what other team members will do and not do, what they do and do not believe, and what they will and will not tolerate. It is especially useful at the beginning of a project when most team members do not know each other.</div>
<div>&nbsp;</div>
<div><strong>How to facilitate a constellation exercise?</strong></div>
<div>&nbsp;</div>
<div></div>
<div>Choose any object (chair, ball,...) and put it on the floor in the middle of the room. This object represents the center of the constellation and all team members should arrange themselves around this object. Tell them that you are going to read some statements, and as you read the statement they should gravitate toward or away from the center object in relation to how true the statement is for them. The more true the statement is for them, the closer to the center they should move.</div>
<div>After you read the statement everyone should move at the same time and they should not pay attention where other team members are moving. After everyone has moved they should all look around and see where other team members stand and they should feel the shape of the constellation. Once they have looked around, read the next statement.</div>
<div>After you read your statements, let the team members write their own statements. Collect all the statements and read it to the team.</div>
<div></div>
<div>&nbsp;</div>
<div>Here are some statements that can be used:</div>
<div>
<ul>
<li>I like to work alone</li>
<li>I am competitive</li>
<li>I like to facilitate meetings</li>
<li>I am a perfectionist</li>
<li>I like to learn new things</li>
<li>I like&nbsp;surprises</li>
<li>I like lots of documentation</li>
</ul>
</div>
<p>To learn more about the exercises that can help the team jell read a great book <a href="http://www.amazon.com/exec/obidos/ASIN/0321637704/agilelifestre-20">Coaching agile teams</a> written by Lyssa Adkins.</p>
<div></div>
<div></div>]]></content></entry><entry><title>The 3 A's of awesome</title><category term="Personal growth"/><id>http://www.agilelifestream.com/blog/2011/1/14/the-3-as-of-awesome.html</id><link rel="alternate" type="text/html" href="http://www.agilelifestream.com/blog/2011/1/14/the-3-as-of-awesome.html"/><author><name>Voranc</name></author><published>2011-01-14T09:01:32Z</published><updated>2011-01-14T09:01:32Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>If you are looking for something inspirational you should watch Neil Pasricha's&nbsp;great talk about awesome things in your life. I also recommend you to check his <a href="http://1000awesomethings.com/">blog</a>&nbsp;which won Webby Awards in 2009 for Best Blog&nbsp;or read his bestseller <a href="http://www.amazon.com/exec/obidos/ASIN/0399156518/agilelifestre-20">book</a>.</p>
<p style="text-align: center;"><object width="446" height="326"><param name="movie" value="http://video.ted.com/assets/player/swf/EmbedPlayer.swf"></param><param name="allowFullScreen" value="true" /><param name="allowScriptAccess" value="always"/><param name="wmode" value="transparent"></param><param name="bgColor" value="#ffffff"></param> <param name="flashvars" value="vu=http://video.ted.com/talks/dynamic/NeilPasricha_2010X-medium.flv&su=http://images.ted.com/images/ted/tedindex/embed-posters/NeilPasricha-2010X.embed_thumbnail.jpg&vw=432&vh=240&ap=0&ti=1048&introDuration=15330&adDuration=4000&postAdDuration=830&adKeys=talk=neil_pasricha_the_3_a_s_of_awesome;year=2010;theme=a_taste_of_tedx;theme=master_storytellers;theme=what_makes_us_happy;event=TEDxToronto+2010;&preAdTag=tconf.ted/embed;tile=1;sz=512x288;" /><embed src="http://video.ted.com/assets/player/swf/EmbedPlayer.swf" pluginspace="http://www.macromedia.com/go/getflashplayer" type="application/x-shockwave-flash" wmode="transparent" bgColor="#ffffff" width="446" height="326" allowFullScreen="true" allowScriptAccess="always" flashvars="vu=http://video.ted.com/talks/dynamic/NeilPasricha_2010X-medium.flv&su=http://images.ted.com/images/ted/tedindex/embed-posters/NeilPasricha-2010X.embed_thumbnail.jpg&vw=432&vh=240&ap=0&ti=1048&introDuration=15330&adDuration=4000&postAdDuration=830&adKeys=talk=neil_pasricha_the_3_a_s_of_awesome;year=2010;theme=a_taste_of_tedx;theme=master_storytellers;theme=what_makes_us_happy;event=TEDxToronto+2010;"></embed></object></p>]]></content></entry><entry><title>Agile Principle 2: Changing Requirements</title><category term="Agile"/><category term="Productivity"/><category term="Project management"/><category term="Scrum"/><id>http://www.agilelifestream.com/blog/2011/1/3/agile-principle-2-changing-requirements.html</id><link rel="alternate" type="text/html" href="http://www.agilelifestream.com/blog/2011/1/3/agile-principle-2-changing-requirements.html"/><author><name>Voranc</name></author><published>2011-01-03T14:13:00Z</published><updated>2011-01-03T14:13:00Z</updated><content type="html" xml:lang="en-US"><![CDATA[<div>
<div>This is the second post in the series of 12 posts about <a href="http://agilemanifesto.org/principles.html">Agile Manifesto Principles</a>.&nbsp;They are the foundation of all agile methodologies and every Scrum team member should be familiar with them.</div>
<div>&nbsp;</div>
<div></div>
<div>Here is the second principle, that talks about change:</div>
<div>&nbsp;</div>
<div></div>
<div></div>
<div></div>
<div></div>
<div></div>
<div>
<div id="_mcePaste">
<div id="_mcePaste" style="text-align: center; font-size: 110%;"><span style="font-size: 130%;"><strong>Welcome</strong> changing requirements, even late in&nbsp;</span></div>
<div id="_mcePaste" style="text-align: center; font-size: 110%;"><span style="font-size: 130%;">development. Agile processes <strong>harness</strong> change for&nbsp;</span></div>
<div id="_mcePaste" style="text-align: center; font-size: 110%;"><span style="font-size: 130%;">the customer's competitive advantage.</span></div>
</div>
</div>
<div></div>
<div></div>
<div>&nbsp;&nbsp;</div>
<div>In software development we all strive for a projects where customer would never change their minds. And we all know that will never happen because changes are inevitable in real world. Customers usually do not see a problem of changing requirements as a serious one.</div>
<div>&nbsp;</div>
<div>Traditional development process prefers sticking to their well-thought-out plans that are the result of the requirement-gathering phase.&nbsp;Introducing change late in the development process is costly because you need to repeat the whole waterfall process (analyse, design,...) for each change.</div>
<div>&nbsp;</div>
<div>Agile methods take a different approach and treat change as an expected and welcome part of every project. After all, it is all about <a href="http://www.agilelifestream.com/blog/2010/12/30/scrum-agile-manifesto-principle-1.html">satisfying the customer</a> because it is necessary to preserve customer's competitive advantage.</div>
<div>During the project&nbsp;the customer can continue to make changes, as long as they prioritize these changes in the appropriate iteration. Product owner is responsible for understanding of the customer needs and grooming the product backlog (prioritizing work based on business value) even near the end of the project.&nbsp;It is even better to make decisions later in the process when we have a better understanding of the product that we are building.&nbsp;Because a product backlog is a living thing that evolve constantly it can respond to the actions of customer's competitors. Agility is all about flexibility and being open to change is a big advantage.</div>
<div></div>
<div>&nbsp;</div>
<div></div>
<div>You need to remember the following two words about this principle:&nbsp;<strong>welcome</strong>&nbsp;(changing requirements) and <strong>harness</strong> (change)!</div>
<div></div>
<div>&nbsp;</div>
<div>You can find the explanation of the first principle&nbsp;<a href="http://www.agilelifestream.com/blog/2010/12/30/scrum-agile-manifesto-principle-1.html">here</a>.</div>
</div>]]></content></entry><entry><title>Scrum &amp; Agile Manifesto Principle 1</title><category term="Agile"/><category term="Productivity"/><category term="Project management"/><category term="Scrum"/><id>http://www.agilelifestream.com/blog/2010/12/30/scrum-agile-manifesto-principle-1.html</id><link rel="alternate" type="text/html" href="http://www.agilelifestream.com/blog/2010/12/30/scrum-agile-manifesto-principle-1.html"/><author><name>Voranc</name></author><published>2010-12-30T17:09:44Z</published><updated>2010-12-30T17:09:44Z</updated><content type="html" xml:lang="en-US"><![CDATA[<div></div>
<div>Many software development companies are striving to become more agile and the <a href="http://www.scrumalliance.org/">Scrum </a>is the agile buzzword #1 at the moment. The problem is that some companies or teams want to adopt Scrum just because they read about it on the internet and they are sure that if it is a simple agile&nbsp;framework&nbsp;it must be very easy using it. Besides, who wouldn't want to be more agile in these days?</div>
<div>Some people start using Scrum although they know almost nothing about the Scrum. It makes me really sad when I meet people with the following mindset "Scrum == Sprint". Yes, all they know about Scrum is that you have to work in some iterations called "Sprint". And at the end of the project they are so disappointed&nbsp;because the project was not as successful as they expected. That is because the Scrum is dramatically different from traditional sequential development.&nbsp;</div>
<div>&nbsp;</div>
<div></div>
<div>Every Scrum team member must be familiar with the basic values of Scrum.&nbsp;That's why I decided to wrote 12 posts about the foundation of all agile methodologies including Scrum:&nbsp;<a href="http://agilemanifesto.org/principles.html">Agile Manifesto Principles</a>. In every post I try to will explain one principle in a very simple way.</div>
<div>&nbsp;</div>
<div></div>
<div>Here is the first principle:</div>
<div>&nbsp;</div>
<div></div>
<div></div>
<div></div>
<div></div>
<div></div>
<div>
<div id="_mcePaste" style="text-align: center; font-size: 130%;"><span style="font-size: 110%;">Our highest priority is to <strong>satisfy</strong> the customer</span></div>
<div id="_mcePaste" style="text-align: center; font-size: 130%;"><span style="font-size: 110%;">through early and continuous delivery</span></div>
<div id="_mcePaste" style="text-align: center; font-size: 130%;"><span style="font-size: 110%;">of <strong>valuable </strong>software.</span></div>
</div>
<div></div>
<div></div>
<div>&nbsp;</div>
<div>At the start of the new project you have to answer one really big question, what exactly are we building? The short answer is, that you must build the software that is going to be of value to the customer and will satisfy their needs. But in the&nbsp;reality&nbsp;it is not so simple to achieve that.</div>
<div>&nbsp;</div>
<div>In the&nbsp;sequential development&nbsp;project you would first start with a lengthy up-front requirement-gathering phase. The result of this phase would be hundreds of pages of&nbsp;detailed&nbsp;requirements documentation where all features are equal important. Let's face it, the customer don't care about documents and UML diagrams and it is hard to get the right information from the customer and put it on the paper. They just want to get the software that maximizes the added value to their business and they don't know exactly what that value is on the first day of the project. There is a big chance that there will be some&nbsp;disappointment on the customer side when the software will be presented for the first time at the end of the project, although the software works as at it is described it the documentation.</div>
<div>&nbsp;</div>
<div>There is a total different story with Scrum teams which adapt early and continuous delivery of valuable software because the client is involved throughout the lifetime of the project. That is how you can get early customer feedback and valuable emergent requirements. Scrum team documents all the features in a product backlog, which is a master list of all desired functionality not yet in the product. Product backlog is also known as prioritized feature list and priority is assigned based on the items of most value to the business or that offer the earliest ROI and value.&nbsp;Product owner has to groom the product backlog continuously because items are added, removed and reprioritized each sprint as more is learned about the product being developed.&nbsp;The result is that the most important and highest-priority items are implemented first because they are found at the top of the product backlog.</div>
<div>&nbsp;</div>
<div></div>
<div>So, remember two words about this principle: <strong>satisfy</strong>&nbsp;(the customer) and <strong>valuable</strong> (software)!</div>
<div></div>
<div>&nbsp;</div>
<div></div>
<div></div>
<div></div>
<div></div>
<div></div>
<div></div>
<div>You can find a very brief explanation of agility <a href="http://www.agilelifestream.com/blog/2010/2/24/agile-explained.html">here</a>.</div>
<div></div>
<div></div>
<div></div>]]></content></entry><entry><title>Get Rid Of Unproductive Meetings With Six Thinking Hats</title><category term="Productivity"/><category term="Project management"/><category term="Team"/><id>http://www.agilelifestream.com/blog/2010/12/20/get-rid-of-unproductive-meetings-with-six-thinking-hats.html</id><link rel="alternate" type="text/html" href="http://www.agilelifestream.com/blog/2010/12/20/get-rid-of-unproductive-meetings-with-six-thinking-hats.html"/><author><name>Voranc</name></author><published>2010-12-20T14:26:43Z</published><updated>2010-12-20T14:26:43Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p><span class="full-image-float-right ssNonEditable"><span><img src="http://www.agilelifestream.com/storage/blog-pictures/Fotolia_8629800_XS_SixHats.jpg?__SQUARESPACE_CACHEVERSION=1292784942317" alt="" /></span></span></p>
<p>We are all very accustomed on traditional type of thinking which goes like this: "I am right, you are wrong". We usually try to build a logical argument to prove the other side is wrong. Thankfully there are better methods which forces you to move outside of this old habitual thinking style and closer to the fruitful thinking without attacking or judging. One such method is <strong><a href="http://en.wikipedia.org/wiki/Six_Thinking_Hats">Six Thinking Hats</a></strong>&nbsp;which is a thinking framework that provides an alternative to the argument.</p>
<p>This thinking method was invented by <a href="http://en.wikipedia.org/wiki/Edward_de_Bono">Dr. Edward de Bono</a> who is the leading international authority on creative thinking and lateral thinking guru. He has written more than 60 books, including the great book <a href="http://www.amazon.com/exec/obidos/ASIN/0316178314/agilelifestre-20">Six Thinking Hats</a>.</p>
<blockquote>
<p><em>An idea that is developed and put into action is more important than an idea that exists only as an idea.&nbsp;~Edward de Bono</em></p>
</blockquote>
<p>The Six Thinking Hats helps to accomplish the following:</p>
<ul>
<li>Separate out thinking so we can do one thing at a time.</li>
<li>Ask people to switch thinking from one mode to another.</li>
<li>Separate ego from performance.</li>
<li>Signal what thinking process we are going to use next.</li>
<li>Allow specific time for creativity.</li>
<li>Explore subjects in parallel.</li>
<li>Expand from one-dimensional to full-colored thinking.</li>
</ul>
<p>Imagine that you have six different hats. Each hat is a different color and represents a different type of thinking. For instance, if you want to be positive and find some benefits to some idea you just put the yellow hat on.</p>
<p>The hats and colors are designed to make <a href="http://en.wikipedia.org/wiki/Parallel_thinking">Parallel Thinking</a> a practical process. Parallel Thinking is getting everyone focused on using the same thinking tool at the same time and the goal is to think of many points under each different kind of hat.</p>
<p><strong>Blue Hat - Control:</strong>&nbsp;This hat manages the thinking process and sets the focus and agenda. It organizes the thinking and makes adjustments if the process isn't productive. It summarize the major points of the discussion and calls the group to make decisions. The hat is usually worn by the meeting facilitator.</p>
<p><strong>White Hat - Information:</strong>&nbsp;This hat focuses on facts, data and information available. It asks the following questions:</p>
<ul>
<li>What do we know?</li>
<li>What do we need to know?</li>
<li>Where can we get this information?</li>
</ul>
<p>It also looks at Other People's Views (O.P.V.) by asking the following questions:</p>
<ul>
<li>What views does this person or group have?</li>
<li>What information do we need from them?</li>
<li>How could we get this missing information?</li>
</ul>
<p><strong>Red Hat - Feelings:</strong>&nbsp;This hat is concerned with emotions, feelings, hunches and intuition. It does not require us to justify or explain the reasons for our feelings and it should be limited to 30 seconds. The key questions are:</p>
<ul>
<li>What are my feelings right now?</li>
<li>What does my intuition tell me?</li>
<li>What is my gut reaction?</li>
</ul>
<p><strong>Yellow Hat - Benefits:</strong>&nbsp;This hat is optimistic and represents the positive aspects of the situation. It is the opposite of black hat and it reinforces creative ideas and new directions. The key questions are:</p>
<ul>
<li>What are the benefits?</li>
<li>What are the positives?</li>
<li>What is the value here?</li>
</ul>
<p><strong>Black Hat - Judgment:</strong>&nbsp;This hat is gloomy and negative and is used to point out the weaknesses of the situation. This hat is usually overused because a lot of people place too much emphasis on critical thinking. The key questions are:</p>
<ul>
<li>What are the challenges - both existing and potential?</li>
<li>What are some of the difficulties?</li>
<li>What are the points for caution?</li>
<li>What are the risks?</li>
</ul>
<p><strong>Green Hat - Creativity:</strong>&nbsp;This hat is for creative and unconventional thinking. It encourages a search for new ideas and alternatives. The key questions are:</p>
<ul>
<li>Are there other ways to do this?</li>
<li>What else could we do here?</li>
<li>What are the possibilities?</li>
<li>What will overcome our black hat concerns?</li>
</ul>
<p>Six Thinking Hats can be used in various sequences (fixed, flexible or evolving) for different desired outcomes (process improvement, idea generation,...). The following sequence for instance can be used for problem solving:</p>
<ol>
<li>Blue Hat: Focus statement.</li>
<li>White Hat: What could be causing the problem?</li>
<li>Green Hat: Generate ideas to solve the problem.</li>
<li>Red Hat: Choose the best ideas.</li>
<li>Yellow Hat:What are the benefits of each idea?</li>
<li>Black Hat: What are the weaknesses of each idea?</li>
<li>Green Hat: Overcoming the weaknesses.</li>
<li>Blue Hat: What do we need to do, by when?</li>
</ol>]]></content></entry><entry><title>Why backpacking rocks?</title><category term="Personal growth"/><category term="Travel"/><id>http://www.agilelifestream.com/blog/2010/10/22/why-backpacking-rocks.html</id><link rel="alternate" type="text/html" href="http://www.agilelifestream.com/blog/2010/10/22/why-backpacking-rocks.html"/><author><name>Voranc</name></author><published>2010-10-22T08:16:30Z</published><updated>2010-10-22T08:16:30Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>The fact that I'm going to Nepal on Monday already makes me itch and&nbsp;scratching&nbsp;doesn't help. I almost forgot that great feeling because it is more than two years since my last backpacking trip to <a href="http://voranc.smugmug.com/Travel/Peru-Bolivia">Peru &amp; Bolivia</a>.</p>
<p>Me and my wife are true backpackers hence we only buy the flight tickets, Lonely Planet guide, pack our backpacks and go with the flow. We will spend the next month trekking in Nepal. We didn't decide yet between the Annapurna Circuit and Everest Base Camp trek, we will make the final decision when we arrive in Kathmandu.</p>
<blockquote>
<p>A good traveler has no fixed plans and is not intent on arriving. <em>~</em>Lao Tzu</p>
</blockquote>
<p>Backpacking is a life altering experience and&nbsp;here are some reasons to buy a flight ticket, pack your stuff and travel to the faraway places.</p>
<p><strong>Have fun. </strong>There is no rocket science in this one. Backpacking is fucking awesome and it is the best way to explore the world and enjoy while you are doing it.</p>
<p><strong>Meet a ton of cool people. </strong>While backpacking you meet the most genuine travelers. Nobody is hiding behind his social position or&nbsp;job title, nobody has the latest BMW to&nbsp;impress&nbsp;others, nobody stands out with his fancy clothes,... At the evening all the people in the hostel are talking what they have already experienced and where are they going tomorrow.</p>
<p><strong>Broaden your horizons. </strong>Visiting new cultures and new places will awaken some specific areas of your inner-self. It is also very educating and positive experience which expands your mind. Backpacking is quite challenging and you to learn to be more creative and flexible.&nbsp;You will definitely come back as a better person with a bunch of new knowledge about life.</p>
<p><strong>Relax and be happier. </strong>Life is really crazy these days. That's why it is really advisable to get away from the stress of everyday life. You will sense the real freedom because there are no limits and you can decide where to go and what to do in the last minute.</p>
<p>If you are still not convinced you MUST watch the following video. And if that video doesn't make you itch...then you are hopeless.</p>
<p>Namaste!</p>
<p><object width="640" height="385"><param name="movie" value="http://www.youtube.com/v/zlfKdbWwruY?fs=1&amp;hl=en_US"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/zlfKdbWwruY?fs=1&amp;hl=en_US" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="640" height="385"></embed></object></p>]]></content></entry><entry><title>What Is Between Stimulus And Response?</title><category term="Personal growth"/><category term="Productivity"/><id>http://www.agilelifestream.com/blog/2010/10/17/what-is-between-stimulus-and-response.html</id><link rel="alternate" type="text/html" href="http://www.agilelifestream.com/blog/2010/10/17/what-is-between-stimulus-and-response.html"/><author><name>Voranc</name></author><published>2010-10-17T13:28:32Z</published><updated>2010-10-17T13:28:32Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p><span class="full-image-float-right ssNonEditable"><span><img src="http://www.agilelifestream.com/storage/blog-pictures/Fotolia_8221723_XS_viktor_frankl.jpg?__SQUARESPACE_CACHEVERSION=1287144956286" alt="" /></span></span>Have you ever wondered why in a particular situation you unconsciously react like you do, although you sometimes regret your actions? Imagine that you could stop the time and thing for a few seconds to choose the most appropriate positive response in a given situation. Wouldn't it be great if you had that power. I can tell you that you are capable of doing this...OK, not to&nbsp;physically&nbsp;stop the time but at least to choose the right response.</p>
<p>Let me first tell you a fascinating story about <a href="http://en.wikipedia.org/wiki/Viktor_Frankl">Viktor E. Frankl</a>. He was an Austrian psychiatrist who was a prisoner in a concentration camp during World War II. One day he began to become aware that despite the daily torture he has a freedom his Nazi captors could not take away. Using the unique human endowments (self-awareness, imagination, conscience and independent will) he created his own freedom that was even bigger that the freedom of his Nazi captors. He exercised his freedom to the extend that he could decide how something was going to effect him and choose his own response. He called this freedom "the last of the human freedoms". He became an inspiration to those around him, even to some of the guards. Frankl survived the Holocaust and later wrote a great book called <a href="http://www.amazon.com/exec/obidos/ASIN/0807014273/agilelifestre-20">Man's Search for Meaning</a>.</p>
<blockquote>
<p>Between stimulus and response there is a space. In that space is our power to choose our response. In our response lies our growth and our freedom. <em>~</em>Viktor E. Frankl</p>
</blockquote>
<p><strong>There is a space called freedom of choice.</strong></p>
<p>Most people thing there is no space between stimulus and response. They skip this space between not realizing they have a choice because they are sure that things just happens.&nbsp;<strong>Between stimulus and response there is a space and in that space lies the freedom to choose.</strong>&nbsp;This freedom to choose is ours in every aspect of our lives.&nbsp;Humans are the only creatures on earth that have that tremendous power. Animals, for instance respond only by their instinct.&nbsp;A lot of people gave that power away and they just respond from their unconscious. They believe that every person is the product of genetics, environment and past experiences.</p>
<p><strong>Learn to use this space</strong></p>
<p>The first step&nbsp;toward being more proactive is to become aware of this space. Take a few deep breaths and&nbsp;listen to your subconscious after you&nbsp;receive some negative stimulus and try to sense this space before you response. Notice the script that it runs in the background and drive your response in the usual way. The next step is to become aware of your conscious and the freedom of choice. Try to replace your subconscious voice with the conscious one. Basically that means to change the old script with new "conscious" one. So, the next time you will be exposed to some stimuli stop for a moment, think about it and then respond.</p>
<p>Reacting to a stimulus without any thinking is a&nbsp;characteristic&nbsp;of a reactive person who is often affected by his physical and social environment.</p>
<p><strong>Conclusion</strong></p>
<p>Remember, you are totally responsible for how you react because you have the power to choose your response. Stop blaming your physical or social environment, parents, spouse, school, boss,...</p>
<p>If you want to learn more about this subject I suggest you read a book <a href="http://www.amazon.com/exec/obidos/ASIN/0743269519/agilelifestre-20">The 7 Habits of Highly Effective People</a>, written by Stephen R. Covey.</p>]]></content></entry><entry><title>Social Loafing - Free-riders vs. Suckers</title><category term="Productivity"/><category term="Project management"/><category term="Team"/><id>http://www.agilelifestream.com/blog/2010/8/29/social-loafing-free-riders-vs-suckers.html</id><link rel="alternate" type="text/html" href="http://www.agilelifestream.com/blog/2010/8/29/social-loafing-free-riders-vs-suckers.html"/><author><name>Voranc</name></author><published>2010-08-29T17:55:07Z</published><updated>2010-08-29T17:55:07Z</updated><content type="html" xml:lang="en-US"><![CDATA[<div></div>
<div>
<p><span class="full-image-float-right ssNonEditable"><span><img src="http://www.agilelifestream.com/storage/blog-pictures/Fotolia_21962577_XS_loafing.jpg?__SQUARESPACE_CACHEVERSION=1283087525873" alt="" /></span></span>Regarding to the fact that I'm a project manager I work with teams and team members most of my time. I'm also very keen on learning agile methodologies, hence I'm learning about <a href="http://www.scrumalliance.org/">Scrum&nbsp;</a>at the moment. While reading a book about Scrum I came across very interesting topic that drew my attention.</p>
</div>
<div>
<p>We can probably all agree that large teams with more than 10 people can be very unproductive because they provide a wonderful camouflage to lazy people.&nbsp;If you have ever worked in a large team you probably noticed that some team members were not working as efficient as they could. Why is that so? Some people have tendency to exert less effort when they believe there are others who will pick up the slack. The researchers call that phenomenon the&nbsp;<strong>Social Loafing</strong>. In short it says that the more people you throw at a problem, the less each contributes. In software development we have a well known <a href="http://en.wikipedia.org/wiki/Brooks's_law">Brook's law</a> which says that adding manpower to a late software project makes it even later.</p>
<blockquote>
<div id="_mcePaste">The simple act of paying positive attention to people has a great deal to do with productivity.&nbsp;<em>~</em>Thomas J. Peters&nbsp;</div>
</blockquote>
</div>
<div></div>
<div></div>
<div></div>
<div></div>
<div></div>
<div></div>
<div>
<p>Social loafing is also known as Ringelmann Effect, because it was first identified by French professor Maximilien Ringelmann in the 1913 when he measured the pressure exerted by individuals and teams pulling on a rope. He found that the sum of the individual pulls did not equal the total of the group pulls but it was less. For instance, group of eight people exhibited less than four times the individual average. The group result was much less then the sum of individual effort because the individual pulls harder alone than as part of a group.</p>
</div>
<div>Social loafing manifests in two ways:</div>
<div>
<ul>
<li><strong>free-rider</strong> effect - some individuals reduce their effort when they realise that the performance of the group will not suffer because of their lack of effort</li>
<li><strong>sucker </strong>effect - some individuals lower their effort in response to the free-riders attitude, to avoid being the "sucker"</li>
</ul>
</div>
<p>There are several ways to prevent the effects of social loafing within a group.<strong>&nbsp;</strong>Here are a few tips for avoiding social loafing:</p>
<ul>
<li><strong>Keep it small</strong> - a number of studies have shown that individual effort in inversely related to team size. Consequently, the ideal Scrum team size is five to nine individuals. For instance,&nbsp;<a href="http://www.amazon.com/">Amazon</a> refers to their teams as "two-pizza teams" meaning a team should be so small that can be fed with two pizzas.</li>
<li><strong>Emphasize team importance</strong> - when the team (project) is important to its members they work harder. Management can boost the team&rsquo;s morale by emphasizing the importance of the team and the value the team adds to the organization. Free-riding does not occur when team members feel that the project itself is important.</li>
<li><strong>Increase task visibility</strong> - make sure everyone in a team knows that they can easily be evaluated by others. Scrum solved this problem with a Scrum daily meeting during which each team member provides answers to the following three questions:&nbsp;What did you do yesterday? What will you do today? Are there any impediments in your way?</li>
<li><strong>Define responsibilities</strong> - roles and responsibilities have to very clear be defined upfront.</li>
</ul>
<p>Social loafing is a behavior that organizations want to eliminate, because it has negative impact on performance of organizations.&nbsp;Social loafing is most abundant in the organizations and teams that lack simple and open communication and where individuals are constantly dealing with undefined project goals, tasks and responsibilities.</p>
<p>An the game between free-riders and suckers can begin...</p>
<div></div>]]></content></entry><entry><title>Enjoy The Moment</title><category term="Personal growth"/><id>http://www.agilelifestream.com/blog/2010/8/24/enjoy-the-moment.html</id><link rel="alternate" type="text/html" href="http://www.agilelifestream.com/blog/2010/8/24/enjoy-the-moment.html"/><author><name>Voranc</name></author><published>2010-08-24T19:13:48Z</published><updated>2010-08-24T19:13:48Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p><a href="http://www.scottberkun.com/">Scott Berkun</a> mentioned this incredible video yesterday on his blog. The video if so beautiful that I feel obliged to share it with you.</p>
<blockquote>
<p>Life is a succession of moments. To live each one is to succeed. ~Coreta Kent</p>
</blockquote>
<p>I'm pretty sure most of us fail to be present in the moment because we are so busy every day finishing tasks written on out to-do lists. We all need to slow down a little and enjoy spontaneous moments on a daily basis. Enough talking...enjoy the video.</p>
<p><iframe src="http://player.vimeo.com/video/8189067?title=0&amp;portrait=0&amp;color=ffffff" width="400" height="225" frameborder="0"></iframe></p>
<p><a href="http://vimeo.com/8189067">Moments</a> from <a href="http://vimeo.com/everynone">Everynone</a> on <a href="http://vimeo.com">Vimeo</a>.</p>]]></content></entry></feed>
