User story templates
and examples.

User story templates
and examples.

User story templates
and examples.

Learn user story writing with the pre-made templates.

Learn user story writing with the pre-made templates.

Learn user story mapping
step by step

What are user stories

What are user stories

A user story is a short, simple description of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system. It typically follows a basic (user goal) format:


As a [type of user], I want [some goal] so that [benefit]


This format helps to keep the focus on what the user needs and why, rather than how the feature will be implemented. User stories are used in software development to help teams understand who the user is, what they need, and the value of the feature, guiding them in creating effective solutions.

A user story is a short, simple description of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system. It typically follows a basic (user goal) format:


As a [type of user], I want [some goal] so that [benefit]


This format helps to keep the focus on what the user needs and why, rather than how the feature will be implemented. User stories are used in software development to help teams understand who the user is, what they need, and the value of the feature, guiding them in creating effective solutions.

What you can learn from story map examples

What you can learn from story map examples

User stories are crucial in software development and project management, particularly in Agile methodologies. Here are some key functions they serve:


  1. Clarifying User Needs: User stories help the development team understand exactly what a user needs from the system, which helps to ensure that the end product is useful and relevant.

  2. Facilitating Communication: They provide a simple, clear language for describing features that all team members, regardless of technical expertise, can understand. This fosters better communication between developers, designers, product managers, and stakeholders.

  3. Guiding Development: User stories can guide the development process. They are often used to prioritize tasks, with the team focusing on delivering the most valuable features first.

  4. Encouraging User-Centric Design: By focusing on the user's perspective, user stories ensure that the design and development process remains user-centric rather than being driven by technology or assumptions.

  5. Improving Flexibility: User stories allow for changes and adaptations as more is learned about user needs and the system requirements during the development process.

  6. Facilitating Testing and Validation: User stories typically include acceptance criteria, which are conditions that the software must meet to be accepted by the user. This makes it easier to conduct testing and ensures the functionality meets user expectations.

  7. Serving as a Planning Tool: In Agile development, user stories are often used to estimate the effort required for various features, which helps in iteration planning and managing the project’s scope.

Overall, user stories are a foundational tool in Agile development that help teams to stay user-focused, manage complexity, and deliver value more effectively.

User stories are crucial in software development and project management, particularly in Agile methodologies. Here are some key functions they serve:


  1. Clarifying User Needs: User stories help the development team understand exactly what a user needs from the system, which helps to ensure that the end product is useful and relevant.

  2. Facilitating Communication: They provide a simple, clear language for describing features that all team members, regardless of technical expertise, can understand. This fosters better communication between developers, designers, product managers, and stakeholders.

  3. Guiding Development: User stories can guide the development process. They are often used to prioritize tasks, with the team focusing on delivering the most valuable features first.

  4. Encouraging User-Centric Design: By focusing on the user's perspective, user stories ensure that the design and development process remains user-centric rather than being driven by technology or assumptions.

  5. Improving Flexibility: User stories allow for changes and adaptations as more is learned about user needs and the system requirements during the development process.

  6. Facilitating Testing and Validation: User stories typically include acceptance criteria, which are conditions that the software must meet to be accepted by the user. This makes it easier to conduct testing and ensures the functionality meets user expectations.

  7. Serving as a Planning Tool: In Agile development, user stories are often used to estimate the effort required for various features, which helps in iteration planning and managing the project’s scope.

Overall, user stories are a foundational tool in Agile development that help teams to stay user-focused, manage complexity, and deliver value more effectively.

User story examples and templates

User story examples and templates

Explore three key user story formats: User Goal, Role-Based Requirement, and BDD Scenario, illustrated with a consistent example. This brief guide helps you choose the right format to clearly define user needs in agile and behavior-driven development projects.

Explore three key user story formats: User Goal, Role-Based Requirement, and BDD Scenario, illustrated with a consistent example. This brief guide helps you choose the right format to clearly define user needs in agile and behavior-driven development projects.

User Goal Format: "As a [user], I want to [action] so that [benefit]."

User Goal Format: "As a [user], I want to [action] so that [benefit]."

  • Structure: This format is straightforward and focuses on the user's perspective. It starts with identifying the user or their role, states what the user wants to do, and concludes with the reason behind this desire.

  • Focus: It emphasizes the user's need or desire and the benefit they expect to gain. This user-centered format makes it easier to understand who benefits from the feature and why it's crucial.

  • Use Case: This format is commonly used in agile development processes. It helps create features that directly address user needs, making it particularly useful for product teams aiming to maintain a user-focused approach in their development cycle.

  • Structure: This format is straightforward and focuses on the user's perspective. It starts with identifying the user or their role, states what the user wants to do, and concludes with the reason behind this desire.

  • Focus: It emphasizes the user's need or desire and the benefit they expect to gain. This user-centered format makes it easier to understand who benefits from the feature and why it's crucial.

  • Use Case: This format is commonly used in agile development processes. It helps create features that directly address user needs, making it particularly useful for product teams aiming to maintain a user-focused approach in their development cycle.

