Abstract
Agile development methods are gaining adherents in a wide variety of industries. Agile proponents and those who support traditional process improvement have been equally vocal in their disdain for each other. However, it is unclear whether or not agile methods constitute an improvable „process.” This paper discusses the relationship between agile methods and process improvement goals and values and evaluates the components of the Capability Maturity Model IntegrationSM (CMMISM) Systems Engineering/Software Engineering/ Integrated Product and Process Model for their support of agile methods.
The following Carnegie Mellon University service marks and registered marks are used in this paper: Capability Maturity Model., CMM., CMM IntegrationSM, and CMMISM.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
Paulk, M., Extreme Programming from a CMM Perspective. IEEE Software, 2001.
Rakitin, S., Manifesto Elicits Cynicism. Computer, 2001(December): p. 4.
Boehm, B.W., Get Ready for Agile Methods, with Care. IEEE Computer, 2002.
Glass, R. L., Agile versus Traditional: Make Love not War. Cutter IT Journal, 2001. Vol. 14, No. 12(December): p. 12–18.
Turner, R. and A. Jain. Agile Meets CMMI: Culture Clash or Common Cause? in Extreme Programming and Agile Mathods-XP/Agile Universe 2002. 2002. Chicago, IL: Springer-Verlag.
Crosby, P. B., Quality is Free: The Art of Making Quality Certain. 1979, New York, NY: MacGraw-Hill.
Deming, W. E., Out of Crisis. 1986, Cambridge, MA: MIT Center for Advanced Engineering.
Juran, J. M., Juran on Planning for Quality. 1988, New York, NY: MacMillan.
Ahern, D. M., A. Clouse, and R. Turner, CMMI distilled: a practical introduction to integrated process improvement. The SEI series in software engineering. 2001, Boston: Addison-Wesley. xv, 306.
CMMI Development Team, CMMI-SE/SW/IPPD, V1.1: Capability Maturity Model Integrated for Systems Engineering, Software Engineering and Integrated Product and Process Development, Version 1.1: continuous representation.. 2001, Software Engineering Institute, Carnegie Mellon University: Pittsburgh, PA. p. 688.
Beck, K., Extreme Programming Explained. 1999, Boston: Addison-Wesley.
Schwaber, K. and M. Beedle, Agile Software Development with Scrum. 2002, Upper Saddle River, N. J.: Prentice Hall.
Cockburn, A., Agile Software Development. 2002, Boston: Addison-Wesley.
Agile Alliance, Manifesto for Agile Software Development. 2001.
Cockburn, A., Agile Software Development Joins the “Would-be Crowd,”. Cutter IT Journal, 2002. 15(1): p. 6–12.
Highsmith, J., Agile Software Development Ecosystems. 2002, Boston: Addison-Wesley.
Humphrey, W. S., Introduction to the Personal Software ProcessSM. 1997, Boston: Addison-Wesley.
Humphrey, W. S., Introduction to the Team Software ProcessSM. 2000, Boston: Addison-Wesley.
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2002 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Turner, R. (2002). Agile Development: Good Process or Bad Attitude?. In: Oivo, M., Komi-Sirviö, S. (eds) Product Focused Software Process Improvement. PROFES 2002. Lecture Notes in Computer Science, vol 2559. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-36209-6_13
Download citation
DOI: https://doi.org/10.1007/3-540-36209-6_13
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-00234-5
Online ISBN: 978-3-540-36209-8
eBook Packages: Springer Book Archive