Requirements Engineering Practice and Problems in Agile Projects: Results from an International Survey

Requirements engineering (RE) is considerably dierent in agile development than in traditional processes. Yet, there is little em- pirical knowledge on the state of the practice and contemporary prob- lems in agile RE. As part of a bigger survey initiative (Naming the Pain in Requirements Engineering), we build an empirical basis on such as- pects of agile RE. Based on the responses from 92 people representing 92 organisations, we found that agile RE concentrates on free-text doc- umentation of requirements elicited with a variety of techniques. Many manage explicit traces between requirements and code. Furthermore, the continuous improvement of RE is done because of intrinsic motivation. Important experienced problems include unclear requirements and com- munication aws. Hence, agile RE is in several aspects not so dierent from RE in other development processes. We plan to investigate spe- cic techniques, such as acceptance-test-driven development, in a future survey to better capture what is special in agile RE.

[1]  Tayana Conte,et al.  Naming the Pain in Requirements Engineering: Comparing Practices in Brazil and Germany , 2015, IEEE Software.

[2]  Tayana Conte,et al.  Towards Building Knowledge on Causes of Critical Requirements Engineering Problems , 2015, SEKE.

[3]  Michael Felderer,et al.  Preventing Incomplete/Hidden Requirements: Reflections on Survey Data from Austria and Brazil , 2016, SWQD.

[4]  Daniel Méndez Fernández,et al.  Naming the Pain in Requirements Engineering - NaPiRE-Report 2013 , 2013 .

[5]  Orit Hazzan,et al.  The Agile Manifesto , 2014 .

[6]  Andreas Hoffmann,et al.  Model-Based Testing , 2012, IEEE Software.

[7]  Sabrina Marczak,et al.  A systematic literature review on agile requirements engineering practices and challenges , 2015, Comput. Hum. Behav..

[8]  Guilherme Horta Travassos,et al.  Automating and Evaluating Probabilistic Cause-Effect Diagrams to Improve Defect Causal Analysis , 2011, PROFES.

[9]  Daniela E. Damian,et al.  A Mapping Study on Requirements Engineering in Agile Software Development , 2015, 2015 41st Euromicro Conference on Software Engineering and Advanced Applications.

[10]  Stefan Wagner,et al.  What Do Practitioners Vary in Using Scrum? , 2015, XP.

[11]  Stefan Wagner,et al.  Naming the pain in requirements engineering: design of a global family of surveys and first results from Germany , 2013, EASE '13.

[12]  Dave Astels,et al.  The RSpec Book: Behaviour Driven Development with RSpec, Cucumber, and Friends , 2010 .

[13]  Dean Leffingwell,et al.  Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise , 2011 .

[14]  Kent L. Beck,et al.  Test-driven Development - by example , 2002, The Addison-Wesley signature series.

[15]  Des Greer,et al.  The Maturation of Agile Software Development Principles and Practice: Observations on Successive Industrial Studies in 2010 and 2012 , 2013, 2013 20th IEEE International Conference and Workshops on Engineering of Computer Based Systems (ECBS).

[16]  Betty H. C. Cheng,et al.  Research Directions in Requirements Engineering , 2007, Future of Software Engineering (FOSE '07).

[17]  Roel Wieringa,et al.  Naming the pain in requirements engineering , 2016, Empirical Software Engineering.

[18]  Michael Felderer,et al.  Manual test case derivation from UML activity diagrams and state machines: A controlled experiment , 2015, Inf. Softw. Technol..

[19]  Roel Wieringa,et al.  Naming the pain in requirements engineering , 2016, Empirical Software Engineering.