User Story Writing in Crowd Requirements Engineering: The Case of a Web Application for Sports Tournament Planning

Although users feel more engaged when they are involved in the elicitation, negotiation and prioritization of requirements for a product or service they are using, the quality of crowdsourced requirements remains an issue. Simple notations like user stories have been highly adopted by practitioners in agile development to capture requirements for a software product, but their utilization in crowdsourced requirements engineering is still scarce. Through a case study of a web application for sports tournament planning, we investigate how a dedicated platform for user story writing in crowd requirements engineering is valued by its users and we show that the delivered requirements are not inferior to those written by professionals.

[1]  Olga Liskin,et al.  How Artifacts Support and Impede Requirements Communication , 2015, REFSQ.

[2]  Mike Cohn,et al.  User Stories Applied: For Agile Software Development , 2004 .

[3]  Neil A. M. Maiden,et al.  Acquiring COTS software selection requirements , 1998, Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.

[4]  Sjaak Brinkkemper,et al.  Engaging the Crowd of Stakeholders in Requirements Engineering via Gamification , 2017 .

[5]  Sjaak Brinkkemper,et al.  Improving agile requirements: the Quality User Story framework and tool , 2016, Requirements Engineering.

[6]  Jörg Thomaschewski,et al.  Agile Requirements Engineering: A systematic literature review , 2017, Comput. Stand. Interfaces.

[7]  Sjaak Brinkkemper,et al.  REfine: A gamified platform for participatory requirements engineering , 2015, 2015 IEEE 1st International Workshop on Crowd-Based Requirements Engineering (CrowdRE).

[8]  Keith Phalp,et al.  Modelling Users Feedback in Crowd-Based Requirements Engineering: An Empirical Study , 2015, PoEM.

[9]  Klaas-Jan Stol,et al.  Two's company, three's a crowd: a case study of crowdsourcing software development , 2014, ICSE.

[10]  Martin Glinz,et al.  GARUSO: a gamification approach for involving stakeholders outside organizational reach in requirements engineering , 2019, Requirements Engineering.

[11]  Robert M. Davison,et al.  Principles of canonical action research , 2004, Inf. Syst. J..

[12]  Fabiano Dalpiaz.  Requirements data sets (user stories) , 2018 .

[13]  Mark Harman,et al.  A survey of the use of crowdsourcing in software engineering , 2017, J. Syst. Softw..

[14]  Roel Wieringa,et al.  Technical Action Research as a Validation Method in Information Systems Design Science , 2012, DESRIST.

[15]  Mohamad Kassab,et al.  The changing landscape of requirements engineering practices over the past decade , 2015, 2015 IEEE Fifth International Workshop on Empirical Requirements Engineering (EmpiRE).

[16]  Sjaak Brinkkemper,et al.  The Use and Effectiveness of User Stories in Practice , 2016, REFSQ.

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

[18]  Daniela E. Damian,et al.  StakeSource2.0: using social networks of stakeholders to identify and prioritise requirements , 2011, 2011 33rd International Conference on Software Engineering (ICSE).

[19]  Matthias Jarke,et al.  Requirements Bazaar: Social requirements engineering for community-driven innovation , 2013, 2013 21st IEEE International Requirements Engineering Conference (RE).