tag:blogger.com,1999:blog-10280668.post114698521169532453..comments2023-09-22T06:05:17.495-05:00Comments on Brad Appleton's ACME Blog: Nutshell definitions of Agile developmentBrad Appletonhttp://www.blogger.com/profile/15136106921504315995noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-10280668.post-74774350522238576592007-03-20T18:54:00.000-05:002007-03-20T18:54:00.000-05:00Rediculous. Reminds me of how I wrote web applica...Rediculous. Reminds me of how I wrote web applications (and responded to new requirements) in 1997. <BR/><BR/>Someone would make a valid comment on the feedback form which cc'd to webmaster@....com, and the next day, I'd make the change in dev, unit test, and update prod.<BR/><BR/>Granted, things aren't the same now that I work at a global financial institution, but still seems petty considering how we used to react back in the boom years...<BR/><BR/>Sending hundreds of people to training, to learn a "methodology" for rapid-response releases...<BR/><BR/>Yeah yeah, i know... Millions of dollars are at stake now, not just a potential IPO price. Sigh... still seems like two steps backwards... considering all we spent training folks on Six Sigma and DMAIC. <BR/><BR/>I long for the days when I could make a needed UI improvement directly to prod, based on a single email to feedback@...com, without asking for anyones permission! :PMartyhttps://www.blogger.com/profile/14777483678013218629noreply@blogger.comtag:blogger.com,1999:blog-10280668.post-1148167252440857682006-05-20T18:20:00.000-05:002006-05-20T18:20:00.000-05:00I like your defintion Scott. My only complaint wo...I like your defintion Scott. My only complaint would be that it's quite long, for a "soundbite".<BR/><BR/>I had a go at making a shorter soundbite, here http://www.agilekiwi.com/definition.htm<BR/><BR/>To me, there are two important aspects to any definiton:<BR/><BR/>1. It must encompass those of use who, as Alistair Cockburn puts it, "Came to agility through the door marked 'efficiency' [of process] not the door marked 'changing requirements'". (Both are about minimising total cost over the whole lifecycle - both development and maintenance - so there's plenty of common ground).<BR/><BR/>2. Be about _agile_ in the broadest, sense, not specifically XP. For that reason, I specifically disagree with the kind of definition given by Tim Haughton, above. (Click my signature for the reasons why).<BR/><BR/>By the way, we had an interesting discision of this topic on the Cystal Clear newsgroup some months ago.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-10280668.post-1148006212495852602006-05-18T21:36:00.000-05:002006-05-18T21:36:00.000-05:00My definition is:Agile is an iterative and increme...My definition is:<BR/>Agile is an iterative and incremental (evolutionary) approach to software development <BR/>which is performed in a highly collaborative manner with "just enough" ceremony <BR/>that produces high quality software which meets the changing needs of its stakeholders.Scott W, Amblerhttps://www.blogger.com/profile/07416328932753598174noreply@blogger.comtag:blogger.com,1999:blog-10280668.post-1147274209360400312006-05-10T10:16:00.000-05:002006-05-10T10:16:00.000-05:00I also liked Tim Haughton's take:--------------Whe...I also liked Tim Haughton's take:<BR/>--------------<BR/>When clients ask me what 'Agile' development is, I tell them it is any<BR/>development method that revolves around 4 key pillars. In today's<BR/>lingo, we might refer to them as "The Axes of Agility", namely;<BR/><BR/>- Short iterations, circa 2 weeks.<BR/>- Automated accetance tests.<BR/>- A 'war room' style programming environment.<BR/>- Test Driven Development.<BR/><BR/>If you have these things in place, other agile practices will almost<BR/>inevitably follow.<BR/>---------------Anonymousnoreply@blogger.com