Peaceful Coexistence of Agile Development and CMMI
In the SEI paper “CMMI or Agile: Why Not Embrace Both“ a truce between Agile and CMMI is called for. The abstract of the document follows: “Agile development methods and CMMI (Capability Maturity Model® Integration) best practices are often perceived to be at odds with each other. This report clarifies why the discord need not exist and proposes that CMMI and Agile champions work toward deriving benefit from using both and exploit synergies that have the potential to dramatically improve business performance.”
The report discusses how early adopters of both Agile and CMMI are at the extremes of their paradigms. The report points out that Agile has its roots not in web development as many assume but in work from about 75 years ago and that it traces to Demmings “Plan-Do-Study-Act” paradigm.
The report points to several areas that have caused the chasm:
- Misuse
- Lack of Accurate Information
- Terminology Difficulties
The report refers to the Agile Manifesto and points out that Agile is misunderstood or misquoted by many as follows:
“The Agile Manifesto has been frequently cited by Agile proponents as justification for not having processes, for not documenting their work, and for not having plans. This interpretation gives justifiable cause to Agile detractors to accuse proponents of being “undisciplined lackeys.” Similarly, Agile detractors abuse the Agile Manifesto by using the same exact mechanism. By attributing a value of zero to the “things on the right,” detractors assume the worst of Agile proponents. However, these interpretations of the Agile Manifesto are incomplete and disingenuous.”
The report points out the general attributes of successful Agile projects:
- small teams consisting of approximately ten people
- an involved customer
- “rolling wave” or continual planning
- co-located and cross-functional teams
- organizations that are not in the habit of breaking up teams until each member is individually
competent at Agile
Agile is not successful when the following is true:
- lack of processes
- lack of discipline
- absent a role for plans or planning
This report is well worth the read. And it pretty much squelches the thought that Agile projects don’tneed estimates, plans or documentation (one I have heard from time to time from excited developers). SEER includes Agile Knowledge Bases as well as supporting CMMI so estimates of Agile systems and agile CMMI systems can easily be developed. Galorath’s David DeWitt did a good job of detailing these in his Agile briefing and webinar.
Thank you for reading “Dan on Estimating”, if you would like more information about Galorath’s estimation models, please visit our contact page or call us at +1 310 414-3222.
Related posts:
- Agile Development Mature Scrum Thanks to Tom Gilb for the article on a CMMI level 5 company that implemented Agile . I think the most interesting...
- Combining Agile and Traditional Development Gary Gack , software process consultant, did an interesting webinar and discussed the combining of Agile and traditional development approaches. ...
- Estimation & Agile Development… Plan and Control Agile Projects While at the IBM Rational user conference in Orlando I (Dan Galorath) attended a briefing by Scott Ambler, practice leader...
- Many Observed Incorrect Implementations of CMMI High Maturity At the CMMI conference a number of difficulties with high maturity, CMMI levels 4 & 5 quantified management. Some included...
- Agile Estimating User Stories There is an interesting article on estimating agile software with user story points agile estimating. While the intent of the article avoids...
Comments
Leave a Reply
Project Prediction Infographic
