Abstract
Flexible nature of scope definition in agile makes it difficult or impossible to measure its completeness and quality. The aim of this paper is to highlight the important ingredients of scope definition for agile projects and to present a method for agile projects in order to measure the quality and completeness of their scope definitions. The proposed method considers the elements that are retrieved as a result of the systematic literature review. An industrial survey is conducted to validate and prioritize these elements. Elements are then assigned weights according to their importance in scope definition to build a scorecard for calculating the score of user stories present in the product backlog. The proposed method is able to identify the clear and complete user stories that can better be implemented in the coming iteration. Formal experiments are performed for the evaluation of the proposed method, and it suggests that the method is useful for experts in order to quantify the completeness and quality of scope definition of an agile software project.
| Original language | English |
|---|---|
| Pages (from-to) | 5822-5847 |
| Number of pages | 26 |
| Journal | IEEE Access |
| Volume | 6 |
| DOIs | |
| Publication status | Published - 23 Oct 2017 |
Bibliographical note
© 2017 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works.Keywords
- Agile software development
- project management
- project planning
- project scope management
- scope definition