Example

Example

As a project manager, I want to add new tasks to the project so that I can keep the project plan up to date.

As a project manager, I want to add new tasks to the project so that I can keep the project plan up to date.

Role-Based Requirement Format: "In the role of [role], I need [requirement] to achieve [goal]."

Role-Based Requirement Format: "In the role of [role], I need [requirement] to achieve [goal]."

  • Structure: This format starts with a specific role, focuses on a specific need or requirement, and ends to be achieved. It's more specific about the user's role than the first format.

  • Focus: It highlights the necessity (requirement) that needs to be fulfilled to achieve a specific goal, putting less emphasis on the user's desire and more on the functional requirement and its purpose.

  • Use Case: This format suits situations where the user's role significantly influences the requirement. It's beneficial for developing features in professional or specialized domains where the user's role determines the needs and goals.

Example

Example

In the role of a project manager, I need the ability to input new tasks into the project to achieve an updated and accurate project schedule.

In the role of a project manager, I need the ability to input new tasks into the project to achieve an updated and accurate project schedule.

Behavior-Driven Development (BDD) Scenario Format: "Given [context], when [event/action], then [outcome]."

Behavior-Driven Development (BDD) Scenario Format: "Given [context], when [event/action], then [outcome]."

  • Structure: This is the structure of a behavior-driven development (BDD) scenario rather than a traditional user story. It sets a context (Given), describes an event or action (When), and defines the expected outcome (Then).

  • Focus: It focuses on the conditions and outcomes of specific actions, making it ideal for defining acceptance criteria and test cases. This format is more about how the system should behave under particular conditions than about user needs or goals.

  • Use Case: This format specifies software behavior primarily in behavior-driven development (BDD). It helps developers and testers create and run test scenarios that ensure the software behaves as expected in various situations.

Example

Example

Given I am logged in as a project manager, when I enter details for a new task and submit it, then the task should be added to the project plan.

Given I am logged in as a project manager, when I enter details for a new task and submit it, then the task should be added to the project plan.

In summary, the first two formats are variations of user stories that prioritize user needs and goals from slightly different perspectives, with the first being more general and the second more specific to user roles. The third format, however, is not a user story per se but a scenario definition used in BDD to specify system behavior. Each format serves a different purpose and is chosen based on the context of the development process and the project's specific needs.

Brainstorm user stories for your project

Free story mapping ebook

50 handpicked hints on

  • Discovering project goals

  • Mapping the user journey

  • Prioritizing user stories

NEW! AI bonus materials included

  • 100 user story map examples

  • Templates for specs

  • Useful articles

Free story mapping ebook

50 handpicked hints on

  • Discovering project goals

  • Mapping the user journey

  • Prioritizing user stories

NEW! AI bonus materials included

  • 100 user story map examples

  • Templates for specs

  • Useful articles

Join 1000+ organizations that
love StoriesOnBoard

Join 1000+ organizations
that love StoriesOnBoard

Business analysts, product owners, product managers, and teams of all shapes and sizes save time by planning products and enjoy efficient collaboration.

join StoriesOnBoard
join StoriesOnBoard
join StoriesOnBoard

Generate user stories &
build a backlog with AI assistance

StoriesOnBoard AI enables a new level of accuracy and speed in software planning and development.

Learn user story writing and story mapping with AI

  • Build an entire story map from just a few details

  • Understand the essence of the narrative flow, user goals, and user steps

  • Writing user stories, adoption criteria or release summaries is just a click away with ready-to-use AI recommendations

ai story mapping
ai story mapping
ai story mapping
user story writing with AI
user story writing with AI
user story writing with AI

Save time by writing user stories and more with AI

  • Craft a product backbone with goals, steps, user stories, and acceptance criteria in seconds

  • Improve ongoing projects by adding new perspectives and filling the gaps

  • Add acceptance criteria to each user story, and generate release summaries and announcements with a single click

Start story mapping today

Save time, and unlock the full potential of your software projects.

Start story mapping today

Save time, and unlock the full potential
of your software projects.

Start story mapping today

Save time, and unlock the full potential of your software projects.