Comments on: What the heck does Agile mean anyway? http://pliantalliance.org/2007/08/17/what-the-heck-does-agile-mean-anyway/ Think. Evaluate. Change. Fri, 21 Nov 2008 16:39:57 +0000 http://wordpress.org/?v=2.5.1 By: Michael Bolton http://pliantalliance.org/2007/08/17/what-the-heck-does-agile-mean-anyway/#comment-785 Michael Bolton Fri, 28 Sep 2007 21:52:09 +0000 http://pliantalliance.org/main/what-the-heck-does-agile-mean-anyway/#comment-785 I don't think it's worth worrying about if you apply The Thesaurus Heuristic: assume that people mean different things by the same words, and the same things by different words. "I may have worked on an Agile project, but perhaps not by that name." THEY think they mean something by "Agile", so the quickest way around the problem is to note that you'd like to avoid misunderstanding, and to ask what they mean by it. I don’t think it’s worth worrying about if you apply The Thesaurus Heuristic: assume that people mean different things by the same words, and the same things by different words. “I may have worked on an Agile project, but perhaps not by that name.” THEY think they mean something by “Agile”, so the quickest way around the problem is to note that you’d like to avoid misunderstanding, and to ask what they mean by it.

]]> By: Gabriel C http://pliantalliance.org/2007/08/17/what-the-heck-does-agile-mean-anyway/#comment-773 Gabriel C Mon, 20 Aug 2007 20:19:16 +0000 http://pliantalliance.org/main/what-the-heck-does-agile-mean-anyway/#comment-773 It always though it was ironic that the most popular Agile process (XP) is a brittle, hard to change, all-or-nothing process. There's usually little room to adapt the process to your context. For doing a minimal design, you need constant refactoring, for doing constant refactoring, you need extensive unit tests. As the documentation is the code, and to ensure the quality of the unit tests, you need to pair program always... (you get the idea... <a href=http://www.softwarereality.com/lifecycle/xp/safety_net.jsp rel="nofollow">A Self-Referential Safety Net</a>) It's very hard to change any practice without affecting adversely the others... that doesn't sound much agile... <b>Note:</b> Edited to fix the link - tbeck It always though it was ironic that the most popular Agile process (XP) is a brittle, hard to change, all-or-nothing process. There’s usually little room to adapt the process to your context.
For doing a minimal design, you need constant refactoring, for doing constant refactoring, you need extensive unit tests. As the documentation is the code, and to ensure the quality of the unit tests, you need to pair program always…
(you get the idea… A Self-Referential Safety Net)
It’s very hard to change any practice without affecting adversely the others… that doesn’t sound much agile…

Note: Edited to fix the link - tbeck

]]> By: Jonathan Kohl http://pliantalliance.org/2007/08/17/what-the-heck-does-agile-mean-anyway/#comment-770 Jonathan Kohl Sat, 18 Aug 2007 00:09:23 +0000 http://pliantalliance.org/main/what-the-heck-does-agile-mean-anyway/#comment-770 Isn't it just a clever marketing term to line the pockets of consultants, tool vendors and third-rate authors? ;) Isn’t it just a clever marketing term to line the pockets of consultants, tool vendors and third-rate authors? ;)

]]>