A Mapping Study on Requirements Engineering in Agile Software Development

Proceedings - 41st Euromicro Conference on Software Engineering and Advanced Applications, SEAA 2015

Volumn , Issue , 2015, Pages 199-207

  Heikkila, Ville T ^a,b   Damian, Daniela ^b   Lassenius, Casper ^a   Paasivaara, Maria ^b  

^a UNIVERSITY OF VICTORIA   (Canada)

^b AALTO UNIVERSITY   (Finland)

Author keywords

agile development; mapping study; requirements engineering; scrum

Indexed keywords

APPLICATION PROGRAMS; MAPPING; PUBLIC RELATIONS; REQUIREMENTS ENGINEERING; SOFTWARE DESIGN;

AGILE DEVELOPMENT; AGILE SOFTWARE DEVELOPMENT; CUSTOMER RELATIONSHIPS; CUSTOMER REPRESENTATIVE; DEVELOPMENT RESOURCES; MAPPING STUDIES; SCIENTIFIC LITERATURE; SCRUM;

SOFTWARE ENGINEERING;

EID: 84958267829     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/SEAA.2015.70     Document Type: Conference Paper

References (54)

1. J. Beall. Medical publishing triage-chronicling predatory open access publishers. Annals of Medicine and Surgery, 2(2):47-49, 2013.
2. K. Beck and C. Andres. Extreme programming explained : embrace change. Addison-Wesley, Boston, MA, USA, 2nd edition, 2004.
3. K. Beck, M. Beedle, A. van Bennekum, A. Cocburn, W. Cunningham, M. Fowler, J. Grenning, A. Hunt, R. Jeffries, J. Kern, B. Maric, R. C. Martin, S. Mellor, K. Schwaber, J. Sutherland, and D. Thomas. Manifesto for agile software development. http://agilemanifesto.org/, 2001. Retrieved Sep 17th, 2014.
4. P. Berander and A. Andrews. Requirements prioritization. In A. Aurum and C. Wohlin, editors, Engineering and Managing Software Requirements, pages 69-94. Springer Berlin Heidelberg, 2005.
5. B. W. Boehm. Requirements that handle ikiwisi, cots, and rapid change. Computer, 33(7):99-102, 2000.
6. I. K. Bray. An introduction to requirements engineering. Addison-Wesley, Harlow, UK, 2002.
7. R. Britto, M. Usman, and E. Mendes. Effort estimation in agile global software development context. In T. Dingsr, N. Moe, R. Tonelli, S. Counsell, C. Gencel, and K. Petersen, editors, Agile Methods-Large-Scale Development, Refactoring, Testing, and Estimation, volume 199 of Lecture Notes in Business Information Processing, pages 182-192. Springer, 2014.
8. I. F. da Silva, P. A. da Mota Silveira Neto, P. OLeary, E. S. de Almeida, and S. R. de Lemos Meira. Agile software product lines: A systematic mapping study. Software: Practice and Experience, 41(8):899-920, 2011.
9. P. Deemer, G. Benefield, C. Larman, and B. Vodde. The Scrum Primer-A lightweight guide to the theory and practice of Scrum, version 2. Technical report, 2012.
10. P. Diebold and M. Dahlem. Agile practices in practice: A mapping study. In Proc. 18th International Conference on Evaluation and Assessment in Software Engineering (EASE 14), pages 30:1-30:10, New York, NY, USA, 2014. ACM.
11. T. Dingsr, S. Nerur, V. Balijepally, and N. B. Moe. A decade of agile methodologies: Towards explaining agile software development. Journal of Systems and Software, 85(6):1213-1221, 2012.
12. T. Dyba and T. Dingsr. Empirical studies of agile software development: A systematic review. Information and Software Technology, 50(9-10):833-859, 8 2008.
13. H. Erdogmus. Tips for software authors. IEEE Software, 24(5):5-7, Sept 2007.
14. E. Hossain, M. A. Babar, and P. Hye-young. Using Scrum in global software development: A systematic literature review. In Proc. Fourth IEEE International Conference on Global Software Engineering (ICGSE 2009), pages 175-184, July 2009.
15. I. Inayat, S. S. Salim, S. Marczak, M. Daneva, and S. Shamshirband. A systematic literature review on agile requirements engineering practices and challenges. Computers in Human Behavior, in press, 2014.
16. ISO/IEC/IEEE. Systems and software engineering-life cycle processes-requirements engineering. International Standard 29148:2011(E), pages 1-94, Dec 2011.
17. G. Jurca, T. D. Hellmann, and F. Maurer. Integrating agile and user-centered design: A systematic mapping and review of evaluation and validation studies of agile-UX. In Proc. Agile Conference (AGILE), pages 24-32, July 2014.
18. B. A. Kitchenham and S. Charters. Guidelines for performing systematic literature reviews in software engineering. Technical Report EBSE 2007-001, Keele University and Durham University, 2007. Version 2.3.
19. D. Salah, R. F. Paige, and P. Cairns. A systematic literature review for agile development processes and user centred design integration. In Proc. 18th International Conference on Evaluation and Assessment in Software Engineering (EASE 14), pages 5:1-5:10, New York, NY, USA, 2014. ACM.
20. K. Schwaber and M. Beedle. Agile software development with Scrum. Prentice-Hall, Upper Saddle River, NJ, USA, 2002.
21. K. Schwaber and J. Sutherland. The Scrum Guide-The definitive guide to Scrum: The rules of the game. Technical report, Scrum.org, July 2013.
22. P. Sfetsos and I. Stamelos. Empirical studies on quality in agile practices: A systematic literature review. In Proc. Seventh International Conference on the Quality of Information and Communications Technology (QUATIC), pages 44-53, Sept 2010.
23. O. Sohaib and K. Khan. Integrating usability engineering and agile software development: A literature review. In Proc. 2010 International Conference on Computer Design and Applications (ICCDA), volume 2, pages 32-38, June 2010.
24. S. Stavru. A critical examination of recent industrial surveys on agile method usage. Journal of Systems and Software, 94(0):87, 2014.
25. M. Usman, E. Mendes, F. Weidt, and R. Britto. Effort estimation in agile software development: A systematic literature review. In Proc. 10th International Conference on Predictive Models in Software Engineering (PROMISE 14), pages 82-91, New York, NY, USA, 2014. ACM.
26. VersionOne, Inc. 8th annual "State of Agile Development" survey. Technical report, 2014.
27. J. Arajo and J. C. Ribeiro. Towards an aspect-oriented agile requirements approach. In Proc. Eighth International Workshop on Principles of Software Evolution, pages 140-143, Sept 2005.
28. E. Bjarnason, K. Wnuk, and B. Regnell. A case study on benefits and side-effects of agile practices in large-scale requirements engineering. In Proc. 1st Workshop on Agile Requirements Engineering (AREW 11), pages 3:1-3:5, New York, NY, USA, 2011. ACM.
29. E. Bjarnason, K. Wnuk, and B. Regnell. Are you biting off more than you can chew? a case study on causes and effects of overscoping in large-scale software engineering. Information and Software Technology, 54(10):1107-1124, 10 2012.
30. L. Cao and B. Ramesh. Agile requirements engineering practices: An empirical study. Software, 25(1):60-67, 2008.
31. M. Daneva, E. van der Veen, C. Amrit, S. Ghaisas, K. Sikkel, R. Kumar, N. Ajmeri, U. Ramteerthkar, and R. Wieringa. Agile requirements prioritization in large-scale outsourced system projects: An empirical study. Journal of Systems and Software, 86(5):1333-1353, 5 2013.
32. S. Dimitrijevi, J. Jovanovi, and V. Devedži. A comparative study of software tools for user story management. Information and Software Technology, (in press).
33. N. A. Ernst and G. C. Murphy. Case studies in just-intime requirements analysis. In Proc. Second International Workshop on Empirical Requirements Engineering (EmpiRE), pages 25-32. IEEE, 2012.
34. D. Firesmith. Generating complete, unambiguous, and verifiable requirements from stories, scenarios, and use cases. Journal of Object Technology, 3(10):27-39, 2004.
35. X. Ge, R. F. Paige, F. A. C. Polack, H. Chivers, and P. J. Brooke. Agile development of secure web applications. In Proc. 6th International Conference on Web Engineering (ICWE 06), pages 305-312, New York, NY, USA, 2006. ACM.
36. B. Haugset and T. Stalhane. Automated acceptance testing as an agile requirements engineering practice. In Proc. 45th Hawaii International Conference on System Science (HICSS-45), pages 5289-5298, 2012.
37. E. Hochmuller. The requirements engineer as a liaison officer in agile software development. In Proc. 1st Workshop on Agile Requirements Engineering (AREW 11), pages 2:1-2:4, New York, NY, USA, 2011. ACM.
38. O. Ktata and G. Lovesque. Agile development: Issues and avenues requiring a substantial enhancement of the business perspective in large projects. In Proc. 2nd Canadian Conference on Computer Science and Software Engineering (C3S2E 09), pages 59-66, New York, NY, USA, 2009. ACM.
39. A. Lucia and A. Qusef. Requirements engineering in agile software development. Journal of Emerging Technologies in Web Intelligence, 2(3), 2010.
40. L. Ludlow. The application of user stories for strategic planning. In G. Concas, E. Damiani, M. Scotto, and G. Succi, editors, Agile Processes in Software Engineering and Extreme Programming, volume 4536 of Lecture Notes in Computer Science, pages 198-202, 2007.
41. I. Mahmud and V. Veneziano. Mind-mapping: An effective technique to facilitate requirements engineering in agile software development. In Proc. 14th International Conference on Computer and Information Technology (CIT-2014), pages 157-162, 2011.
42. N. Maiden. Cherishing ambiguity. Software, IEEE, 29(6):16-17, 2012.
43. R. Mugridge. Managing agile project requirements with storytest-driven development. Software, IEEE, 25(1):68-75, 2008.
44. R. Noordeloos, C. Manteli, and H. van Vliet. From RUP to Scrum in global software development: A case study. In Proc. Seventh International Conference on Global Software Engineering (ICGSE), pages 31-40. IEEE, 2012.
45. K. Orr. Agile requirements: opportunity or oxymoron? Software, IEEE, 21(3):71-73, May 2004.
46. F. Paetsch, A. Eberlein, and F. Maurer. Requirements engineering and agile software development. In Proc. Twelfth IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises (WET ICE), pages 308-313, 2003.
47. Z. Racheva and M. Daneva. How do real options concepts fit in agile requirements engineering? In Proc. Eighth ACIS International Conference on Software Engineering Research, Management and Applications (SERA), pages 231-238, 2010.
48. Z. Racheva, M. Daneva, K. Sikkel, A. Herrmann, and R. Wieringa. Do we know enough about requirements prioritization in agile projects: Insights from a case study. In Proc. 18th IEEE International Requirements Engineering Conference (RE 2010), pages 147-156, 2010.
49. B. Ramesh, L. Cao, and R. Baskerville. Agile requirements engineering practices and challenges: An empirical study. Information Systems Journal, 20(5):449-480, 2010.
50. J. Savolainen, J. Kuusela, and A. Vilavaara. Transition to agile development-rediscovery of important requirements engineering practices. In Proc. 18th IEEE International Requirements Engineering Conference (RE 2010), pages 289-294, Sept 2010.
51. I. Sommerville. Integrated requirements engineering: A tutorial. Software, IEEE, 22(1):16-23, 2005.
52. N. C. Surendra. Using an ethnographic process to conduct requirements analysis for agile systems development. Information Technology and Management, 9(1):55-69, 2008.
53. K. Vlaanderen, S. Jansen, S. Brinkkemper, and E. Jaspers. The agile requirements refinery: Applying SCRUM principles to software product management. Information and Software Technology, 53(1):58-70, 1 2011.
54. B. Waldmann. Theres never enough time: Doing requirements under resource constraints, and what requirements engineering can learn from agile development. In Proc. 19th IEEE International Requirements Engineering Conference (RE 11), pages 301-305, 2011.