A user story is a brief and concise description of a functionality or quality of a product or a service. It is informative and is written in spoken language.
How many times did we hear the client say: you implemented what was written, but this is not what I wanted? User stories focus on the value for the business. They invite the exploration of requirements by encouraging further discussions with stakeholders.
A user story is typically a sentence or two, each one containing 10 to 15 words, describing the need(s) of a user, their intended goal and any additional information required to understand the story.
A user story is not an untouchable list of needs. It is regularly modified, which makes it very common to use in agile methodology.
Why use User Stories?
Captures stakeholder needs and prioritize development of solutions
Provides a basis for estimating and planning solution delivery.
Allows generating user acceptance tests
Measures the delivery of value.
Traces and retraces requirements.
Creates a basis for additional analysis.
Assists project management and monitoring.
How to create a User Story
Who is accountable for writing user stories?
Read more by subscribing to the BA Toolkit
On top of the brief description of the method, access to:
- an explanation of when and how to use it,
- a practical example,
- tips and recommendations for use,
- downloadable checklists and templates,
- references for further reading,