Skip to main content

Agile Maturity Model: Oxymoron or the Next Level of Understanding

  • Conference paper
Software Process Improvement and Capability Determination (SPICE 2012)

Abstract

From the agile camp you can hear someone to say that CMMI is the big American waterfall model monster, and is outright contra productive to agile methods. From the CMMI camp you can hear someone to say that agile methods is hackers from hell that uses the agile paradigm to enjoy anarchy with no rules. You can also hear some say that agile works the best in CMMI level 5 companies. The context of the dilemma however is slightly awkward. CMMI describes characteristics of good development practices, and agile is a lifecycle concept. So from a meta point of view they can easily co-exist. We would like to state that they do, and that you need both to support the best development performance. Starting in December 2011 three surveys were launched to get an idea about what could an agile maturity model deliver and what might be its added value. 67 Participants from several agile or/and CMMI® related LinkedIn Groups contributed to the survey. This article explains the survey results and proposes further research topics and harmonization actions.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. CMMI Product Team. CMMI for development, version 1.3. Software Engineering Institute, CMU/SEI- TR-2010- 033, Pittsburgh, PA, USA (2010)

    Google Scholar 

  2. Ambler, S.: The Agile Maturity Model (AMM) (web publishing), http://drdobbs.com/architecture-and-design/224201005

  3. Anderson, D.J.: Agile Management for Software Engineering, Applying the theory of constraints for business results. Prentice Hall (2004) (web publishing)

    Google Scholar 

  4. Banerjee, U.: Agile Maturity Model – Three Different Approaches (web publishing)

    Google Scholar 

  5. Benefield, R.: Seven Dimensions of Agile Maturity in the Global Enterprise: A Case Study. In: Proceedings of the 43rd Hawaii International Conference on System Sciences – 2010 (2010) (web publishing)

    Google Scholar 

  6. Humble, J., Russell, R.: The Agile Maturity Model Applied to Building and Releasing Software. ThoughtWorks White Paper (web publishing)

    Google Scholar 

  7. Jayaraj, S.: The Agile Maturity Model (web Publishing)

    Google Scholar 

  8. Kuvaja, P., Simila, J., Krzanik, L., Bicego, A., Saukkonen, S., Koch, G.: Software Process Assessment & Improvement, The BOOTSTRAP Approach. Blackwell, Oxford (1994)

    Google Scholar 

  9. Patel, C., Ramachandran, M.: Agile Maturity Model (AMM): A Software Process Improvement framework for Agile Software Development Practices. Int. J. of Software Engineering, IJSE 2(1), 3–28 (2009)

    Google Scholar 

  10. Proulx, M.: Yet Another Agile Maturity Model (AMM) – The 5 Levels of Maturity (web publishing)

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2012 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Schweigert, T., Nevalainen, R., Vohwinkel, D., Korsaa, M., Biro, M. (2012). Agile Maturity Model: Oxymoron or the Next Level of Understanding. In: Mas, A., Mesquida, A., Rout, T., O’Connor, R.V., Dorling, A. (eds) Software Process Improvement and Capability Determination. SPICE 2012. Communications in Computer and Information Science, vol 290. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-30439-2_34

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-30439-2_34

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-642-30438-5

  • Online ISBN: 978-3-642-30439-2

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics