<?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>TastyCupcakes.com &#187; servant leadership</title>
	<atom:link href="http://blog.tastycupcakes.com/tag/servant-leadership/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.tastycupcakes.com</link>
	<description>Fuel for Software Professionals</description>
	<lastBuildDate>Wed, 07 Jul 2010 15:23:14 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Project Pinwheel</title>
		<link>http://blog.tastycupcakes.com/2009/11/project-pinwheel/</link>
		<comments>http://blog.tastycupcakes.com/2009/11/project-pinwheel/#comments</comments>
		<pubDate>Mon, 09 Nov 2009 00:28:43 +0000</pubDate>
		<dc:creator><a href="http://scrumofscrums.blogspot.com" rel="nofollow">Andre Simones</a></dc:creator>
				<category><![CDATA[All Games]]></category>
		<category><![CDATA[Team Dynamics]]></category>
		<category><![CDATA[empowerment]]></category>
		<category><![CDATA[self organization]]></category>
		<category><![CDATA[servant leadership]]></category>

		<guid isPermaLink="false">http://blog.tastycupcakes.com/?p=360</guid>
		<description><![CDATA[<p>I've only conducted the exercise once with a group of technical managers and directors.  The response was very positive, and now I can refer to this exercise when there is a need to trust and empower the team.</p> [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Timing:</strong></p>
<p>15-20 minutes</p>
<p><strong>Ingredients:</strong></p>
<p>Each table (with 5-6 students) has a plastic shoe-box containing enough supplies for 20 pinwheels (would need less most likely). Make sure that you make samples of what the pinwheels are supposed to look like for each group.  HOWEVER, make sure that the sample pinwheels are not in the shoebox at first.  The students should not even know they exist.  Here&#8217;s the supplies in each box.</p>
<ol>
<li>Straws</li>
<li>Paper fasteners</li>
<li>Paper copies of the pinwheel pattern to cut out</li>
<li>Scissors</li>
<li>Markers</li>
<li>Paper punch</li>
<li>Shoe-box size plastic containers (to hold the supplies at each table)</li>
</ol>
<p><strong>Recipe:</strong></p>
<p>This is conducted in two rounds, with three slides (two slides in round 1, and one additional slide for round 2).</p>
<p><strong><em>Round 1</em></strong></p>
<p><em>Slide 1</em></p>
<blockquote><p>Your job is to create as many pinwheels as you can in 5 minutes.  Take a minute, and assign the following roles at each table:</p>
<ul>
<li>Cutter &#8211; owns the scissors and completes the cutting</li>
<li>Decorator/Designer &#8211; owns the markers and creates the design for the pinwheel</li>
<li>Hole Puncher &amp; Paper Fastener &#8211; owns the hole puncher and the paper fasteners</li>
<li>Folder &#8211; does any necessary manipulation or folding of the paper during the creation of the pinwheel</li>
<li>Tester &#8211; tests the pinwheel when it has been finished.  Verify that it has been decorated and that it at least moves a little when someone blows.</li>
<li>Manager &#8211; responsible for telling each team member what to do.  The manager will communicate the tasks to the team members.  The team members are not allowed to see the instructions.</li>
</ul>
</blockquote>
<p><em>Slide 2</em></p>
<blockquote>
<ul>
<li>At your table there is a box.  Each box contains the instructions and the supplies.</li>
<li>No one is allowed to step outside their role.</li>
<li>The manager is the only one that can speak, by instructing the team members.  Each team member is only allowed to speak to the manager.</li>
<li>If the pinwheel fails testing, the tester must hand the pinwheel back to who they think caused the “bug”.</li>
</ul>
</blockquote>
<p>At this point, the teams DO NOT see the sample.  They don&#8217;t even know a sample exists</p>
<p>Now, start the timer.  After 5 minutes, they will likely create 0 pinwheels.</p>
<p><strong><em>Round 2</em></strong></p>
<p><em>Slide 1</em></p>
<blockquote>
<ul>
<li>Manager, you are now a servant leader.  Please do whatever it takes to help the team.</li>
<li>Team members are allowed to help others out.</li>
<li>You can cross role boundaries.</li>
<li>Everyone can read the instructions.  You can use the instructions as a guideline, but you can now be creative in how you create the pinwheels.</li>
<li>First, take 2 minutes to discuss how you will work together to be more efficient.  Then, you will have 5 minutes to create as many pinwheels as possible.</li>
</ul>
</blockquote>
<p>Here, the team goes through a time-boxed planning session of 2 minutes to figure out how to best make the pinwheels before the 5 minute pin-wheel making session.  I also pull out the sample pinwheel, so the team can have a collective understanding of what the &#8220;vision&#8221; is.</p>
<p>During this second round, the teams made between 5-10 pinwheels.  The ones who made less had issues with the &#8220;servant leader&#8221; concept, which made for a great discussion afterwords.</p>
<p>This is a bit of a pain in the butt to set up, but in the end, it is WELL worth it, and now I have the supplies for many classes to come!</p>
<p><strong>Learning Points:</strong></p>
<p>This exercise illustrates the following points.</p>
<ul>
<li>Cross functional team work</li>
<li>Self organizing teams are more effective than those teams under a command-and-control regime</li>
<li>Team members must be able to cross functional silos to be the most efficient</li>
<li>Managers are the most effective when they are serving the team, not telling the team what to do</li>
<li>Over-specialization causes bottle-necks (you&#8217;ll notice that some functions will be far ahead of others, such as the &#8220;cutters&#8221;, and others will be far behind, such as the designers)</li>
<li>It&#8217;s important for the team to take time to retrospect and plan together</li>
</ul>
<p>It is up to you whether you discuss after each round what was experienced.  I only had the discussion at the end, and compared and contrasted the ways of working.  I plan on introducing lean concepts in subsequent sessions, such as &#8220;eliminate waste&#8221;.  The &#8220;cutters&#8221; tended to stack the papers and cut out lots of patterns, which introduced a lot of waste in the end, as the hole punchers, folders and designers couldn&#8217;t keep up.  I may add a round 3 to illustrate this.</p>
<p><a href="http://blog.tastycupcakes.com/wp-content/uploads/360/pinwheel_instructions_and_cutout.zip">pinwheel_instructions_and_cutout.zip (93 KB)</a></p>
<p>This post was submitted by <a href="http://scrumofscrums.blogspot.com" rel="nofollow">Andre Simones</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://blog.tastycupcakes.com/2009/11/project-pinwheel/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
