User Stories are a simple way of capturing user requirements throughout a project – an alternative to writing lengthy requirements specifications all up-front.
A User Story is a simple statement about what a user wants to do with a feature of the software, written from a user’s perspective.
User Stories should be written in business language that is understandable to all.
A User Story should focus on the who, what and why of a feature, not how.
As a [user role], I want to [goal], so I can [reason].
Product Backlog.
users will often tell storiesabout the failings of their current system or process.
Try capturing these stories as User Stories. On cards. While you’re in the meeting. As they are told.
In traditional development projects, these stories often aren’t captured as they are told, they’re captured in a lengthy analysis process and captured in a lengthy document; a format that isn’t particularly user friendly.