Do Agile Methods Marginalize Problem Solvers? by
Victor Skowronski
Published in IEEE Computer, October 2004
This short professional article comments that a software development methodology should take advantage of programmers’ strengths and avoid their weaknesses. It argues, by reference to the working styles of Thomas Aquinas and Isaac Newton, that agile methods may do the opposite for certain working styles – that of problem solvers. The author questions whether agile methods provide the best environment for the best programmers, and indicates that a good problem solver who lacks people skills appears to be less competent in the eyes of agile methods proponents. "Competent in this context means that the programmer possesses real-world experience in the technology domain, has built similar systems in the past, and has good people and communication skills." The four phases of problem solving (Preparation, Incubation, Illumination, and Verification) are discussed in terms of the difficulties faced at each phase for a problem-solver in an agile environment. The paper makes a really interesting observation, argued by historical anecdote. It reads occasionally dismissive of agile without supporting argument, but it would still be interesting to see further work in this area.
Reviewed for the Agile Alliance
Comments