Using Storyotypes to Split Bloated XP Stories
An ideal XP project is composed of stories defined by the customer that are of the right size and focus to plan and manage according to XP principles and practices. A story that is too large creates a variety of problems: it might not fit into a single iteration; there are a large number of tasks that must be coordinated; it can be too large to test adequately at the story/functional level; too much non-essential functionality is bundled early in development causing essential functionality to be deferred. Teams new to XP find managing the size of stories especially challenging because they lack the experience required to simplify and breakdown large stories. This experience report describes four heuristics (storyotypes) we have used on our XP projects to successfully manage the size of stories.
Unable to display preview. Download preview PDF.
- 1.Beck, K.: Extreme Programming Explained: Embrace Change. Addison-Wesley, Reading (2000) ISBN 201-61641-6Google Scholar
- 2.Beck, K.: Martin Fowler, Planning Extreme Programming. Addison-Wesley, Reading (2001) ISBN 0-201-71091-9Google Scholar
- 3.Andrea, J.: Managing the Bootstrap Story in an XP Project .In: Proceedings of XP2001 (2001)Google Scholar
- 4.Cockburn, A.: Writing Effective Use Cases. Addison-Wesley, Reading (2001) ISBN 0-201- 70225-8Google Scholar
- 5.Poppendieck, M., Tom: Lean Software Development, An Agile Toolkit. Addison- Wesley, Reading (2003) ISBN 0-321-15078-3Google Scholar