Skip to main content
SpringerLink
Log in

Agile Development: Good Process or Bad Attitude?

  • Conference paper
  • First Online:
Product Focused Software Process Improvement (PROFES 2002)

Part of the book series: Lecture Notes in Computer Science ((LNCS,volume 2559))

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.

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

Access this chapter

Log in via an institution
Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 84.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 109.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. Paulk, M., Extreme Programming from a CMM Perspective. IEEE Software, 2001.

    Google Scholar 

  2. Rakitin, S., Manifesto Elicits Cynicism. Computer, 2001(December): p. 4.

    Google Scholar 

  3. Boehm, B.W., Get Ready for Agile Methods, with Care. IEEE Computer, 2002.

    Google Scholar 

  4. Glass, R. L., Agile versus Traditional: Make Love not War. Cutter IT Journal, 2001. Vol. 14, No. 12(December): p. 12–18.

    Google Scholar 

  5. 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.

    Google Scholar 

  6. Crosby, P. B., Quality is Free: The Art of Making Quality Certain. 1979, New York, NY: MacGraw-Hill.

    Google Scholar 

  7. Deming, W. E., Out of Crisis. 1986, Cambridge, MA: MIT Center for Advanced Engineering.

    Google Scholar 

  8. Juran, J. M., Juran on Planning for Quality. 1988, New York, NY: MacMillan.

    Google Scholar 

  9. 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.

    Google Scholar 

  10. 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.

    Google Scholar 

  11. Beck, K., Extreme Programming Explained. 1999, Boston: Addison-Wesley.

    Google Scholar 

  12. Schwaber, K. and M. Beedle, Agile Software Development with Scrum. 2002, Upper Saddle River, N. J.: Prentice Hall.

    Google Scholar 

  13. Cockburn, A., Agile Software Development. 2002, Boston: Addison-Wesley.

    Google Scholar 

  14. Agile Alliance, Manifesto for Agile Software Development. 2001.

    Google Scholar 

  15. Cockburn, A., Agile Software Development Joins the “Would-be Crowd,”. Cutter IT Journal, 2002. 15(1): p. 6–12.

    MathSciNet  Google Scholar 

  16. Highsmith, J., Agile Software Development Ecosystems. 2002, Boston: Addison-Wesley.

    Google Scholar 

  17. Humphrey, W. S., Introduction to the Personal Software ProcessSM. 1997, Boston: Addison-Wesley.

    Google Scholar 

  18. Humphrey, W. S., Introduction to the Team Software ProcessSM. 2000, Boston: Addison-Wesley.

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. The George Washington University, 20052, DC, Washington

    Richard Turner

Authors
  1. Richard Turner
    View author publications

    You can also search for this author in PubMed Google Scholar

Editor information

Editors and Affiliations

  1. Department of Information Processing Science, University of Oulu, P.O. Box 3000, 90014, Oulun yliopisto, Finland

    Markku Oivo

  2. VTT Electronics, VTT Technical Research Centre of Finland, P.O. Box 1100, 90571, Oulu, Finland

    Seija Komi-Sirviö

Rights and permissions

Reprints 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

Publish with us

Policies and ethics

Search

Navigation