<HTML><FONT FACE=arial,helvetica><HTML><FONT COLOR="#000000" FACE="Geneva" FAMILY="SANSSERIF" SIZE="2"><BR>
In a message dated 2/19/05 2:17:21 PM, hhowen@comcast.net writes:<BR>
<BR>
<BR>
<BLOCKQUOTE CITE STYLE="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px" TYPE="CITE"></FONT><FONT COLOR="#000000" FACE="Geneva" FAMILY="SANSSERIF" SIZE="2">He knows all about playing by the old rules which require a project plan,<BR>
budget, staffing levels, milestones, evaluation and testing procedure, and<BR>
all the rest. But, what about all this "self-organizing" stuff? How do you<BR>
play by the new rules? What are they? And last but not least - how do you<BR>
rationalize what you have done under the new rules so that it looks like the<BR>
"old rules" have been observed? This last part may seem sneaky and<BR>
dishonest, but my young manager friend really likes his job.<BR>
</BLOCKQUOTE></FONT><FONT COLOR="#000000" FACE="Geneva" FAMILY="SANSSERIF" SIZE="2"><BR>
Harrison,<BR>
<BR>
Well, I'm not sure this is probable (it may be slightly possible). As Kuhn writes, the user of a new paradigm hasn't got the proof that it is the way to go. Everything says otherwise. The risk takers are going on 'faith' in their instincts. Your young manager has more than that, he has deep world experience with OS to draw on. Maybe he can use it to get an "aha" about the programming process itself. <BR>
<BR>
But, about the self-organizing to </FONT><FONT COLOR="#000000" FACE="Geneva" FAMILY="SANSSERIF" SIZE="2"><I>write a new software program</I></FONT><FONT COLOR="#000000" FACE="Geneva" FAMILY="SANSSERIF" SIZE="2">, that seems really iffy. Software requires strategy, discipline and right code, not something that very easily emerges from no structure. Even Chaos, with it's structure of bounded instability, can't predict what the outcome will be or when it will emerge. Only that something will. Rather like the instructions for building an ant's nest.<BR>
<BR>
1. When an ant, carrying a stick, comes to another stick, the ant puts its stick down.<BR>
<BR>
2. When an ant, not carrying a stick, comes to a stick, it picks the stick up.<BR>
<BR>
Those two instructions will build an ant hill (mathematically, I'm told) but you can't tell where or when it will emerge, just that it will. I doubt this will be sufficient for the client. <BR>
<BR>
Maybe the two process should be separated. The 'chaos' of OS for breakthroughs, the discipline of code writing for getting something needed to emerge in a timely, semi-predictable manner to meet the needs of the client customer. <BR>
<BR>
Paul Everett</FONT><FONT COLOR="#000000" FACE="Geneva" FAMILY="SANSSERIF" SIZE="2"></FONT></HTML>
*
*
==========================================================
OSLIST@LISTSERV.BOISESTATE.EDU
------------------------------
To subscribe, unsubscribe, change your options,
view the archives of oslist@listserv.boisestate.edu:
http://listserv.boisestate.edu/archives/oslist.html
To learn about OpenSpaceEmailLists and OSLIST FAQs:
http://www.openspaceworld.org/oslist