What is User Stories?

Blog > Business Analysis

What Is User Stories?


A user story is a brief explanation of functionality or quality that is required to provide value to a specific stakeholder.


User stories capture a specific stakeholder's demands and allow teams to design features that are important to that stakeholder using short, basic documentation. They can be used to identify needs and aid in the prioritization, estimation, and planning of solutions. A user story is often a phrase or two that outlines who has the need addressed by the story, the goal the user is attempting to achieve, and any extra information that is necessary to comprehend the scope of the story. User stories encourage exploration of requirements by encouraging extra dialogues with stakeholders and grouping functional requirements for delivery, with an emphasis on stakeholder value.

User stories can be used:

• to capture stakeholder needs and prioritize development of solutions,

• as a basis of estimating and planning solution delivery,

• as a basis for generating user acceptance tests,

• as a metric for measuring the delivery of value,

• as a unit for tracing related requirements,

• as a basis for additional analysis, and

• as a unit of project management and reporting.


1 Title (optional): The story's title refers to a task that the stakeholder wants to complete with the system.

2 Statement of Value: User stories do not have to be structured in any particular way. Three elements constitute the most preferred format.:

•Who: a user role or persona.

•What: a necessary action, behavior, feature, or quality.

•Why: the benefit or value received by the user when the story is implemented.

For example, "As a , I need to , so that ." "Given...When...Then" is another common format.

3 Conversation: User stories assist teams in exploring and comprehending the story's features and the value it will provide to the stakeholder. The tale does not contain everything there is to know about the stakeholder demand, and when the story is provided, the knowledge in the story is augmented by further modeling.

4 Acceptance Criteria: The development of specific acceptance criteria can help support a user story. Acceptance criteria define a user story's bounds and assist the team in determining what the solution must provide in order to deliver value to the stakeholders. Other analysis models may be used to supplement acceptance criteria as needed.


Usage Considerations

1 Strengths:

• Easily understandable by stakeholders.

• Can be developed through a variety of elicitation techniques.

• Focuses on value to stakeholders.

• A shared understanding of the business domain is enhanced through collaboration on defining and exploring user stories.

• Tied to small, implementable, and testable slices of functionality, which facilitates rapid delivery and frequent customer feedback.

2 Limitations: In general, user stories are meant to be used for short-term demand capture and prioritizing, not for long-term knowledge retention or comprehensive analysis. Fail to comply this principle can result in the following problems:

• Because the team does not have all of the answers and comprehensive specs upfront, this conversational method can be challenging.

• Requires context and visibility; if tales aren't traced back through validation or augmented with the higher-level analysis and visual artifacts, the team may lose sight of the overall picture.

• It's possible that there won't be enough documentation to meet governance requirements, a baseline for future work, or stakeholder expectations. It's possible that more documents will be required.



BABOK Guide(p.359-361)