Details
| Original language | English |
|---|---|
| Title of host publication | Agile Processes in Software Engineering and Extreme Programming |
| Subtitle of host publication | 15th International Conference, XP 2014, Proceedings |
| Publisher | Springer Verlag |
| Pages | 110-125 |
| Number of pages | 16 |
| ISBN (print) | 9783319068619 |
| Publication status | Published - 2014 |
| Event | 15th International Conference on Agile Software Development, XP 2014 - Rome, Italy Duration: 26 May 2014 → 30 May 2014 |
Publication series
| Name | Lecture Notes in Business Information Processing |
|---|---|
| Volume | 179 LNBIP |
| ISSN (Print) | 1865-1348 |
Abstract
User stories are a widespread instrument for representing requirements. They describe small user-oriented parts of the system and guide the daily work of developers. Often however, user stories are too coarse, so that misunderstandings or dependencies remain unforeseeable. Granularity of user stories needs to be investigated more, but at the same time is a hard-to-grasp concept. This paper investigates Expected Implementation Duration (EID) of a user story as a characteristic of granularity. We want to find out, whether it is suitable as a quality aspect and can help software teams improve their user stories. We have conducted a study with software engineering practitioners. There, many user stories had a relatively high EID of four or more days. Many developers state to have experienced certain problems to occur more often with such coarse user stories. Our findings emphasize the importance to reflect on granularity when working with user stories.
Keywords
- Requirements quality, User requirements, User stories
ASJC Scopus subject areas
- Business, Management and Accounting(all)
- Management Information Systems
- Engineering(all)
- Control and Systems Engineering
- Business, Management and Accounting(all)
- Business and International Management
- Computer Science(all)
- Information Systems
- Mathematics(all)
- Modelling and Simulation
- Decision Sciences(all)
- Information Systems and Management
Cite this
- Standard
- Harvard
- Apa
- Vancouver
- BibTeX
- RIS
Agile Processes in Software Engineering and Extreme Programming : 15th International Conference, XP 2014, Proceedings. Springer Verlag, 2014. p. 110-125 (Lecture Notes in Business Information Processing; Vol. 179 LNBIP).
Research output: Chapter in book/report/conference proceeding › Conference contribution › Research › peer review
}
TY - GEN
T1 - Why we need a granularity concept for user stories
AU - Liskin, Olga
AU - Pham, Raphael
AU - Kiesling, Stephan
AU - Schneider, Kurt
PY - 2014
Y1 - 2014
N2 - User stories are a widespread instrument for representing requirements. They describe small user-oriented parts of the system and guide the daily work of developers. Often however, user stories are too coarse, so that misunderstandings or dependencies remain unforeseeable. Granularity of user stories needs to be investigated more, but at the same time is a hard-to-grasp concept. This paper investigates Expected Implementation Duration (EID) of a user story as a characteristic of granularity. We want to find out, whether it is suitable as a quality aspect and can help software teams improve their user stories. We have conducted a study with software engineering practitioners. There, many user stories had a relatively high EID of four or more days. Many developers state to have experienced certain problems to occur more often with such coarse user stories. Our findings emphasize the importance to reflect on granularity when working with user stories.
AB - User stories are a widespread instrument for representing requirements. They describe small user-oriented parts of the system and guide the daily work of developers. Often however, user stories are too coarse, so that misunderstandings or dependencies remain unforeseeable. Granularity of user stories needs to be investigated more, but at the same time is a hard-to-grasp concept. This paper investigates Expected Implementation Duration (EID) of a user story as a characteristic of granularity. We want to find out, whether it is suitable as a quality aspect and can help software teams improve their user stories. We have conducted a study with software engineering practitioners. There, many user stories had a relatively high EID of four or more days. Many developers state to have experienced certain problems to occur more often with such coarse user stories. Our findings emphasize the importance to reflect on granularity when working with user stories.
KW - Requirements quality
KW - User requirements
KW - User stories
UR - http://www.scopus.com/inward/record.url?scp=84904549332&partnerID=8YFLogxK
U2 - 10.1007/978-3-319-06862-6_8
DO - 10.1007/978-3-319-06862-6_8
M3 - Conference contribution
AN - SCOPUS:84904549332
SN - 9783319068619
T3 - Lecture Notes in Business Information Processing
SP - 110
EP - 125
BT - Agile Processes in Software Engineering and Extreme Programming
PB - Springer Verlag
T2 - 15th International Conference on Agile Software Development, XP 2014
Y2 - 26 May 2014 through 30 May 2014
ER -