Skip to main content

Using Agile Methods? – Expected Effects

  • Chapter
  • First Online:
Information Systems Development

Abstract

This chapter focuses on the movement from traditional to agile methods. What are the expected benefits of using agile methods instead of traditional ones? The chapter compares identified benefits in traditional and agile methods and takes a critical attitude in order to reveal possibilities and risks with the expressed benefits in agile methods. The chapter also tries to answer the questions of what benefits are lost and what benefits are preserved when moving to agile methods.

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 259.00
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 329.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 329.99
Price excludes VAT (USA)
  • Durable hardcover 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

References

  1. Abrahamsson, P., Salo, O., Ronkainen, J., and Warsta, J. (2002). Agile Software Development Methods.  VTT Electronic, Espoo. http://www.vtt.fi/inf/pdf/publications/2002/P478.pdf , site accessed Jan 26. 2008.

  2. Ambler, S. (2002). Agile Modeling: Effective Practices for Effective Programming. Wiley & Sons, Inc, New York.

    Google Scholar 

  3. AskOxford.com. (2008). http://www.askoxford.com/?view=uk. Site accessed Jan 15, 2008.

  4. Baskerville, R., Levine, L., Pries-Heje, J., Ramesh, B., & Slaughter, S. (2003). Is Internet-speed software development different? IEEE Software, 20(6), 70–77.

    Article  Google Scholar 

  5. Beck, K. (1999). Extreme Programming Explained: Embrace Change, Addison-Wesley, Reading, MA.

    Google Scholar 

  6. Beck, K., Beedle, M., van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M., Grenning, J., Highsmith, J., Hunt, A., Jeffries, R., Kern, J., Marick, B., Martin, R. C., Mellor, S., Schwaber, K. and Sutherland, J, Thomas, D. (2001). Manifesto for Agile Software Development. http://agilemanifesto.org/, Site accessed Jan 26, 2008.

  7. Boland, A. J. and Pondy, L. R. (1983). Accounting in organizations: a Union of natural and rational perspectives, Accounting, Organizations and Society, 8, 223–234.

    Article  Google Scholar 

  8. Bratteteig, T. and Stolterman, E. (1997). Design in groups – and all that jazz. In Kyng, M. and Mathiassen, L. (eds.), Computers and Design in Context, The MIT Press, Cambridge, MA.

    Google Scholar 

  9. Brinkkemper, S.,Motoshi, S. and Harmsen, F. (1998). Assembly techniques for method engineering. In Pernici, B. and Thanos, C. (eds.), Proceedings of the Tenth International Conference on Advanced Information Systems Engineering (CAiSE*98), Pisa, Italy.

    Google Scholar 

  10. Cambridge Dictionaries Online. (2008). http://dictionary.cambridge.org/. Site accessed Jan 15, 2008.

  11. Checkland, P. (1981). Systems Thinking, Systems Practice, Wiley, Chichester, UK.

    Google Scholar 

  12. Checkland, P. and Scholes, J. (1999). Soft Systems Methodology in Action, Wiley & Sons, Toronto.

    Google Scholar 

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

    Google Scholar 

  14. Croce, B. (1985). What is Living and What is Dead of the Philosophy of Hegel, University Press of America, Lanham, MD.

    Google Scholar 

  15. Cronholm, S. (1995). Why CASE Tools in Information Systems Development?, In Dahlbom, B., Kämmerer, F., Ljungberg, F., Stage, J. and Sörensen, C. (eds), Proceedings of the 18th Information Systems Research in Scandinavia (IRIS 18), Gjern, Denmark.

    Google Scholar 

  16. Cronholm, S. and Goldkuhl, G. (2005). Communication analysis as perspective and method for requirements engineering. In Maté, J. L. and Silva, A. (eds.), Requirements Engineering for Sociotechnical Systems, Idea Group Inc., Hershey, PA.

    Google Scholar 

  17. DSDM Consortium. (1997). Dynamic Systems Development Method, Version 3, DSDM Consortium, Ashford.

    Google Scholar 

  18. Ehn, P. (1989). Work-Oriented Design of Computer Artifacts, Lawrence Erlbaum, Hillsdale, NJ.

    Google Scholar 

  19. Goldkuhl, G. (2005). Socio-instrumental pragmatism: a theoretical synthesis for pragmatic conceptualisation in information systems. In Proceedings of the 3rd Intl Conf on Action in Language, Organisations and Information Systems (ALOIS), University of Limerick, Limerick.

    Google Scholar 

  20. Goldkuhl, G., Lind, M. and Seigerroth, U. (1998). Method integration: the need for a learning perspective. IEE Proceedings Software, 145(4): 113–118.

    Article  Google Scholar 

  21. Goldkuhl, G. and Lyytinen, K. (1982). A language action view of information systems. SYSLAB report no 14, SYSLAB, University of Stockholm, Stockholm, Sweden.

    Google Scholar 

  22. Grenning, J. (2001). Launching ‘XP at a Process-Intensive Company’, IEEE, 18: 3–9.

    Google Scholar 

  23. Harmsen, A. F. (1997). Situational Method Engineering. PhD dissertation. Moret Ernst & Young Management Consultants, Utrecht, The Netherlands.

    Google Scholar 

  24. Highsmith, J. A. (2000). Adaptive Software Development: A Collaborative Approach to Managing Complex Systems, Dorset House Publishing, New York.

    Google Scholar 

  25. Highsmith, J. and Cockburn, A. (2001). Agile Software Development – The Business of Innovation, Computer 34(9):120–122.

    Article  Google Scholar 

  26. IBM Software. (2008). Rational Rose Enterprise. http://www-306.ibm.com/software/awdtools/developer/rose/ enterprise/index.html. Site accessed Jan 26, 2008.

  27. Introna, L. D. and Whitley, E. A. (1997). Against method-ism. Information Technology & People, 10(1): 31–45.MCB University Press.

    Article  Google Scholar 

  28. Jayaratna, N. (1994). Understanding and Evaluating Methodologies, McGraw-Hill Book Company, London.

    Google Scholar 

  29. Juell-Skiels, G. (2007). In Swedish: Irrläror frälser oss inte., Computer Sweden, Oct 29.

    Google Scholar 

  30. Kruchten, P. (1999). The Rational Unified Process: An Introduction, Addison Wesley Inc., Reading, MA.

    Google Scholar 

  31. McCauley, R. (2001). Agile Development Methods, Poised to Upset Status Quo, SIGCSE Bullentin 33(4): 14–15.

    Article  Google Scholar 

  32. Mintzberg, H. (1983), Structure in Fives: Designing Effective Organizations, Prentice-Hall, Engle wood Cliffs, NJ.

    Google Scholar 

  33. Nandhakumar, J. and Avison J. (1999). The Fiction of Methodological Development – a Field Study of Information Systems Development, Information Technology & People 12(2): 175–191.

    Article  Google Scholar 

  34. Object Management Group. (2008). UML Resource Page. http://www.uml.org/. Site accessed Jan 26, 2008.

  35. Oxford English Dictionary. (2008). http://www.askoxford.com/. Site accessed Jan 26, 2008.

  36. Popkin Software. (2008). Systems Architect. http://www.telelogic.com/campaigns/popkin/index.cfm. Site accessed Jan 26, 2008.

  37. Rumbaugh, J., Blaha, M., Premerlani, W., Eddy, F. and Lorensen, W. (1991). Object-Oriented Modeling and Design, Prentice–Hall, Englewood Cliffs, NJ.

    Google Scholar 

  38. Schwaber, K. (1995). Scrum Development Process, OOPSLA 1995 Workshop on Business Object Design and Implementation, Springer-Verlag, Berlin.

    Google Scholar 

  39. Stolterman, E. (1991) The Hidden Rationale of Design Work (In Swedish: Designarbetets dolda rationalitet), PhD Thesis. Department of Information Processing, Umeå University, Sweden.

    Google Scholar 

  40. Suchman, L. A. (1987). Plans and Situated Actions: The Problem of Human-Machine Communication, Cambridge University Press, New York.

    Google Scholar 

  41. Takeuchi, H. and Nonaka, I. (1986). The new product development game, Harvard Business Review, Jan/Feb: 137–146.

    Google Scholar 

  42. Truex, D. P., Baskerville, R. and Travis, J. (2000), A methodical systems development: the deferred meaning of systems development methods, Accounting, Management and Information Technologies, 10(1): 53–79.

    Article  Google Scholar 

  43. Weber, M. (1978). Economy and Society, University of California Press, Berkeley, CA.

    Google Scholar 

  44. Wiegers, K. E. (1998). Read My Lips: No New Models, IEEE Software 15(5): 10–13.

    Article  Google Scholar 

  45. Yourdon, E. (1989). Modern Structured Analysis. Prentice-Hall, Englewood Cliffs, NJ.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2009 Springer Science+Business Media, LLC

About this chapter

Cite this chapter

Cronholm, S. (2009). Using Agile Methods? – Expected Effects. In: Papadopoulos, G., Wojtkowski, W., Wojtkowski, G., Wrycza, S., Zupancic, J. (eds) Information Systems Development. Springer, Boston, MA. https://doi.org/10.1007/b137171_96

Download citation

  • DOI: https://doi.org/10.1007/b137171_96

  • Published:

  • Publisher Name: Springer, Boston, MA

  • Print ISBN: 978-0-387-84809-9

  • Online ISBN: 978-0-387-84810-5

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics