Agile methods and CMMI: compatibility or conflict?

• Autorzy: Fritzsche M. , Keil P.
• Języki publikacji: EN

Abstrakty

EN

During the last years, agile methods like eXtreme Programming have become increasingly popular. Parallel to this, more and more organizations rely on process maturity models to assess and improve their own processes or those of suppliers, since it has been getting clear that most project failures can be imputed to inconsistent, undisciplined processes. Many organizations demand CMMI compliance of projects where agile methods are employed. In this situation it is necessary to analyze the interrelations and mutual restrictions between agile methods and approaches for software process analysis and improvement. This paper analyzes to what extent the CMMI process areas can be covered by XP and where adjustments of XP have to be made. Based on this, we describe the limitations of CMMI in an agile environment and show that level 4 or 5 are not feasible under the current specifications of CMMI and XP.

Słowa kluczowe

EN

agile method; CMMI requirement; Capability Maturity Model Integration (CMMI)

• Wydawca: Oficyna Wydawnicza Politechniki Wrocławskiej
• Czasopismo: e-Informatica Software Engineering Journal
• Rocznik: 2007
• Tom: Vol. 1, nr 1
• Strony: 9--26
• Opis fizyczny: Bibliogr. 29 poz.

Twórcy

autor

Fritzsche M.

autor

Keil P.

• Technische Universitat Munchen

Bibliografia

• [1] V-Modell XT Portal. http://www.v-modell-xt.de.
• [2] D. J. Anderson. Stretching Agile to fit CMMI Level 3 - the story of creating MSF for CMMI Process Improvement at Microsoft Corporation. In AGILE, pages 193–201, 2005.
• [3] K. Beck and C. Andres. Extreme Programming Explained: Embrace Change. Addison-Wesley,2nd edition, 2004.
• [4] K. Beck, M. Beedle, A. van Bennekum, A. Cockburn, W. Cunningham, M. Fowler, J. Grenning,J. Highsmith, A. Hunt, R. Jeffries, J. Kern, B. Marick, R. C. Martin, S. Mellor,K. Schwaber, J. Sutherland, and D. Thomas. Manifesto for Agile Software Development,accessed in 2006. http://AgileManifesto.org/.
• [5] A. Cockburn. Agile Software Development. Addison-Wesley, 2002.
• [6] A. Cockburn and J. Highsmith. Agile Software Development: The People Factor. IEEE Computer, 34(11):131–133, 2001.
• [7] D. Cohen, M. Lindvall, and P. Costa. Agile Software Development: A DACS State-of-the-Art Report. Technical report, 2003. http://www.thedacs.com/techs/agile/agile.pdf.
• [8] M. Doernhoefer. Surfing the net for software engineering notes. SIGSOFT Softw. Eng. Notes,31(1):5–13, 2006.
• [9] C. Dogs and T. Klimmer. Agile Software-Entwicklung kompakt. mitp-Verlag, 2005.
• [10] M. Fowler. Using an Agile Software Process with Offshore Development, accessed in 2005.http://www.martinfowler.com/articles/agileOffshore.html.
• [11] M. Fritzsche. Agile Methoden im industriellen Umfeld. Master’s thesis, Technische Universit¨at M¨unchen, 2005.
• [12] H. Glazer. Dispelling the Process Myth: Having a Process Does Not Mean Sacrificing Agility or Creativity. CrossTalk: The Journal on Defense Software Engineering, (14):27–30, 2001.
• [13] J. D. Herbsleb, D. Zubrow, D. Goldenson, W. Hayes, and M. C. Paulk. Software Quality and the Capability Maturity Model. Commun. ACM, 40(6):30–40, 1997.
• [14] J. Highsmith. Extreme Programming: Agile Project Management Advisory Service White Paper, accessed in 2005. http://www.cutter.com/freestuff/ead0002.pdf.26 Martin Fritzsche, Patrick Keil
• [15] S. E. Institute. Capability Maturity Model Integration (CMMI), Version 1.1 (CMMISE/SW/IPPD/SS, V1.1). Technical report, Software Engineering Institute, Carnegie Mellon University, 2002.
• [16] J. J. Jiang, G. Klein, H.-G. Hwang, J. Huang, and S.-Y. Hung. An exploration of the relationship between software development process maturity and project performance. Inf. Manage.,41(3):279–288, 2004.
• [17] T. K¨ahk¨onen and P. Abrahamsson. Achieving CMMI Level 2 with Enhanced Extreme Programming Approach. In PROFES, pages 378–392, 2004.
• [18] D. Kane and S. Ornburn. Agile Development: Weed or Wildflower? CrossTalk: The Journal on Defense Software Engineering, 2002.
• [19] P. Keil. Principal agent theory and its application to analyze outsourcing of software development.In EDSER ’05: Proceedings of the seventh international workshop on Economics-driven software engineering research, pages 1–5, New York, NY, USA, 2005. ACM Press.
• [20] M. C. Paulk. Using the Software CMM With Good Judgment. ASQ Software Quality Professional,1(3), 1999.
• [21] M. C. Paulk. Extreme Programming from a CMM Perspective. IEEE Software, 18(6):19–26,2001.
• [22] M. C. Paulk, B. Curtis, M. B. Chrissis, and C. V. Weber. Capability Maturity Model, Version 1.1. IEEE Softw., 10(4):18–27, 1993.
• [23] M. Poppendieck and T. Poppendieck. Lean Software Development: An Agile Toolkit. Addison-Wesley Longman Publishing Co., Inc., Boston, MA, USA, 2003.
• [24] R. S. Sangwan and S. P. Masticola. Model-Driven Rapid Application Development: A Framework for Agile Development in Outsourced Environments. Technical report, Siemens Corporate Research, 2004.
• [25] K. Schwaber and M. Beedle. Agile Software Development with Scrum. Prentice Hall PTR,Upper Saddle River, NJ, USA, 2001.
• [26] M. Simons. Internationally Agile, accessed in 2005. http://www.informit.com/articles/article.asp?p=25929.
• [27] R. Turner. Agile Development: Good Process or Bad Attitude? In PROFES, pages 134–144,2002.
• [28] R. Turner and A. Jain. Agile Meets CMMI: Culture Clash or Common Cause? In XP/Agile Universe, pages 153–165, 2002.
• [29] R. van Solingen. Measuring the ROI of Software Process Improvement. IEEE Software,21(3):32–38, 2004.