<?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>Thomas Koeppen Blog &#187; 2007 &#187; May</title>
	<atom:link href="http://thomaskoeppen.com/2007/05/feed/" rel="self" type="application/rss+xml" />
	<link>http://thomaskoeppen.com</link>
	<description>steady for every message</description>
	<lastBuildDate>Mon, 08 Feb 2010 22:08:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>What is a leader?</title>
		<link>http://thomaskoeppen.com/2007/05/19/what-is-a-leader/</link>
		<comments>http://thomaskoeppen.com/2007/05/19/what-is-a-leader/#comments</comments>
		<pubDate>Sat, 19 May 2007 19:06:04 +0000</pubDate>
		<dc:creator>thomas</dc:creator>
				<category><![CDATA[business]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[leadership]]></category>

		<guid isPermaLink="false">http://blog.thomaskoeppen.com/pages/viewpage.action?pageId=3833881</guid>
		<description><![CDATA[I found a nice description from http://www.agileadvice.com/ : &#8220;A leader is a person who assists a group of people become a self-organizing, self-managing and self-sustaining team so that he/she no longer has to be a leader for that group.&#8221; This is an interesting definition in contrast to the wikipedia one: House defines &#8220;leadership&#8221; organizationally and [...]]]></description>
			<content:encoded><![CDATA[<p>I found a nice description from <a href="http://www.agileadvice.com/" rel="nofollow">http://www.agileadvice.com/</a> :</p>
<p>&#8220;A leader is a person who assists a group of people become a self-organizing, self-managing and self-sustaining team so that he/she no longer has to be a leader for that group.&#8221;</p>
<p>This is an interesting definition in contrast to the wikipedia one:</p>
<blockquote>
<p>House defines &#8220;leadership&#8221; organizationally and narrowly as &#8220;the ability of an individual to influence, motivate, and enable others to contribute toward the effectiveness and success of the organizations of which they are members&#8221;. Organizationally, leadership directly impacts the effectiveness of costs, revenue generation, service, satisfaction, earnings, market value, share price, social capital, motivation, engagement, and sustainability. Leadership is the ability of an individual to set an example for others and lead from the front. It is an attitude that influences the environment around us.</p>
</blockquote>
<p>Read more: <a href="http://en.wikipedia.org/wiki/Leadership" rel="nofollow">http://en.wikipedia.org/wiki/Leadership</a></p>
<p><a href="http://www.agileaxioms.com/"><img style="border:0" src="http://www.agileaxioms.com/AgileAxioms.png" alt="Agile Axioms" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://thomaskoeppen.com/2007/05/19/what-is-a-leader/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Pitching Agile to Top Management</title>
		<link>http://thomaskoeppen.com/2007/05/19/pitching-agile-to-top-management/</link>
		<comments>http://thomaskoeppen.com/2007/05/19/pitching-agile-to-top-management/#comments</comments>
		<pubDate>Sat, 19 May 2007 13:04:27 +0000</pubDate>
		<dc:creator>thomas</dc:creator>
				<category><![CDATA[business]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[management]]></category>

		<guid isPermaLink="false">http://blog.thomaskoeppen.com/display/blog/2007/05/19/Pitching+Agile+to+Top+Management</guid>
		<description><![CDATA[Scott Ambler&#8217;s latest DDJ article covers a topic that is important for us: Pitching Agile to Senior Management &#8211; This inability to articulate to senior management why they should adopt agile techniques is ironic considering our focus on communication. Ambler&#8217;s experience is that management is often very willing to become more agile if you&#8217;re able [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.ambysoft.com" rel="nofollow">Scott Ambler&#8217;s </a> latest DDJ article covers a topic that is important for us:</p>
<p>Pitching Agile to Senior Management &#8211; This inability to articulate to senior management why they should adopt agile techniques is ironic considering our focus on communication. Ambler&#8217;s experience is that management is often very willing to become more agile if you&#8217;re able to describe to them the costs and benefits in an understandable and meaningful way.</p>
<p>Read more: <a href="http://www.ddj.com/dept/architect/199300107" rel="nofollow">http://www.ddj.com/dept/architect/199300107</a></p>
<p><a href="http://thomaskoeppen.com/wp-content/uploads/2008/07/070501sa01_f1.gif"><img src="http://thomaskoeppen.com/wp-content/uploads/2008/07/070501sa01_f1.gif" alt="" title="070501sa01_f1" width="500" height="337" class="alignnone size-full wp-image-111" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://thomaskoeppen.com/2007/05/19/pitching-agile-to-top-management/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Which Agile Process Is Right For Me?</title>
		<link>http://thomaskoeppen.com/2007/05/19/which-agile-process-is-right-for-me/</link>
		<comments>http://thomaskoeppen.com/2007/05/19/which-agile-process-is-right-for-me/#comments</comments>
		<pubDate>Sat, 19 May 2007 10:13:46 +0000</pubDate>
		<dc:creator>thomas</dc:creator>
				<category><![CDATA[business]]></category>
		<category><![CDATA[agile]]></category>

		<guid isPermaLink="false">http://blog.thomaskoeppen.com/pages/viewpage.action?pageId=3833876</guid>
		<description><![CDATA[There are many different processes that fit under the Agile umbrella and almost every company implements them differently. The idealistic phase is over, and teams are quite practical in the ways in which they adopt and adapt Agile processes. But many are overwhelmed by the tasks of selecting specific practices, fitting them with legacy processes, [...]]]></description>
			<content:encoded><![CDATA[<p>There are many different processes that fit under the Agile umbrella and almost every company implements them differently. The idealistic phase is over, and teams are quite practical in the ways in which they adopt and adapt Agile processes. But many are overwhelmed by the tasks of selecting specific practices, fitting them with legacy processes, and finding the right tools to support their efforts.<br/><br />
<a href="http://www.jroller.com/page/gursesl" rel="nofollow">Levent Gurses</a> stresses the importance of evaluating Agile methods and practices according to their contribution to business value.</p>
<ul>
<li><a href="http://www.drdobbs.com/dept/architect/193402902" rel="nofollow">Levent&#8217;s 10 Mistakes in Transitioning to Agile (10/2006) </a></li>
</ul>
<p>To implement Agile processes and minimize business disruption, <a href="http://agilemanager.blogspot.com/" rel="nofollow">Ross Pettit</a> (<a href="http://www.thoughtworks.co.uk" rel="nofollow">thoughtworks</a>) advocates that IT organizations focus on three primary goals: achieving &#8220;completion integrity,&#8221; providing meaningful transparency, and removing underlying organizational constraints.</p>
<p>Shaping an Agile process that delivers value is not a selection of prescriptive actions.  It is a conscious effort to fit and mature best practices in an environment.  Three core questions guide this process:</p>
<ul>
<li>What will provide sufficient completion integrity for the work we do?</li>
<li>What will create meaningful transparency of the work being done?</li>
<li>What are the underlying organizational constraints that will impede changes in the way work is done?</li>
</ul>
<ul>
<li><a href="http://www.agilejournal.com/content/view/278/76/" rel="nofollow">Ross Pettit&#8217;s Key Success Factors in Top-Down Agile Adoption (03/2007) </a></li>
<li><a href="http://www.agilejournal.com/content/view/66/53/" rel="nofollow">Ross Pettit&#8217;s Enabling Global Business Success (07/2006) </a></li>
</ul>
<hr />
<p>And now the best news:</p>
<p>Thanks to <a href="http://www.sprint-it.de/" rel="nofollow">Boris Gloger</a> who held the Scrum Master Training in <a href="http://www.namics.com/news-medien/daten-events/scrum-training.html" rel="nofollow">Zurich, May 2007 </a>.<br/><br />
It were 2 wonderful days learning new thoughts on Scrum.<br/><br />
So i am prepared for my future without traditional project management methods.</p>
<p>I am now a Certified Scrum Master.</p>
]]></content:encoded>
			<wfw:commentRss>http://thomaskoeppen.com/2007/05/19/which-agile-process-is-right-for-me/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Change Prozesse</title>
		<link>http://thomaskoeppen.com/2007/05/12/change-prozesse/</link>
		<comments>http://thomaskoeppen.com/2007/05/12/change-prozesse/#comments</comments>
		<pubDate>Sat, 12 May 2007 11:56:30 +0000</pubDate>
		<dc:creator>thomas</dc:creator>
				<category><![CDATA[business]]></category>
		<category><![CDATA[management]]></category>

		<guid isPermaLink="false">http://blog.thomaskoeppen.com/display/blog/2007/05/12/Change+Prozesse</guid>
		<description><![CDATA[Nichts ist so bestÃ¤ndig wie der Wandel. VerÃ¤nderungen sind zum permanenten Begleiter im Wirtschaftsleben geworden: Strategiewechsel, Restrukturierungen, UnternehmenszusammenschlÃ¼sse und externe EinflÃ¼sse verlangen von Unternehmen, sich zu verÃ¤ndern &#8211; und von Mitarbeitern ebenfalls. Der Sozialwissenschaftler Lewin teilt einen erfolgreichen VerÃ¤nderungsprozess in 3 Phasen ein: PHASE 1: Auftauen (unfreeze): Zu Beginn eines jeden VerÃ¤nderungsprozesses mÃ¼ssen WiderstÃ¤nde gegen [...]]]></description>
			<content:encoded><![CDATA[<p>Nichts ist so bestÃ¤ndig wie der Wandel. VerÃ¤nderungen sind zum permanenten Begleiter im Wirtschaftsleben geworden: Strategiewechsel, Restrukturierungen, UnternehmenszusammenschlÃ¼sse und externe EinflÃ¼sse verlangen von Unternehmen, sich zu verÃ¤ndern &#8211; und von Mitarbeitern ebenfalls. Der Sozialwissenschaftler Lewin teilt einen erfolgreichen VerÃ¤nderungsprozess in 3 Phasen ein:</p>
<p>PHASE 1: Auftauen (unfreeze):<br/><br />
Zu Beginn eines jeden VerÃ¤nderungsprozesses mÃ¼ssen WiderstÃ¤nde gegen die VerÃ¤nderung abgebaut werden.</p>
<p>PHASE 2: Bewegung (move):<br/><br />
In Phase 2 kommt der Change-Prozess in Bewegung. Es geht darum, die VerÃ¤nderungen umzusetzen.</p>
<p>PHASE 3: Einfrieren (freeze):<br/><br />
In dieser Phase geht es darum, Kurs zu halten. Ziel der 3. Phase ist daher, das neue Verhalten zu stabilisieren.</p>
<p>ÃœberprÃ¼fen Sie anhand der folgenden Checkliste, ob Sie an alles gedacht haben:</p>
<p>PHASE 1: Auftauen<br/><br />
Kernaufgaben:</p>
<ul>
<li>Diagnose stellen: Warum muss Ihr Unternehmen sich verÃ¤ndern?</li>
<li>Vision entwickeln</li>
<li>Managementteam ins Boot holen</li>
</ul>
<p>PHASE 2: Bewegung<br/><br />
Kernaufgaben:</p>
<ul>
<li>Ziele ableiten</li>
<li>Vision, Ziele und Strategien kommunizieren</li>
<li>MaÃŸnahmen entwickeln</li>
<li>Verantwortlichkeiten regeln</li>
<li>Mitarbeiter qualifizieren</li>
<li>PersÃ¶nliche Positionierung im Changeprozess erarbeiten</li>
<li>VerÃ¤nderungsschritte steuern, kontrollieren und dokumentieren</li>
</ul>
<p>PHASE 3: Einfrieren<br/><br />
Kernaufgaben:</p>
<ul>
<li>Ergebnisse reflektieren</li>
<li>Stand der VerÃ¤nderung festhalten</li>
<li>Kontinuierliche Verbesserung verankern</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://thomaskoeppen.com/2007/05/12/change-prozesse/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
