The insight I’m reaching is we have to understand what the job entails. Stay tuned on my next blog-entries because I’m going to address understanding the job. Your comment about using a methodology where it doesn’t fit is salient; I’m going to propose a definition of ‘fit’ that can help us select a methodology/approach to software projects that may help.

Using the correct tool allows you to focus your energy where it’s important. Software or otherwise, all of the successful projects I’ve been a part of had one thing in common–use the tools that will help you deliver, throw the rest away. Don’t use C++ for a task when a simple shell script will do. Don’t use a screwdriver as a chisel. Don’t blindly apply a software methodology to your project where it doesn’t fit.

Part of the problem with agile development methodologies is that they’re only very recently becoming popular, and as such we’re just figuring out what parts work and what parts get in the way in a given environment.