Agile Programming and the CMM: Anti-Matter and Matter or Reconcilable Differences?
Software Technology Conference,
May 1, 2002
by David Kane and Steve OrnburnAbstract:
The Department of Defense and many other government agencies have made investments in
the Capability Maturity Model (CMM). Increasingly, it is common for CMM capability
to be required of bidders for RFP's. However, while the CMM has been a focal point
for process improvement for the past decade, there has been a surge in interest in
'lightweight' or 'agile' methodologies such as eXtreme Programming, Adaptive Programming,
SCRUM and Crystal. At first glance, these agile methodologies would appear to be at
odds with the goals and approaches of the CMM. Make no mistake -- there are major
differences. The CMM is often described as replacing the cowboy programmers archetype
with repeatable processes, while the Agile Manifesto specifically calls for an emphasis
of people over process. Ironically, if you examine many of these agile processes in
detail, you find most, if not all of the characteristics of a 'mature' software
development organization. How do we resolve this conflict? Is there a role for agile
methods in major government software development activities? | |
