Skip to main content

Agile Support and Maintenance of IT Services

  • Conference paper
  • First Online:
Information Systems Development

Abstract

In this paper, we deal with agile and lean support and maintenance of IT services. Agile approaches are considered as software development approaches mostly, but the usage of agile principles and techniques also brings a lot of benefits to the support and maintenance. Common support and maintenance standards, recommendations and methods are process oriented and omit human aspect. Paper takes a critical viewpoint of process-orientation. We define agile and lean support and maintenance principles and control framework for improvement and implementation of these principles in IT services. The described approach was piloted in 13 IT services. Achievements are enclosed as verification of practical results and benefits.

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. OGC (2007) The official introduction to the ITIL service lifecycle, version 3. TSO, London

    Google Scholar 

  2. ISO 12207:2008 (2008) Standard for software lifecycle processes

    Google Scholar 

  3. IEEE Std. 610.12 (1990) Standard glossary of software engineering terminology. IEEE, Computer Society Press, Los Alamitos

    Google Scholar 

  4. Hopkins R, Jenkins K (2008) Eating the IT elephant. IBM Press, Upper Saddle River

    Google Scholar 

  5. Boehm B (1981) Software engineering economics. Prentice Hall, Englewood Cliffs

    MATH  Google Scholar 

  6. ISO 14764:2006 (2006) Standard for software lifecycle processes—maintenance

    Google Scholar 

  7. IEEE 1219 (1998) Standard for software maintenance

    Google Scholar 

  8. ISO 20000 (2007) Standard for service management—Part 1, Part 2

    Google Scholar 

  9. Polo M, Piattini M, Ruiz F, Calero C (1999) MANTEMA: a software maintenance methodology based on the ISO/IEC12207 standard. In: Fourth IEEE international symposium and forum on software engineering standards, pp 76–81

    Google Scholar 

  10. Schwaber K (2004) Agile project management with scrum. Microsoft Press, Redmond

    MATH  Google Scholar 

  11. Beck K (1999) Extreme programming explained. Embrace change. Addison-Wesley, New York

    Google Scholar 

  12. Poppendieck M (2006) Implementing lean software development. Addison-Wesley, New York

    Google Scholar 

  13. Agile Manifesto (2001) http://agilemanifesto.org. Accessed 21 Jan 2010

  14. de Souza SC et al (2007) Which documentation for software maintenance? J Braz Comput Soc 13(2):31–44

    MathSciNet  Google Scholar 

  15. Liker J (2003) The Toyota way. McGraw-Hill, New York

    MATH  Google Scholar 

  16. Rudzki J, Hammouda I, Mikkola T (2009) Agile experiences in software service company. In: SEAA conference, IEEE Computer Society, pp 224–228

    Google Scholar 

  17. Svensson H, Host M (2005) Introducing an agile process in software maintenance and evolution organization. In Proceedings of the 9th European conference on software maintenance and reengineering, pp 256–264

    Google Scholar 

  18. Brooks FP Jr (1987) No silver bullet. IEEE Comput 20(4):10–19

    Article  Google Scholar 

  19. Canfora G, Cimitile A (1995) Software maintenance. In Proceedings of the 7th international conference software engineering and knowledge engineering, pp 478–486

    Google Scholar 

  20. Bills M (2004) ROI: bad practice, poor results. Cutter IT J 17(8):10–15

    Google Scholar 

  21. Standish Group (2009) Chaos research 1999–2009

    Google Scholar 

  22. Martorelli B (2010) Application outsourcing clients are satisfied, but want more. Forrester (Published on April 21)

    Google Scholar 

  23. Lientz BP, Swanson EB (1981) Problems in application software maintenance. CACM 24(11):763–769

    Article  Google Scholar 

  24. Selby R (2007) Software engineering: Barry W. Boehm’s lifetime contributions to software development, management, and research. Wiley, New York (Reprinted edition)

    Book  Google Scholar 

  25. Palvia P, Patula A, Nosek J (1995) Problems and issues in application software maintenance management. J Inf Technol Manag VI(3):17–28

    Google Scholar 

  26. Kroll P, Cantor M (2009) Software and system development with the IBM measured capability improvement framework. IBM white paper

    Google Scholar 

  27. OpenUP Development Framework (2007) http://epf.eclipse.org/. Accessed 27 Jan 2010

  28. Kroll P, Kruchten P (2003) The rational unified process: made easy. Addison-Wesley, New York

    Google Scholar 

  29. Williams LA, Kessler R (2000) All i really need to know about pair programming i learned in kindergarted. CACM 43(5):109–114

    Article  Google Scholar 

  30. Constantine LL (1995) Constantine on peopleware. Yourdon Press, Englwood Cliffs

    Google Scholar 

  31. Buchalcevova A (2009) Research of the use of Agile methodologies in the Czech Republic. In: Information systems development challenges in practice, theory, and education. Springer, New York, pp 51–64. doi: 1007/978-0-387-68772-8_5

    Google Scholar 

  32. Prochazka J (2008) Experience from Agile adoption in distributed environment. In: Software development conference. VSB-TU Ostrava, pp 156–163

    Google Scholar 

  33. Poole CJ, Huisman JW (2001) Using extreme programming in a maintenance environment. IEEE Software 18(6):42–50

    Article  Google Scholar 

  34. Dettmer HW (1997) Goldratt’s theory of constraints. ASQ Quality Press, Milwaukee

    Google Scholar 

  35. Eclipse Way (2003). http://www.eclipse.org. Accessed 21 Jan 2010

  36. Doran G (1981) There’s a S.M.A.R.T. way to write managements’ goals and objectives. Manag Rev 70(11):35–36 (November)

    Google Scholar 

  37. Park RE (1996) Goal-driven software measurement. CMU/SEI-96-HB-002

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Jaroslav Prochazka .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2011 Springer Science+Business Media, LLC

About this paper

Cite this paper

Prochazka, J. (2011). Agile Support and Maintenance of IT Services. In: Pokorny, J., et al. Information Systems Development. Springer, New York, NY. https://doi.org/10.1007/978-1-4419-9790-6_48

Download citation

  • DOI: https://doi.org/10.1007/978-1-4419-9790-6_48

  • Published:

  • Publisher Name: Springer, New York, NY

  • Print ISBN: 978-1-4419-9645-9

  • Online ISBN: 978-1-4419-9790-6

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics