<?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>AnotherKettleOfFish &#187; team-building</title>
	<atom:link href="http://anotherkettleoffish.com/weblog/category/team-building/feed/" rel="self" type="application/rss+xml" />
	<link>http://anotherkettleoffish.com/weblog</link>
	<description></description>
	<lastBuildDate>Fri, 26 Feb 2010 22:00:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>About Induction Management and Orientation</title>
		<link>http://anotherkettleoffish.com/weblog/2007/04/28/your-team-is-about-to-become-greater-than-the-sum-of-its-parts-once-again/</link>
		<comments>http://anotherkettleoffish.com/weblog/2007/04/28/your-team-is-about-to-become-greater-than-the-sum-of-its-parts-once-again/#comments</comments>
		<pubDate>Sat, 28 Apr 2007 21:29:39 +0000</pubDate>
		<dc:creator>anotherk</dc:creator>
				<category><![CDATA[team-building]]></category>

		<guid isPermaLink="false">http://anotherkettleoffish.com/weblog/2007/04/28/your-team-is-about-to-become-greater-than-the-sum-of-its-parts-once-again/</guid>
		<description><![CDATA[<p>Today you&#8217;ve got someone new joining your organization. It&#8217;s an important day. Every time someone joins your team is an important day. You don&#8217;t bring someone at the heart of your group without motives. Your team grows, you have plans, you&#8217;ve got expectations. As a result of this new hire, things will improve.</p>
<p>For her first [...]]]></description>
			<content:encoded><![CDATA[<p>Today you&#8217;ve got someone new joining your organization. It&#8217;s an important day. Every time someone joins your team is an important day. You don&#8217;t bring someone at the heart of your group without motives. Your team grows, you have plans, you&#8217;ve got expectations. As a result of this new hire, things will improve.</p>
<p><span id="more-13"></span>For her first day you may bring your new recruit around, present her to all your guys, just to say hello. A courtesy introduction, a quick, pleasant, sometimes &#8220;uneasy&#8221; discussion&#8230; then another one, with lots of replay of the same questions. Quite boring obligation really, but you don&#8217;t mind, it&#8217;s a one-shot and it has to done by someone.</p>
<p>This exercise though, is somewhat all loosing a bit of its initial intention. You &#8220;fail to convince&#8221; in making your team comfortable with this new &#8220;unknown element&#8221;. It may worth saying it, everyone seem a bit nervous about this new recruit starting in your organization. It quickly become obvious that it&#8217;s not only your new employee that you aim to put &#8220;at ease&#8221;; it&#8217;s also the most established members of your team.</p>
<p>And let&#8217;s face it, you&#8217;re a bit anxious yourself. It is very unlikely that your new recruit will &#8220;fit&#8221; in your organization without disturbing the chemistry of your place. On the other side of the coin there&#8217;s nothing wrong with that&#8230; it&#8217;s a challenge, you&#8217;re a middle manager; you like it. Your team is about to become more than the sum of its parts, things will soon get exciting.</p>
<p>You ideally <em>presume</em> that this person will find her feet and enjoy working for you from day-one. If so, you may take some time reconsidering this assumption.</p>
<p>As middle managers, we too often have this over-optimistic &#8220;welcoming&#8221; view of our organization. Unfortunately, what often occur is a month-long period of time where your new employee is literally left on her own, with the small consolation of having a pile of printed documents or a few pages from your intranet to read. And that&#8217;s the &#8220;best case&#8221; scenario&#8230; The worse case is being thrown to the deep ends first-day on, struggling to find your way, and re-surfacing with as much information about your place than the 1st day you came-in: in other words, not a lot.</p>
<p>But you&#8217;re thinking that your organization is too well structured to let this happen right? In the doubt, next time you&#8217;ve got a new hire starting, keep on eye on things. You may get surprised. That said, here&#8217;s a simple way to bring your new recruits up-to-speed when they come-in the door. Formalizing a training for each new recruit would be far too costly and hardly justifiable. You may be tempted to bring your new People under your wing, but such an approach is exhausting and Akof loves to think of your <em>middle-manager</em> time being too precious for that <img src='http://anotherkettleoffish.com/weblog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> . So drop the &#8220;coaching&#8221; thing&#8230; let it go, and consider a week-long &#8220;induction&#8221; to get your new People to get up-to-speed in a week time. Your goal is double: (1.) to provide an accurate picture and authentic view of your organization and (2.) to mix-up your people.</p>
<p>To this effect, get your new recruit to meet for 45 minutes or more with <em>everyone of your guys</em>, every hour, 8 hours a day. Set a quick agenda for the week, pick-up the People you feel comfortable explaining what they&#8217;re doing and get them to talk about their past achievements. The situations in which your People have the occasion to describe, value and sell your organization are seldom, but they exist. Organizing inductions for your new recruits is one of these. Don&#8217;t only select the &#8220;orators&#8221; of your team to speak with your new recruits. Let any of your guys giving the overview of what they do and how they do it. Let them tell their story and let your new People ask their own questions. Let the chemistry work between your People. Let your new recruits make their own opinion of your organization. You&#8217;ve got nothing to hide.</p>
<p>When you&#8217;ll see your People talking about their job and organization in front of new recruits, you&#8217;ll discover that they explain and present what they&#8217;re doing with a certain &#8220;<em>pride</em>&#8220;. Something magic happens&#8230; they try to <em>sell your organization</em> and do their best to show how they <em>contribute to its success</em>. It&#8217;s a form of internal marketing. It forces your guys to understand the organization they&#8217;re working-in before explaining its mechanisms to others. This requires an intellectual effort rarely expected from employees and this is too bad. You would not believe how much &#8220;informal&#8221; information they&#8217;ve got to communicate. None of it is written down, it&#8217;s all in the minds and brains of your People.</p>
<p>A new recruits&#8217; induction may not be a thorough, structured and flawless description of your organization by any mean, but there&#8217;s a lot to take-on and believe me, your new guys&#8217; heads will be about to explode after a week. They&#8217;ll be forced to make the distinction of what&#8217;s important from what&#8217;s not. They&#8217;ll criticize and filter the information they receive and ask &#8220;to-the-point&#8221; questions.</p>
<p>In other words, they&#8217;ll <em>engage</em>. And in return, your team will engage. If this happens, your &#8220;induction&#8221; is a success and your recruitment job is now complete.</p>
]]></content:encoded>
			<wfw:commentRss>http://anotherkettleoffish.com/weblog/2007/04/28/your-team-is-about-to-become-greater-than-the-sum-of-its-parts-once-again/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Sprint Zero</title>
		<link>http://anotherkettleoffish.com/weblog/2007/04/24/sprint-zero/</link>
		<comments>http://anotherkettleoffish.com/weblog/2007/04/24/sprint-zero/#comments</comments>
		<pubDate>Tue, 24 Apr 2007 15:25:01 +0000</pubDate>
		<dc:creator>anotherk</dc:creator>
				<category><![CDATA[coaching]]></category>
		<category><![CDATA[team-building]]></category>

		<guid isPermaLink="false">http://anotherkettleoffish.com/weblog/2007/04/24/sprint-zero/</guid>
		<description><![CDATA[<p>The next time you plan to build a Management Team, you may take some time reading about what the &#8220;Agile&#8221; literacy has to say about team-dynamics. Agile Management techniques have come a long way in the past seven years and come handy when time is scarce and uncertainty is a given (which is often to [...]]]></description>
			<content:encoded><![CDATA[<p>The next time you plan to build a Management Team, you may take some time reading about what the &#8220;Agile&#8221; literacy has to say about team-dynamics. <a href="http://en.wikipedia.org/wiki/Agile_management">Agile Management</a> techniques have come a long way in the past seven years and come handy when time is scarce and uncertainty is a given (which is often to be the case when building new teams).</p>
<p>Once again, and as you would expect, Akof&#8217;s goal isn&#8217;t to bring your attention on &#8220;yet another team-building framework&#8221;, but to provide you with an alternative approach to &#8220;classic&#8221; team-building techniques&#8230; so just consider it before recovering your copy of <a href="http://en.wikipedia.org/wiki/Meredith_Belbin">Belbin</a>&#8217;s books on <a href="http://www.amazon.com/Management-Teams-Second-Meredith-Belbin/dp/0750659106/ref=pd_bbs_sr_1/002-6393116-0165642?ie=UTF8&amp;s=books&amp;qid=1173046444&amp;sr=8-1">Management Teams</a> or organizing your next &#8216;off-site&#8217;. No doubt you&#8217;ve got all the &#8220;raw materials&#8221; to build your team. You&#8217;ve got all the &#8220;candidates&#8221; for the job in mind, there&#8217;s much to bet they &#8220;fit the bill&#8221; each in their respective roles&#8230; but the last thing you want is a Management Team that fails to recognize the benefits that teamwork provides, to the risk of fostering the symptoms of a dysfunctional organization.</p>
<p><span id="more-16"></span>Indeed, and as you are aware, in Management more than for any other discipline, what makes a Team successful is the ability of its members to work together. And this is the main challenge. &#8220;Gelling&#8221; strong, bright and self-confident middle-managers together. You need to forge &#8220;rock-solid&#8221; foundations and empower this &#8220;soon-to-be&#8221; team with the ability to kill &#8220;in the egg&#8221; emerging &#8217;silos&#8217; and personal agendas. No doubt that you&#8217;ll remind them that several times, starting with your off-site&#8230; but you will not be there forever.</p>
<p>So what you long for is a self-motivated and self-organized Management Team&#8230; and fortunately, this precisely where Agile Management frameworks can help you.<br />
You may have heard of &#8220;agility&#8221; relating to other disciplines than Management, maybe from the (now famous) &#8220;<a href="http://agilemanifesto.org/">Agile Manifesto</a>&#8220;. If not no worries, the few core <a href="http://agilemanifesto.org/principles.html">principles</a> governing agile frameworks are universal enough to make them eligible to other domains of expertise&#8230; including middle-management.</p>
<p>Agile principles implicitly provide a good bed for team Values; Agile teams must <em>harness change</em> instead of reacting to change. Agile teams are empowered (by you) to get the job done, deliver results frequently&#8230; with a preference to the shorter timescale. Agile teams are focused, they get together daily and privilege face-to-face conversation. More specifically, Agile Management teams undertake and curve-out managerial initiatives in &#8220;Projects&#8221;. Results are delivered in &#8220;<em>Sprints</em>&#8220;, a week-long and intense effort, leading to a clear and tangible result. To this effect, <em>Management Sprints</em> are a way to bring your Management Team through a journey of successive&#8230; well, <em>sprints</em>, each having a clear purpose and a length set-in-stone.</p>
<p>So now you get it&#8230; in the Agile Management world, team-dynamics emerge from:</p>
<p>1. Focused Teamwork Execution<br />
2. People&#8217;s Close Collaboration and<br />
3. Shared accountability on the Frequent Delivery of Results.</p>
<p>Every week, your newly formed Management Team achieves something TOGETHER, and each week, the team builds itself a bit more.<br />
So you&#8217;re cool with that? You want to give it a try? This is quite simple really, let&#8217;s begin with&#8230; <em>Sprint Zero</em>!</p>
<p>This cryptic name characterizes what will be in fact your initial brainstorming session. Nothing too complicated here. Get your Managers in room for a day (go off-site if you feel like it) and optionally bring a facilitator. Ask your guys to write on &#8216;posts-it&#8217; the topics that matter to them the most, then re-group these on &#8216;thematic&#8217; boards. As a rule of thumb, anything dear to their hart should be fine by you. Don&#8217;t filter, don&#8217;t push back. Be open-minded &#8230;you&#8217;re looking for ideas.</p>
<p>Your leaders will submit to your attention a substantial list of what they think your organization (and their team) should focus on. It can be about strategic intentions like it can be about infrastructure issues or people management&#8230; at this point anything is good enough.</p>
<p>&#8230;but DON&#8217;T PLAN (yet) and avoid setting milestones! <em>Resist to the temptation of setting-up timelines</em>. You may die to put things in shape at this point in time, but one of the promises of Agile Management frameworks is to &#8220;<a href="http://www.controlchaos.com/">manage chaos</a>&#8220;, so give it a chance and leave things at that. Your first job is simply to <em>close the initial Sprint</em>. At the end of this exercise, your Management Team has built its first tangible deliverable: an &#8220;<em>Objectives Backlog</em>&#8220;. The size of this &#8220;Backlog&#8221; may scare you a bit&#8230; but try not to think about how the hell your guys will ever get to the bottom of it.</p>
<p>Don&#8217;t prioritize the backlog on their behalf, and don&#8217;t set the main Objectives of your organization on their behalf. They&#8217;ll have to get to this point BY THEMSELVES, and that&#8217;s the purpose of the following &#8220;Sprints&#8221;&#8230; and the purpose of our following Post: &#8220;Sprint One to Many, Act on It!&#8221;, so stay tuned.</p>
]]></content:encoded>
			<wfw:commentRss>http://anotherkettleoffish.com/weblog/2007/04/24/sprint-zero/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
