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.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
Bjarnason, E., Wnuk, K., Regnell, B.: Are you biting off more than you can chew? A case study on causes and effects of overscoping in large-scale software engineering. Information & Software Technology 54(10), 1107–1124 (2012)
Cao, L., Ramesh, B.: Agile requirements engineering practices: An empirical study. IEEE Software 25, 60–67 (2008)
Cockburn, A., Highsmith, J.: Agile software development, the people factor. IEEE Computer 34(11), 131–133 (2001)
Cohn, M.: User Stories Applied: For Agile Software Development. Prentice Hall (2004)
Cohn, M.: Agile Estimating and Planning. Pearson Education (2005)
Coughlan, J., Macredie, R.D.: Effective communication in requirements elicitation: A comparison of methodologies. Requirements Engineering 7(2), 47–60 (2002)
Haugen, N.C.: An empirical study of using planning poker for user story estimation. In: Agile Conference 2006, pp. 9–34 (2006)
Imaz, M., Benyon, D.: How stories capture interaction. In: INTERACT 1999, IFIP TC.13, pp. 321–328. IOS Press (1999)
Mahniç, V., Hovelja, T.: On using planning poker for estimating user stories. Journal of Systems and Software 85(9), 2086–2095 (2012)
Miranda, E., Bourque, P., Abran, A.: Sizing user stories using paired comparisons. Information and Software Technology 51(9), 1327–1337 (2009)
Patel, C., Ramachandran, M.: Story card based agile software development. International Journal of Hybrid Information Technology 2(2), 125–140 (2009)
Schwaber, K., Beedle, M.: Agile Software Development with Scrum. Prentice Hall (2002)
Tamrakar, R., Jørgensen, M.: Does the use of Fibonacci numbers in Planning Poker affect effort estimates? In: Proceedings of the 16th International Conference on Evaluation & Assessment in Software Engineering (EASE 2012), pp. 228–232 (2012)
Wake, W.C.: INVEST in Good Stories, and SMART Tasks. XP123 (2003), http://xp123.com/articles/invest-in-good-stories-and-smart-tasks/
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2014 Springer International Publishing Switzerland
About this paper
Cite this paper
Liskin, O., Pham, R., Kiesling, S., Schneider, K. (2014). Why We Need a Granularity Concept for User Stories. In: Cantone, G., Marchesi, M. (eds) Agile Processes in Software Engineering and Extreme Programming. XP 2014. Lecture Notes in Business Information Processing, vol 179. Springer, Cham. https://doi.org/10.1007/978-3-319-06862-6_8
Download citation
DOI: https://doi.org/10.1007/978-3-319-06862-6_8
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-06861-9
Online ISBN: 978-3-319-06862-6
eBook Packages: Computer ScienceComputer Science (R0)