📄 extrememanagement.html
字号:
<head><title>Extreme Management</title></head><body><h1><img src="logo.gif"> Extreme Management</h1>An idea we're kicking around at my new employ. Think of the traditional XP management division between coach and tracker. They're kind of a pair, right? So let's make 'em a real pair and enlarge the roles a little. Tracker also focuses outwards, operating on the organization to obtain resources and agreements for the group, as per a typical project manager. Coach focuses inwards and also does what a typical <a href="http://c2.com/cgi/wiki?ChiefArchitect">ChiefArchitect</a> does.
<p>These roles are peers; the group is responsible to the pair. So then we can take that pair and make them an element in a larger group, led by a larger pair. This structure continues up to the top, which is a CEO/CTO pair.
<p><strong>Advantages:</strong>
<p><UL><li> most elements of XP can be used throughout the entire organization.
<li> Because a pair can manage twice as many members as an individual, the overall number of levels in the hierarchy is reduced by a very large factor. <strong>A company of 10,000 could work with just 4 levels of management. 3 if you don't count CEO/CTO.</strong>
<li> If one of the managing pair gets knocked out temporarily, by a vacation say, or permanently, through a reshuffle, we're not practicing <em><a href="http://c2.com/cgi/wiki?ProjectOwnership">ProjectOwnership</a></em>, so it's easy to bring a replacement up from the group, down from the coach member of the upper pair, or coming in sidewise from elsewhere.
<li> The pairing mitigates <a href="http://c2.com/cgi/wiki?ChineseWhispers">ChineseWhispers</a>.
<li> Pairing is a really fun and enjoyable way to solve problems; managers will get less stressed and be kinder to everyone.
<li> <a href="http://c2.com/cgi/wiki?ProjectVelocity">ProjectVelocity</a>, however you manage that (yes, I still like <a href="http://c2.com/cgi/wiki?IdealDay">IdealDay</a><strong></strong>s, so there) can be communicated consistently throughout the organization. This is to say you don't have to worry about turning a <a href="http://c2.com/cgi/wiki?CommitmentSchedule">CommitmentSchedule</a> into one of those ridiculous MS-Project graphs to please <a href="http://c2.com/cgi/wiki?CaptainHornHair">CaptainHornHair</a>.
<li> Pairing with senior and junior members of the group is a good way to groom staff for promotion as the organization expands.
<li> When two groups need to cooperate, the leading pairs make a nice sized steering committee.
<li> This goes for QA. So QA can have exactly the same structure as development; a QA team is paired with a development team and uses all the XP practices to keep its development of <a href="FunctionalTests.html">FunctionalTests</a> on track, answering <a href="http://c2.com/cgi/wiki?ExtremeProgrammingChallengeTwentyTwo">ExtremeProgrammingChallengeTwentyTwo</a>.
<li> This is probably the right way to ensure that <a href="ExtremeProgrammingMayScaleUp.html">ExtremeProgrammingMayScaleUp</a>.
<li> Others?
<p></UL><strong>Disadvantages:</strong>
<p><UL><li> I thought a "permanent pair" interfered with the spirit of <a href="PairProgramming.html">PairProgramming</a>, which was that pairs always reform.
<UL><li> I figure a ManagementPair<a href="http://c2.com/cgi/wiki?edit=ManagementPair">?</a> is permanent for an iteration - an iteration is their analogue of an <a href="http://c2.com/cgi/wiki?EngineeringTask">EngineeringTask</a>. I imagine but don't know whether a ManagementPair<a href="http://c2.com/cgi/wiki?edit=ManagementPair">?</a> would stay permanent for longer than that.
<p></UL></UL><strong>Questions:</strong>
<p><UL><li> The mappings and metaphors for all the various XP practices aren't entirely clear yet. Stuff like <a href="http://c2.com/cgi/wiki?CommitmentSchedule">CommitmentSchedule</a>, <a href="http://c2.com/cgi/wiki?DoSimplestThing">DoSimplestThing</a>, <a href="http://c2.com/cgi/wiki?YaGni">YaGni</a>, and <a href="http://c2.com/cgi/wiki?DontGoDark">DontGoDark</a> are clear enough, but how about <a href="http://c2.com/cgi/wiki?CodeUnitTestFirst">CodeUnitTestFirst</a>?
<li> How often should <a href="http://c2.com/cgi/wiki?StandUpMeeting">StandUpMeeting</a><strong></strong>s be held when you get above a group of developers?
<p></UL>--<a href="http://c2.com/cgi/wiki?PeterMerel">PeterMerel</a>
<p><hr>
<p>XP is based on actual practices, used by actual practitioners, honed until they work.
<p><em>Well appreciated, though of course the combination of those practices was, until recently, unhoned. Still, so many of the practices are generic, you have to expect non-developers are going to try them out. I hear a lot of interest in this direction in the organizations I'm involved with. XM may not be a problem domain of interest to all, but it will be very interesting to some. Consider the above the start of ideas for a spike.</em>
<p>In <a href="http://c2.com/cgi/wiki?TomDeMarco">TomDeMarco</a>'s talk at <a href="http://c2.com/cgi/wiki?XpImmersionThree">XpImmersionThree</a>, he spoke of <a href="http://c2.com/cgi/wiki?ManagementTeam">ManagementTeam</a>'s and the fact that there aren't many. <a href="http://c2.com/cgi/wiki?LowellLindstrom">LowellLindstrom</a> suggested that such a thing might be <strong>just</strong> the way to scale XP up. I'll see about drawing a picture and posting it. --<a href="RonJeffries.html">RonJeffries</a>
<p>It is now posted at <a href="http://c2.com/cgi/wiki?TomsTalkAtXpImmersionThree">TomsTalkAtXpImmersionThree</a> -<a href="http://c2.com/cgi/wiki?LowellLindstrom">LowellLindstrom</a>
<p><em>That would be very much appreciated. Especially confusing is the role of QualityAssurance<a href="http://c2.com/cgi/wiki?edit=QualityAssurance">?</a>, though the more I think of it, the more I think QualityAssurance<a href="http://c2.com/cgi/wiki?edit=QualityAssurance">?</a>'s role isn't especially well defined in regular XP either. I've seen, at <a href="http://c2.com/cgi/wiki?WebSense">WebSense</a>, a situation where QualityAssurance<a href="http://c2.com/cgi/wiki?edit=QualityAssurance">?</a> lagged development badly, and all kinds of non-extreme measures were tried in order to make up the lag. But perhaps this question needs to be another <a href="ExtremeProgrammingChallenge.html">ExtremeProgrammingChallenge</a>: <a href="http://c2.com/cgi/wiki?ExtremeProgrammingChallengeTwentyTwo">ExtremeProgrammingChallengeTwentyTwo</a>.</em> --PM
<p>XP is based on practices applied at more than one team. If a single team adapts by-rules that appear to work, credit could be due the by-rules or the participants, and we'll have no way to tell which. The same by-rule at a different site could fail, due simply to different personality dynamics. We have fewer management environments to experiment with, so the margin of error in these experiments will be higher.
<p><em>Hmm. So what you're suggesting is we take these ideas one at a time and see how well they work as little spikes rather than one big one. Good idea.</em>
<p><hr>
<p>Most new ideas seem to have an essence, or kernel.<hr><a href="http://c2.com/cgi/wiki?edit=ExtremeManagement">EditText</a> of this page (last edited July 11, 2000)<br><a href="http://c2.com/cgi/wiki?FindPage&value=ExtremeManagement">FindPage</a> by browsing or searching<p><font color=gray size=-1>This page mirrored in <a href="index.html">ExtremeProgrammingRoadmap</a> as of March 31, 2001</font></body>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -