Chapter 23. User Story
To enact the User Story practice, you simply create an evocative document for requirements. A user story is a high-level description of the requirement to be built. It usually fits on a 3x5 index card and is a “promise for a conversation” later between the person carrying out the Customer Part of Team practice and the implementers.
Business Value
The User Story practice enables flexibility because a small fraction of time is originally invested to create user stories for the backlog. The team is then free to reprioritize them in response to new information or changes in the environment without wasting much work-in-progress. A user story forces a conversation to take place to flesh out the requirements; thus, there is less ...
Get Agile Adoption Patterns: A Roadmap to Organizational Success 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.
