Abstract
In agile development stories are typically used to define small, independent pieces of functionality that have value for the customer. They are most often used to define requirements for future development. This paper describes a project where stories were used on a much broader scale as part of a strategic planning exercise to identify a long-term development roadmap for a new system. Stories were used not only to define what needed to be built but also to document existing functionality and gaps with current systems. This resulted in the generation of a large number of stories, which created challenges with managing and keeping the stories up to date as the project proceeded.
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
Beck, K.: Extreme Programming Explained: Embrace Change. Addison-Wesley, Reading (2000)
Jeffries, R., Anderson, A., Hendrickson, C.: Extreme Programming Installed. Addison-Wesley, Reading (2001)
Author information
Authors and Affiliations
Editor information
Rights and permissions
Copyright information
© 2007 Springer Berlin Heidelberg
About this paper
Cite this paper
Ludlow, L. (2007). The Application of User Stories for Strategic Planning. In: Concas, G., Damiani, E., Scotto, M., Succi, G. (eds) Agile Processes in Software Engineering and Extreme Programming. XP 2007. Lecture Notes in Computer Science, vol 4536. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-73101-6_36
Download citation
DOI: https://doi.org/10.1007/978-3-540-73101-6_36
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-73100-9
Online ISBN: 978-3-540-73101-6
eBook Packages: Computer ScienceComputer Science (R0)