원문정보
초록
영어
Software requirements should be accurately captured in the form of user stories so that development teams are able to meet customer expectations for the software. This study investigates the various challenges in capturing requirements of the agile scrum methodology and proposes some improvements. A user story writing workshop was conducted based on a standard set of business requirements. The resulting user stories were analyzed for correctness and problem areas were identified. Then a separate industry survey was conducted to confirm that the problem areas found in this workshop are indeed the common problem areas for industry practitioners. A set of improvements were then identified to address the problem areas. A second workshop was then conducted to check whether the improvements actually result in better user story writing. The results of the second workshop suggest that the improvements were quite effective in resolving most of the problem areas. They can thus be adopted by industry practitioners as best practices.
목차
1. Introduction
2. Methodology
3. Experiment I: User Story Writing Workshop I
3.1. Material and Experimental Tasks
4. Analysis: User Story Writing Workshop I
5. Correlation of Problem Areas between Survey Responses and Workshop I
6. Improvements Proposed for Writing User Stories
6.1. Improvement 1: User Role Modeling and Persona Support
6.2. Improvement 2: Template for Writing User Story
6.3. Improvement 3: Accurately Defining User Stories
6.4. Improvement 4: Assigning Correct Priority to User Story
6.5. Improvement 5: Writing Effective Acceptance Criteria
6.6. Improvement 6: Coverage of NFR in User Stories or in Acceptance Criteria
6.7. Improvement 7: Typos and Grammatical errors in user Stories and Acceptance Criteria
7. Experiment II: User Story Writing Workshop II
7.1. Material used for the Workshop II
8. Results and Discussions
8.1. Improvements in Workshop II from Learning in Workshop I are as follows –
9. Validity of Results
10. Conclusion
References