Skip to main content
SpringerLink
Log in

Requirements Engineering for Agile Methods

  • Chapter
Engineering and Managing Software Requirements

Abstract

Collecting, understanding, and managing requirements is a critical aspect in all development methods. This is true for Agile Methods as well. In particular, several agile practices deal with requirements in order to implement them correctly and satisfy the needs of the customer. These practices focus on a continuous interaction with the customer to address the requirements evolution over time, prioritize them, and deliver the most valuable functionalities first. This chapter introduces Agile Methods as the implementation of the principles of the lean production in software development. Therefore, Agile Methods focus on continuous process improvement through the identification and the removal of waste, whatever does not add value for the customer.

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

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Abrahamsson P, Salo O, Ronkainen J, Warsta J (2002) Agile software development methods: Review and analysis. EPSOO 2002, VTT Publications 478

    Google Scholar 

  2. Ambler S (2001) Agile documentation. Accessed on 5th December 2004. http://www.agilemodeling.com/essays/agileDocumentation.htm

    Google Scholar 

  3. Ambler S (2002) Lessons in agility from Internet-based development. IEEE Software, 19(2): 66–73

    Article  Google Scholar 

  4. Ambler S (2002) When does(n’t) Agile modeling make sense? Accessed on December 5, 2004, http://www.agilemodeling.com/essays/whenDoesAMWork.htm

    Google Scholar 

  5. Bailey P, Ashworth N, Wallace N (2002) Challenges for stakeholders in adopting XP. In: Proceedings of 3rd International Conference on eXtreme Programming and Agile Processes in Software Engineering (XP2002), Alghero, Italy, 26–29 May

    Google Scholar 

  6. Beck K (1999) Extreme programming explained: Embrace change. Addison-Wesley, UK

    Google Scholar 

  7. Beck K, Beedle M, Bennekum A, Cockburn A, Cunningham W, Fowler M, Grenning J, Highsmith J, Hunt A, Jeffries R, Kern J, Marick B, Martin RC, Mellor S, Schwaber K, Sutherland J, Thomas D (2001) Manifesto for Agile software Development. Accessed on 5th December 2004, online at: http://www.agilemanifesto.org/

    Google Scholar 

  8. Cockburn A, Williams L (2000) The costs and benefits of pair programming. In: Proceedings of 1st International Conference on eXtreme Programming and Agile Processes in Software Engineering (XP2000), Cagliari, Italy, 21–23 June

    Google Scholar 

  9. Cockburn A (2000) Selecting a project’s methodology. IEEE Software, 17(4): 64–71

    Article  Google Scholar 

  10. Cockburn A, Highsmith J (2001) Agile software development: The business of innovation. IEEE Computer, September, pp.120–122

    Google Scholar 

  11. Cockburn A, Highsmith J (2001) Agile software development: The people factor. IEEE Computer, November, pp.131–133

    Google Scholar 

  12. Cockburn A (2002) Agile software development. Addison-Wesley, London, UK

    Google Scholar 

  13. Duncan R (2001) The quality of requirements in extreme programming. The Journal of Defence Software Engineering, June 2001 issue

    Google Scholar 

  14. Cohen D, Lindvall M, Costa P (2003) Agile software development. DACS State-of-the-Art Report. Accessed 5th December 2004, http://www.dacs.dtic.mil/techs/agile/agile.pdf

    Google Scholar 

  15. Cohn M, Ford D (2002) Introducing an Agile process to an organization. Access on 5th December 2004 http://www.mountaingoatsoftware.com/articles/IntroducingAnAgileProcess.pdf

    Google Scholar 

  16. Glass R (2001) Agile versus traditional: Make love, not war. Cutter IT Journal, December, 6(1): 12–18

    Google Scholar 

  17. Highsmith JA (1996) Adaptive software development. Dorset House Publishing, UK

    Google Scholar 

  18. IEEE Standard 830 (1998) IEEE recommended practice for software requirements

    Google Scholar 

  19. IEEE Standard 1233 (1998) IEEE guide for developing system requirements specifications

    Google Scholar 

  20. IEEE Standard 1362 (1998) IEEE guide for information technology: System definition, concept of operations document

    Google Scholar 

  21. Lee C, Guadagno L, Jia X (2003) An Agile approach to capturing requirements and traceability. In: Proceedings of 2nd International Workshop on Traceability in Emerging Forms of Software Engineering, Montreal, Canada, 7 October 22.

    Google Scholar 

  22. Nawrocki J, Jasinski M, Walter B, Wojciechowski A (2002) Extreme programming modified: Embrace requirements engineering practices. In: Proceedings of International Conference on Requirements Engineering, 9–13 September, Essen, Germany

    Google Scholar 

  23. Ohno T (1988) Toyota production system: Beyond large-scale production. Productivity Press Cambridge, Mass

    Google Scholar 

  24. Paetsch F, Eberlein A, Maurer F (2003) Requirements engineering and Agile software development. In Proceedings of 8th International Workshop on Enterprise Security, Linz, Austria, 9–11 June

    Google Scholar 

  25. Poppendieck T, Poppendieck M (2003) Lean software development: An agile toolkit for software development managers. Addison-Wesley, London UK

    Google Scholar 

  26. Rasmusson J (2003) Introducing XP into Greenfield projects: Lessons learned. IEEE Software, May/June, 20(3): 21–28

    Article  Google Scholar 

  27. Ronkainen J, Abrahamsson P (2003) Software development under stringent hardware constraints: Do Agile methods have a chance. In: Proceedings of 4th International Conference on eXtreme Programming and Agile Processes in Software Engineering (XP2003), Genoa, Italy, May 2003, pp.25–29

    Google Scholar 

  28. Schwaber K, Beedle M (2001) Agile software development with scrum. Prentice Hall PTR, Australia

    Google Scholar 

  29. Sommerville I, Sawyer P, (2000) Requirements engineering: A good practice guide. John Wiley & Sons, UK

    Google Scholar 

  30. Smith J. (2001) A comparison of RUP and XP. Rational software white paper. Accessed 5th December 2005 http://www.isk.kth.se/proj/2003/6b3403/sa3/www/RationalUnifiedProcess/papers/rupxp.htm

    Google Scholar 

  31. Standish Group, CHAOS Report 1994. Accessed 5th December 2004. http://www.standishgroup.com/sample_research/chaos_1994_1.php

    Google Scholar 

  32. Stapleton J (1995) DSDM-Dynamic system development method. Addison-Wesley, UK

    Google Scholar 

  33. Tomayko JE (2002) Engineering of unstable requirements using Agile methods. In: Proceedings of International Conference on Time-Constrained Requirements Engineering, Essen, Germany, 9–13 September

    Google Scholar 

  34. Turk D, France R, Rumpe B (2002) Limitations of Agile software processes. In: Proceedings of 3rd International Conference on eXtreme Programming and Agile Processes in Software Engineering (XP2002), Alghero, Italy, 26–29 May

    Google Scholar 

  35. Wells D (2003) Don’t solve a problem before you get to it. IEEE Software, May/June, 20(3): 44–47

    Article  MathSciNet  Google Scholar 

  36. Womack JP, Jones DT (1998) Lean thinking: Banish waste and create wealth in your corporation, Simon & Schuster.

    Google Scholar 

  37. Young R (2002) Recommended requirements gathering practices, Accessed 5th December 2004, http://www.stsc.hill.af.mil/crosstalk/2002/04/young

    Google Scholar 

Download references

Authors
  1. Alberto Sillitti
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Giancarlo Succi
    View author publications

    You can also search for this author in PubMed Google Scholar

Editor information

Editors and Affiliations

  1. School of Information Systems, Technology and Management, University of New South Wales, Sydney, NSW, 2052, Australia

    Aybüke Aurum

  2. School of Engineering, Blekinge Institute of Technology, Box 520, 372 25, Ronneby, Sweden

    Claes Wohlin

Rights and permissions

Reprints and permissions

Copyright information

© 2005 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Sillitti, A., Succi, G. (2005). Requirements Engineering for Agile Methods. In: Aurum, A., Wohlin, C. (eds) Engineering and Managing Software Requirements. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-28244-0_14

Download citation

  • DOI: https://doi.org/10.1007/3-540-28244-0_14

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-25043-2

  • Online ISBN: 978-3-540-28244-0

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics

Search

Navigation