logo
  • About
    • Management
    • World Wide Technology
  • Case Studies
  • Capabilities
    • Mobility
    • Software Development
    • Architecture and Integration
    • Agile Transformation and Training
    • UX and Design
    • Tactical Collaboration
  • News
    • Company Blog
  • Careers
  • Contact
Menu

Are Agile & CMMI Antithetical?

  • May 18, 2010
  • /
  • Comments Off on Are Agile & CMMI Antithetical?
  • /
  • Agile
Are agile and CMMI — Capability Maturity Model Integration — antithetical? Prior to embarking on our relationship with Hillel Glazer, our CMMI consultant, several of us thought exactly that: Agile and lean thinking means that we avoid unnecessary waste and overhead, while CMMI demands heavyweight approaches and documentation. Happily, we’ve learned that our preconceptions about CMMI were wrong and that it in fact can harmonize with agile, especially in our environment. CMMI is, simply, a framework for business-process improvement. It’s a software-management model for software projects to plan, organize and identify what needs to get done to run the project. It’s not an engineering-development standard, a process itself or a prescribed way of doing things. Since our teams have been doing regular retrospectives as an application of agile thinking for a while now, CMMI allows us to build on that foundation of process improvement that is already part of our thinking. So back to the question of whether agile thinking can co-exist with CMMI: of course, if we understand CMMI as a framework for improvement and delivering value to our customers, and if we understand agile to mean, among other things, satisfying our customers through early and continuous delivery of valuable software. In short, CMMI done well and agile done well work hand in glove. When you use CMMI to assess how well you plan (note: it’s not how *much* you plan), deliver requirements (not necessarily document them) and measure things that are important (not measure for measuring’s sake), you also see how effectively agile answers the questions that CMMI asks. And if you’re really applying agile approaches — focusing on working software (not merely avoiding documentation), responding responsibly to change (rather than simply not planning) and working hard to improve (rather than being satisfied), you see how CMMI enhances what you’re doing. Hillel wrote about how we were approaching the CMMI process using Agile techniques in his blog, and even made a video about our CMMI team room, check it out:
About the Author

This author has not added a biography. Meanwhile Matt Philip has contributed 8 posts. Click here to view them.

Recent Posts
  • An Interview with Kate Chadha, User Experience Practice Lead, WWT Asynchrony Labs St. Louis
  • An Interview with Kartik Patel, Office Lead, WWT Asynchrony Labs New York
  • Starting Your Tech Career? Consider WWT Asynchrony Labs in Springfield, Missouri
  • Re:Lax in Action
  • Make Risks Visible with “RAID bingo”
Recent Comments
  • Johan Brodin on Forecasting: Asking Why and Discovering What’s Behind the When (Part 3)
  • Bill on WWT Asynchrony Labs Participates in First-Ever “Longest Day Hack Alzheimer’s” Event
  • Liz Hall on WWT Asynchrony Labs Participates in First-Ever “Longest Day Hack Alzheimer’s” Event
  • Mayada H on Apache JMeter & Integrated Windows Authentication
  • Irudaya Raj on Using TLS with Self-Signed Certificates or Custom Root Certificates in iOS
Archives
  • March 2018
  • February 2018
  • January 2018
  • April 2017
  • March 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • August 2016
  • July 2016
  • February 2016
  • October 2015
  • September 2015
  • August 2015
  • June 2015
  • April 2015
  • March 2015
  • January 2015
  • December 2014
  • November 2014
  • October 2014
  • May 2014
  • April 2014
  • March 2014
  • January 2014
  • December 2013
  • November 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • September 2012
  • August 2012
  • July 2012
  • June 2012
  • April 2012
  • February 2012
  • November 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • March 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • September 2010
  • August 2010
  • July 2010
  • June 2010
  • May 2010
Categories
  • Agile
  • Asynchrony
  • Change
  • creativity
  • Design
  • Development
  • Enterprise Architecture
  • Hackathon
  • Healthcare
  • Quality Assurance
  • Uncategorized
  • Visual Thinking
async-logo-footer
info@asynchrony.com
314.678.2200
900 Spruce Street, Suite 700 St. Louis, MO 63102
Menu
  • About
    • Management
    • World Wide Technology
  • Case Studies
  • Capabilities
    • Mobility
    • Software Development
    • Architecture and Integration
    • Agile Transformation and Training
    • UX and Design
    • Tactical Collaboration
  • News
    • Company Blog
  • Careers
  • Contact