Improving User Story Practice with the Grimm Method: A Multiple Case Study in the Software Industry

Context and motivation: Previous research shows that a considerable amount of real-world user stories contain easily preventable syntactic defects that violate desired qualities of good requirements. However, we still do not know the effect of user stories’ intrinsic quality on practitioners’ work. Question/Problem: We study the effects of introducing the Grimm Method’s Quality User Story framework and the AQUSA tool on the productivity and work deliverable quality of 30 practitioners from 3 companies over a period of 2 months. Principal ideas/results: Our multiple case study delivered mixed findings. Despite an improvement in the intrinsic user story quality, practitioners did not perceive such a change. They explained, however, there was more constructive user story conversation in the post-treatment period leading to less unnecessary rework. Conversely, project management metrics did not result in statistically significant changes in the number of comments, issues, defects, velocity, and rework. Contribution: Introducing our treatment has a mildly positive effect but a larger scale investigation is crucial to decisively assess the impact on work practice. Also, our case study protocol serves as an example for evaluating RE research in practice.

[1]  Christopher W. H. Davis Agile Metrics in Action: Measuring and Enhancing the Performance of Agile Teams , 2015 .

[2]  Ahmed E. Hassan,et al.  Understanding the impact of code and process metrics on post-release defects: a case study on the Eclipse project , 2010, ESEM '10.

[3]  Tony Gorschek,et al.  Evaluation and Measurement of Software Process Improvement—A Systematic Literature Review , 2012, IEEE Transactions on Software Engineering.

[4]  Lech Madeyski,et al.  Which process metrics can significantly improve defect prediction models? An empirical study , 2014, Software Quality Journal.

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

[6]  A. Zeller,et al.  If Your Bug Database Could Talk . . . , 2006 .

[7]  Stefan Wagner,et al.  A Case Study on Artefact-Based RE Improvement in Practice , 2015, PROFES.

[8]  Anas N. Al-Rabadi,et al.  A comparison of modified reconstructability analysis and Ashenhurst‐Curtis decomposition of Boolean functions , 2004 .

[9]  Tetsuo Tamai,et al.  How Does Requirements Quality Relate to Project Success or Failure? , 2007, 15th IEEE International Requirements Engineering Conference (RE 2007).

[10]  J. Chall,et al.  Readability revisited : the new Dale-Chall readability formula , 1995 .

[11]  Teodor Sommestad,et al.  Requirements engineering: The quest for the dependent variable , 2015, 2015 IEEE 23rd International Requirements Engineering Conference (RE).

[12]  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).

[13]  Walt Detmar Meurers,et al.  Readability-based Sentence Ranking for Evaluating Text Simplification , 2016, ArXiv.

[14]  Jie Sun,et al.  The Role of Requirements Engineering Practices in Agile Development: An Empirical Study , 2014, APRES.

[15]  Per Runeson,et al.  Guidelines for conducting and reporting case study research in software engineering , 2009, Empirical Software Engineering.

[16]  Jean Tague-Sutcliffe,et al.  The Pragmatics of Information Retrieval Experimentation Revisited , 1997, Inf. Process. Manag..

[17]  Nannette P. Napier,et al.  Combining Perceptions and Prescriptions in Requirements Engineering Process Assessment: An Industrial Case Study , 2009, IEEE Transactions on Software Engineering.

[18]  Eric Knauss,et al.  Investigating the Impact of Software Requirements Specification Quality on Project Success , 2009, PROFES.

[19]  Ian Sommerville,et al.  An empirical study of industrial requirements engineering process assessment and improvement , 2005, TSEM.

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

[21]  R. Gunning The Technique of Clear Writing. , 1968 .

[22]  A. Zeller,et al.  Predicting Defects for Eclipse , 2007, Third International Workshop on Predictor Models in Software Engineering (PROMISE'07: ICSE Workshops 2007).

[23]  Daniela E. Damian,et al.  Requirements Engineering and Downstream Software Development: Findings from a Case Study , 2005, Empirical Software Engineering.

[24]  G. G. Stokes "J." , 1890, The New Yale Book of Quotations.

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