Re: [AM] Let's call a spade a spade
[email protected] Sat, 27 Mar 2004 10:22:59 EST
| Newsgroups | gmane.comp.programming.modeling.agile |
|---|---|
| Message-ID | <[email protected]> |
-------------------------------1080400979 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Menthol Smokers Only! Click on the link below and=20 register to receive up to $50 in savings from one of=20 America's leading menthol brands.=20 http://click.topica.com/= caab4S3bUrKDAbWnbtka/ Lorillard =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D In a message dated 3/27/2004 5:57:07 AM Pacific Standard Time,=20 [email protected] writes: To my mind, there should be no shame in calling something "partially=20 Agile". To me, it indicates integrity and underlines the importance of=20 the values of the Manifesto.=20 I like to think that there is value in applying Agile practices, or even ju= st=20 an Agile "mindset" in projects being conducted in accordance with virtually= =20 any methodology. In fact, if history is any guide, agility of the sort we= =20 practice is likely to be spread through incremental use and acceptance, as = the=20 "unbelievers" become either Desperate or Daring enough to try it, even in a= n=20 abbreviated form. Also, as long as there are those who decry the agile appr= oach=20 because of its purported scalability issue, adoption of it will be slow. Pe= rhaps=20 the ultimate victory of the agile approach will be the incorporation of its= =20 principles in many other methodologies. IMHE, I've found that applying the= =20 spirit of the Agile Manifesto, if not the letter, yields substantial improv= ements=20 to any development methodology.=20 I have often described my clients as either desperate or daring. In virtual= ly=20 every case, the application of tradition development methods was not an=20 option; there was simply not enough time or other resources to use them. Su= ccess in=20 these projects, against what seemed like significant odds, impressed their= =20 sponsors and other participants enough to consider applying the agile appro= ach=20 in subsequent projects. I don't recall any of them doing so, however, "to t= he=20 letter". Nonetheless, IMHO, they're "on their way". In the playground of my= =20 mind, I see those whose attitudes and practices remain rooted in traditiona= l=20 software development methodologies being overrun from behind by the increas= ing=20 number of "Closet Agileers" who, for whatever reason, have elected to apply= the=20 principles of the Agile Manifesto to the extent possible in the projects in= =20 which they participate. If "building better software, faster" is the object= ive, I=20 can think of nothing better than legions of developers, practitioners of so= me=20 form of agile methodology or philosophy or other, throwing bricks at each= =20 other across the "methodological divides" proclaiming the superiority of th= eir=20 own particular brand of "agile" as the pinnacle of achievement. If we can't= =20 predict the future when building software, how can we presume to be any bet= ter at=20 it regarding the future of Agile? For my money, the future of Agile is=20 assured, simply "by virtue of its virtues". Agility as we know it was born = as a=20 solution to a chronic and intolerable problem: bad software due to bad proc= ess. If=20 there are problems with the current view of Agile (like the aforementioned= =20 scalability issue), it is likely that some agile practitioner(s) will event= ually=20 apply the agile philosophy to the problem and come up with an agile solutio= n.=20=20 IMHO, standing in he way of widespread adoption of agile principles is pure= =20 folly. Resistance to it is largely the result of the widespred and ingraine= d=20 conservatism of the vast majority of developers and the audiences they serv= e. It=20 is entirely conceiveable, from my perspective, that had our predecessors (I= 'm=20 talking pre-Agile, here) paid more attention to the growing number of=20 failing, out of control, chaotic development projects, and "stuck to their = knitting"=20 rather than embraced their imagined "Gods of the Enterprise" status, the= =20 current presidential race would be devoid of one of its "hot topics", softw= are=20 outsourcing. Does anyone really think that this practice was the result of= =20 anyone's notion that the software would be better by being produced off-sho= re? Think=20 of it this way: if there is a major likelihood that the software being=20 developed just might not do what it's intended to do when the time or money= runs out=20 (according to some estimates, a virtual certainty), then why not spend as= =20 little as possible on it's development? If the medical profession (another = hotbed=20 of professional conservatism) had the same record of achievement as softwar= e=20 developers, our health would largely be in the hands of shamans.=20 FMM, software developers and their beneficieries are standing on the=20 theshhold of a new reality in the way software is designed and built, a rea= lity in=20 which I believe "Agileers" will play a major role in its evolution. If I li= ve to=20 be a hundred, it will probably be due to my insatiable curiosity rgarding h= ow=20 all this turns out.=20 Agile forever. Regards, Pete =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Are you looking for savings on products you use everyday?=20 Visit Quality Health today and see the coupons, free=20 samples and special offers our members enjoy each and=20 everyday. http://click.topica.com/= caab3ozbUrKDAbWnbtkf/ Ivo Interactive =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D For more information about AM, visit the Agile Modeling Home Page at www.ag= ilemodeling.com --^---------------------------------------------------------------- This email was sent to: = [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrKDA.= bWnbtk.= Z2NtYS1h Or send an email to: [email protected] For Topica's complete suite of email marketing solutions visit: http://www.topica.com/?p=3DTEXFOOTER --^---------------------------------------------------------------- -------------------------------1080400979 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable <HTML><HEAD> <META charset=3DUS-ASCII http-equiv=3DContent-Type content=3D"text/html; ch= arset=3DUS-ASCII"> <META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD> <BODY style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; BACKGROUND-COLOR: #ffff= ff">= <PRE>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Menthol Smokers Only! Click on the link below and=20 register to receive up to $50 in savings from one of=20 America's leading menthol brands.=20 <A HREF=3D"http://click.topica.com/= caab4S3bUrKDAbWnbtkb/">http://click.topica.com/= caab4S3bUrKDAbWnbtkb/</A> Lorillard =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D </PRE> <DIV> <DIV>In a message dated 3/27/2004 5:57:07 AM Pacific Standard Time, deborah= @hartmann.net writes:</DIV> <BLOCKQUOTE style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue= 2px solid"><FONT face=3DArial>To my mind, there should be no shame in call= ing something "partially <BR>Agile". To me, it indicates integrity and unde= rlines the importance of <BR>the values of the Manifesto. </FONT></BLOCKQUO= TE></DIV> <DIV>I like to think that there is value in applying Agile practices, or ev= en just an Agile "mindset" in projects being conducted in accordance w= ith virtually any methodology. In fact, if history is any guide, agili= ty of the sort we practice is likely to be spread through incremental use a= nd acceptance, as the "unbelievers" become either Desperate or Daring&= nbsp;enough to try it, even in an abbreviated form. Also, as long as there = are those who decry the agile approach because of its purported scalability= issue, adoption of it will be slow. Perhaps the ultimate victory= of the agile approach will be the incorporation of its principles in = many other methodologies. IMHE, I've found that applying the spir= it of the Agile Manifesto, if not the letter, yields substantial impro= vements to any development methodology. </DIV> <DIV> </DIV> <DIV>I have often described my clients as either desperate or daring. = In virtually every case, the application of tradition development methods w= as not an option; there was simply not enough time or other resources to&nb= sp;use them. Success in these projects, against what seemed like signi= ficant odds, impressed their sponsors and other participants enou= gh to consider applying the agile approach in subsequent projects.&nbs= p;I don't recall any of them doing so, however, "to the letter". Nonetheles= s, IMHO, they're "on their way". In the playground of my mind, I see those = whose attitudes and practices remain rooted in traditional software develop= ment methodologies being overrun from behind by the increasing number of "C= loset Agileers" who, for whatever reason, have elected to apply t= he principles of the Agile Manifesto to the extent possible in th= e projects in which they participate. If "building better software, fa= ster" is the objective, I can think of nothing better than legions of devel= opers, practitioners of some form of agile methodology or philosophy or oth= er, throwing bricks at each other across the "methodological divides" procl= aiming the superiority of their own particular brand of "agile" as the= pinnacle of achievement. If we can't predict the future when building soft= ware, how can we presume to be any better at it regarding the future of Agi= le? For my money, the future of Agile is assured, simply "by virtue of= its virtues". Agility as we know it was born as a solution to a chronic&nb= sp;and intolerable problem: bad software due to bad process. If there = are problems with the current view of Agile (like the aforementioned scalab= ility issue), it is likely that some agile practitioner(s) will eventu= ally apply the agile philosophy to the problem and come up with an agi= le solution. </DIV> <DIV> </DIV> <DIV>IMHO, standing in he way of widespread adoption of agile principles is= pure folly. Resistance to it is largely the result of the widespred a= nd ingrained conservatism of the vast majority of developers and the a= udiences they serve. It is entirely conceiveable, from my perspective,= that had our predecessors (I'm talking pre-Agile, here) paid more attentio= n to the growing number of failing, out of control, chaotic development pro= jects, and "stuck to their knitting" rather than embraced their imagined "G= ods of the Enterprise" status, the current presidential race would be devoi= d of one of its "hot topics", software outsourcing. Does anyone really= think that this practice was the result of anyone's notion that the s= oftware would be better by being produced off-shore? Think of it this way: = if there is a major likelihood that the software being developed just might= not do what it's intended to do when the time or money runs out (acco= rding to some estimates, a virtual certainty), then why not spend as little= as possible on it's development? If the medical profession (another h= otbed of professional conservatism) had the same record of achievement = ;as software developers, our health would largely be in the hands of shaman= s. </DIV> <DIV> </DIV> <DIV>FMM, software developers and their beneficieries are standing on = the theshhold of a new reality in the way software is designed and built, a= reality in which I believe "Agileers" will play a major role in its e= volution. If I live to be a hundred, it will probably be due to my insatiab= le curiosity rgarding how all this turns out. </DIV> <DIV> </DIV> <DIV>Agile forever.</DIV> <DIV> </DIV> <DIV>Regards,</DIV> <DIV> </DIV> <DIV>Pete</DIV>= <PRE>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Are you looking for savings on products you use everyday?=20 Visit Quality Health today and see the coupons, free=20 samples and special offers our members enjoy each and=20 everyday. <A HREF=3D"http://click.topica.com/= caab3ozbUrKDAbWnbtkg/">http://click.topica.com/= caab3ozbUrKDAbWnbtkg/</A> Ivo Interactive =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D </PRE> <PRE>For more information about AM, visit the Agile Modeli= ng Home Page at www.agilemodeling.com</PRE> <PRE>--^^--------------------------------------------------------------- This email was sent to: = [email protected] EASY UNSUBSCRIBE click here: <A HREF=3D"http://topica.com/u/?bUrKDA.= bWnbtk.= Z2NtYS1h">http://topica.com/u/?bUrKDA.= bWnbtk.= Z2NtYS1h</A> Or send an email to: [email protected] For Topica's complete suite of email marketing solutions visit: <A HREF=3D"http://www.topica.com/?p=3DTEXFOOTER">http://www.topica.com/?p= =3DTEXFOOTER</A> --^^---------------------------------------------------------------</PRE> </BODY></HTML> -------------------------------1080400979--