Chapter 6. User Stories
They have been at a great feast of languages, and stol’n the scraps.
—Shakespeare, Love’s Labour’s Lost, Act 5, scene 1
Introduction
In Chapter 3, Agile Requirements for the Team, we introduced the concepts and relationships among the key artifacts—backlogs, user stories, tasks, and so on—used by agile teams to define, build, and test the system of interest. We noted that the user story is the workhorse of agile development, and it is the container that carries the value stream to the user. It also serves as a metaphor for our entire incremental value delivery approach, that is:
Define a user value story, implement and test it in a short iteration, demonstrate/and or deliver it to the user, repeat ...
Get Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
