what is a user story in agile

User Stories in Scrum: The All-You-Need-to-Know Guide

The goal is clear: You want to develop a product that delivers a high added value to customers. You want to achieve a result with which team members and stakeholders are satisfied. But how do you do that? How can you meet all the requirements of a product in small, thorough steps? 

In agile, user stories have proven to be an efficient tool for this. They take you step by step from the first idea to a product ready for sale. I'll show you what user stories are, how to create them and how you can benefit from them. Well then, what is a user story in agile?

 

What is a user story in agile? Use case vs. user stories

The definition of user stories in agile describes the requirements for a product from the user's point of view. In other words: User stories tell you what features and functions a product should have. This makes them a key tool for discussing and validating user needs and working on their implementation with a common understanding. 

User stories provide a universal language that team members, stakeholders and customers understand and speak. In practice, this means you can use user stories to develop an understanding of the product the customer wants, leaving little room for misunderstanding. 

Several user stories together form a use case. That is the simple differentiation between use case vs. user stories. User stories and use cases have their origin in agile software development.

 

How are agile user stories structured (user story template)?

User stories describe the requirements and wishes for a project result to be created from the perspective of the customer. For this purpose, agile user stories have this elementary structure - you can use it as a user story template:

WHO (role), wants WHAT goal / wish WHY (Added value)?

Let's take a closer look at the individual components of user stories:

WHO (USER)

You fill the WHO placeholder with your customer or a typical representative of your target group. How detailed you describe the WHO in the agile user story depends on the user story itself and on the progress of the project. Therefore, be detailed enough to create a meaningful user story.

WHAT (FUNCTION)

Here you place the wishes of the user. You can ask yourself what the user expects or needs. If your product is still in an early development phase, you can formulate assumptions based on your experience as to what functions the user expects. If you already have a similar product on the market, you can also derive the desired functions from the feedback on this product.

WHY (ADDED VALUE)

This is maybe the most important part of the user story template. Only the added value shows why a function is important to the user. The WHY therefore allows you to honestly reflect on how well you know a customer's requirements. After all, including a requirement in a user story is easy - for example, because the customer expresses a desire for it. But only when you understand why the customer needs it, you do have the context for implementing the requirement. Only then you can question whether the customer's suggestion/request efficiently satisfies their actual need - or whether there might be a smarter way. Let's take a look at a user story example for this: 

The customer wants a rain cape for cycling. You could therefore now include the requirement "rain cape". Or you could ask the customer why he needs a rain cape. Let's say the customer answers "Because I don't want to get wet". 

That means you don't necessarily have to provide a rain cape. You could also supply a bike with an integrated roof. The important thing is that the customer's need or problem is solved with the user story – namely, not to get wet. The better you understand the “why”, the better you can design your user story.

Most Agile Coaches and Scrum Masters run in circles...

...fixing superficial symptoms. Time to use psychology to foster sustainable mindset change.

"Many team members are afraid to speak up!"

"We discover too many unexpected issues & bugs at a late stage!"

"Why does it sometimes take me hours to prepare a simple retrospective?"

What is a user story in agile (user story example)?

You now know the individual components of agile user stories. An agile user story example might look like this (yes, user stories can look very simple!): 

As a CUSTOMER I want A SECURE PASSWORD, SO THAT MY CUSTOMER DATA IS PROTECTED.

Here, the "CUSTOMER" is the user, "A SECURE PASSWORD " the function and "SO THAT MY CUSTOMER DATA IS PROTECTED " the added value. 

 

What is a user stories in Scrum?

When you work with user stories in Scrum, you add so-called acceptance criteria to them. Acceptance criteria describe the business requirements that user stories must meet at the time of acceptance. In other words: Acceptance criteria are the requirements you need for a user story to create value. (By the way, just to be sure: some people search for "what is a user stories" in Google. Obviously, user stories is plural and it should say "what are user stories" in that case.)

The meaning of agile user stories in the backlog can be more differentiated. Because in backlogs, user stories can not only describe requirements but also represent a specific hierarchy type. Thereby, there are these 3 hierarchy types:

Epics: Epics are broadly defined functional areas of a product whose concrete scope may still be unclear.

Features: Features are specific performance characteristics within an Epic.

Stories: Stories are technical agile user stories and user stories within a feature.

You can implement these hierarchy types within a sprint. They create a concrete benefit for the user. 

 

Writing user stories – How do I create convincing user stories?

In order to write helpful user stories in agile project management, detailed discussions with everyone involved are crucial. These should give you a thorough understanding of the target audience and the product to be created. You can then, for example, derive personas from this. 

In addition, the so-called INVEST criteria' help you to create a convincing user story:

Independent: A user story should be independent of other user stories. That means: The implementation of a story must not require that another story has been implemented beforehand. This has the advantage that you can freely prioritize user stories at any time or remove them from the backlog. 

Let's take another look at the bicycle example. Let's say you decided to install a small roof over the saddle of the bicycle instead of a rain cape, so that the customer doesn't get wet anymore. So that would be a user story. But now you realize that in order to install a roof, you first have to develop a more stable saddle to which the roof can be attached. That would be a different user story. Both stories build on each other. This is exactly what you should avoid.

Of course, it is sometimes unavoidable that you have to do one user story before another. But as a general rule, avoid user stories for which you first have to implement 20 other user stories.

Negotiable: Writing user stories can sometimes take a long time - which does not mean they are set in stone afterwards. Accordingly, Product Owner, stakeholders and developers should always discuss and specify a user story together. 

Valuable: The result of user stories in agile project management must have added value for the customer.

Estimable: A convincing user story enables the development team to estimate how much effort it will take to implement it.

Small: A user story should be so "small" that it can be implemented in a sprint.

Testable: User stories in Scrum should be testable. This is the only way to check whether they can really be implemented in practice.

 

This is how you benefit from user stories in agile

If you are not yet familiar with writing user stories in Agile, at first glance these might just look like additional work. However, user stories give teams an important context for their tasks and thus clarify the importance of each individual task.

Basically, this is how you benefit from user stories:

User focus: User stories are like a problem-oriented to-do list. Your team can use them to keep track of their tasks and know exactly how to meet user needs.

Holistic cooperation: User stories show everyone involved where they're going at a glance. This way, everyone can pull together and keep deciding how to add extra value to users. 

Creative solutions: User stories in agile software development produce creative results. Because they get teams to think critically about the best solution for the final product.

Constant successes: Each user story is a small challenge. Teams can therefore celebrate a small success after each story. This motivates throughout the entire development process.

 

Conclusion

I hope the question "what is a user story in agile" was answered to your satisfaction! User stories are an important tool in the work of agile teams. They show you again and again in detail for whom you are developing what and why. This not only helps you to create a high-quality product tailored to the target group, but also to keep the team motivated throughout the entire process. 

To be successful at this macro level of agile working, your organization as a whole needs to think and function in an agile way. To help you and your organization do this, we've worked with renowned experts to design Project Scagile It shows you in various webinars how to approach an agile transformation the right way. The training is free of charge. Feel free to take a look!

If you are searching for fun retrospective ideas, check out our post on 54 Kickass Retrospective Ideas for Agile Teams (including the Mario Kart Retro & the Team Morale Health Check).

At last, one of the most effective ways to sustainably develop the agile mindset of teams is implementing an agile health check. Our free team health check kit is there to help you implement it and ask the right questions. Just takes a minute to go through it 🙂

Share this article in your network

Need a team boost? Do this: The Spotify Health Check Retrospective!

First Health question: "😍 We love going to work, and have great fun working together."

Sounds good? Try our retro tool for free below.

More articles from our blog

Echometer Newsletter

Don't miss any updates on Echometer & get inspiration for agile working

FAQ about the online retrospective tool

No, you do not need to log in to Echometer or register to test the Retro Board and Retro Tool in Echometer.

You can try out Echometer's Retro Board via the following link without logging in: Try a Practice Round

First, simply register for free in Echometer. Then navigate to the workspace for which you would like to purchase the retro tool. If you haven't already done so, you can do so here: Create account in Echometer 1:1 tool

You can then manage your subscription (for both the retro tool and the 1:1 software) within the workspace settings.

You can choose from various payment methods when upgrading.

If you do not have access to your company's credit card yourself, you can simply add a buyer as a workspace admin in your Echometer workspace so that this admin can carry out the upgrade for you.

In Echometer there are two separate software solutions that are available within each workspace in Echometer:

  • 1:1 tool: Software for planning and conducting 1:1 meetings and tracking employee development
  • Retrospective tool: Software for planning and moderating retrospectives and tracking team development through team health checks

Both are independent software solutions, so they can be used separately from each other.

However, they work according to the same principles and aim to achieve the same added value: The continuous improvement of agile teams. In this respect, the simultaneous use of both software solutions is recommended.

Yes, you can assign administration rights to any number of users at both team level and workspace level. Please note the following:

  • Only workspace admins can take out and manage a Echometer subscription for a Echometer workspace.
  • Only workspace admins can create additional teams and name or remove additional workspace admins.
  • Team admins can appoint and remove additional team admins and team members for their team

If an agile team does not yet have much experience with retrospectives, a tool that effectively guides you through the retrospective and offers many templates is recommended:

  • Echometer is known not only for being an intuitive online retro board, but also for offering a very effective guided flow through the retrospective. At the same time, Echometer offers whiteboards that can be flexibly integrated into the retrospective. This makes Echometer very beginner-friendly.
  • Echometer also has extremely versatile and creative templates for retrospectives and team Health Checks that stimulate team reflection. Inexperienced teams in particular are very grateful for the food for thought in Echometer.

This makes Echometer the best software recommendation for beginners with agile retrospectives or Scrum beginners. By the way, you can try out Echometer for free without logging in: Echometer Try out the retro tool

Yes, you can collect and measure the eNPS (Employee Net Promoter Score) in Echometer's Health Checks and surveys for retrospectives.

The eNPS can be evaluated in Echometer both at team level and across teams. For example, you can use the heat map in the Workspace Health Dashboard for cross-team evaluation.

The Echometer Retrospective software is designed to guide teams through the retrospective process with maximum ease and effectiveness, following best practices.

The steps and their sequence can be customized using the navigation within the retro. By default, a retrospective in Echometer is structured in this way:

  • Icebreaker
  • Review of open measures from past retros
  • Collect feedback (first Health Checks, then open questions)
  • Prioritization of feedback
  • Deriving action items
  • Conclusion of the retrospective with the "ROTI score" (Return on Time Invested)

Additional whiteboards (e.g. for workshops, for analyzing problems or for brainstorming measures) can also be added spontaneously at any point using the Retrospective navigation.

Yes, the Echometer Retrospective Tool offers various export options for retrospectives.

The most popular method is to generate a PDF that contains the feedback, the votes from the prioritization and the measures of the retrospective. It is also possible to share the retrospective via a sharing link.

A summary of the retrospective is also automatically sent to other participants by email after the retrospective, provided they are registered as team members in the team.

Yes, the online retrospective tool Echometer is one of the few retrospective software tools that also optimally supports the recording and tracking of measures:

  • Integration: You can also record measures directly in Jira via an integration.
  • Automatic follow-up: All open measures from past retros appear automatically in the measure review of the next retrospective for tracking purposes. This gives the team an overview of which measures are currently still open and creates a commitment to implementing the agreed measures.
  • Reminders: Measures are assigned to a person responsible, who automatically receives a reminder email when the measure is created so that the measure is not forgotten. In addition, each participant can flexibly receive action reminders via email and manage the action status at any time in the Echometer Retro Tool.

This means that Echometer's tool for team retrospectives has extensive and well thought-out functions for action tracking.

Yes, Echometer allows grouping and prioritizing (voting on points) of feedback on the Retrospective Board.

All participants can simply drag and drop cards onto each other and group them together.

There are 2 modes for prioritizing:

  • In "Live Voting" (the recommended mode), the moderator selects how many votes each participant should have and then starts the hidden voting. As soon as all votes have been cast, the moderator can close the live voting. During the voting, you can see how many votes are still to be awarded. After the voting is closed, the cards in the columns are automatically sorted in descending order so that the cards with the most votes are at the top.
  • In "Facilitated Voting" mode, the moderator simply selects how many votes are allocated to each topic. This mode is only necessary in exceptional cases.

Feedback can be optimally processed in the team using Echometer and the measures derived from it can also be easily recorded in Echometer in direct connection with the feedback.

Yes, with the online retrospective software Echometer you can collect asynchronous feedback on the retrospective in advance via a survey.

This means that obtaining feedback is asynchronous and you can make the most of the time spent together in retrospect.

Yes, absolutely: The online retrospective software Echometer is optimized for distributed teams working remotely and includes various options for interacting with each other in real time.

Both the retrospectives and the whiteboards are synchronized in real time for all participants and you can also optionally display your colleagues' cursors.

Yes, the online retrospective tool Echometer is a free tool that you can try out without logging in.

You can get started right away using this link: Echometer Retro Tool without login.

To invite other participants to your online retrospective in Echometer, you will need to register. Participants only need to enter their email address to join the retrospective, but do not need to log in.

After the retrospective, participants can optionally log in to access the summary even after the retrospective has ended.

Yes, Echometer offers many high-quality templates for retrospectives and the respective steps of a retrospective.

Echometer is the retrospective software tool with probably the most integrated retrospective template ideas and patterns:

  • The retro templates in Echometer contain sample questions for the retro board. These are often creatively based on specific topics in –, such as the "Kart racing retrospective" or the "Time travel retrospective".
  • Some retro templates also contain templates for Health Checks. For example, to measure the Spotify Health Check or psychological safety in the team.
  • When creating a team, you can choose from various team templates for management teams or scrum teams, for example. The team templates then put together a suitable team Health Check for the team.
  • For icebreakers in the retrospective, Echometer has over 50 ideas for sample questions that can be used spontaneously and randomly in a retrospective via a random generator.
  • And then there are whiteboard templates in Echometer, which contain ideas for check-ins, team building and the development of measures.

One of the greatest strengths of the Echometer Retro Tool are the various templates for retrospectives, which can be used as patterns for the creative design of your own retrospectives.

Here is a short list of the samples as an insight into the retrospective templates:

  • Happy, Wondering, Sad
  • Three Little Pigs
  • Team Morale Health Check
  • Easter and Christmas retrospective templates
  • DORA Retrospective
  • 5 agile values Health Check
  • Spotify Squad Health Check Radar
  • Psychological safety Health Check
  • DORA Retrospective
  • Unique retrospective templates such as the "7 Dwarfs Retrospective" or the "Football Retrospective"

If you are interested in the Retrospective Tools templates, take a quick look at the tool: Echometer Retro Templates & Templates

Yes, Echometer is an online tool for retrospectives that offers Jira integration.

With the Jira integration in Echometer, measures from Echometer can be created in Jira boards with a single click.

This makes Echometer a good retrospective software tool if your team is already using Jira.

Echometer is not available in the Atlassian Marketplace, but as separate software via my.echometerapp.com callable.

Yes, Echometer can be called a starfish retrospective tool, because with Echometer you can easily perform the starfish retrospective on an interactive online retrospective board.

Hot tip: If you are interested in the Starfish Retrospective, take a quick look at Echometer. Because the special thing about Echometer is that you can try out the starfish retrospective immediately (time-saving, without logging in) at this link: Echometer Starfish Retrospective Access without login

The Echometer Sprint Retrospective software has very extensive features, both for beginners and experts. The following features form the core of the tool:

  • Structured retrospective flow with integrated whiteboards for flexible brainstorming on individual focus topics
  • Retrospective board for brainstorming, presenting, grouping and voting with live collaboration
  • Moderator tools such as a timer, anonymity settings and control over the agenda step (focused for all participants)
  • Integrated tracking of measures from past retrospectives with automatic resubmission and incl. Jira integration
  • Unbiased brainstorming: Concealed cards on the retro board as well as on the integrated whiteboards prevent participants from influencing each other during the brainstorming session.
  • Simple, quick setup of the tool: Many users report that they were able to start their first retrospective in less than 10 minutes.

The following features are Echometer's unique selling points that are relevant for experienced Scrum Masters and team leaders:

  • Dashboard with retrospective history, including duration of the retrospective, number of participants and ROTI score
  • PDF and Markdown export of the retrospective after completion
  • The retrospective can take place asynchronously (e.g. also via a survey that is sent out before the retro) or in real time
  • Anonymous feedback via survey or on the Retrospective Board
  • Anonymous voting and prioritization of feedback on the retrospective board by awarding points
  • Query or measurement of the "ROTI score" (i.e. Return on Time Invested) after the retrospective for continuous evaluation and improvement of the retrospective by team members
  • Creation of Health Check surveys or pulse surveys as a happiness check and mood barometer in order to recognize trends (e.g. increasing dissatisfaction) in the team at an early stage
  • Health Check KPIs and agile metrics in the analysis dashboard including history
  • Health Check Surveys or pulse surveys also possible across teams

The Echometer Retrospective Tool offers the following features for retrospective template ideas, questions and samples:

  • 50+ Retrospective Template Ideas including Keep Stop Start, Happy Wondering Sad and the Starfish Retrospective
  • 200+ Retrospective Health Check questions and templates
  • Retrospective Icebreaker Library with 50+ fun retrospective check-ins to promote psychological safety and team spirit etc.
  • Whiteboard templates for visual, interactive retrospective icebreakers (including seasonal highlights for e.g. Easter and Christmas)
  • Whiteboard templates to structure and facilitate the creation of measures

Yes, the retrospective software tool Echometer is easy to use even for beginners who are not yet familiar with retrospectives.

Many users report that they were able to carry out their first retrospective in Echometer in less than 10 minutes of preparation!

Thanks to the structured process in Echometer, carrying out the retrospective is also very easy.

On the testimonial page of Echometer you will find numerous confirmed user reviews: Echometer Testimonials

Echometer is the best software tool for retrospectives compared to alternative retrospective software tools such as Retrium, EasyRetro, Reetro, Neetro and TeamRetro for three reasons:

  1. Large selection of creative templates for retrospectives: Users of Echometer confirm that Echometer has a uniquely wide range of retro board ideas.
  2. Echometer has a simple and intuitive structure for retrospectives that guides teams through retrospectives using best practices. This also makes Echometer very beginner-friendly.
  3. Echometer offers a generous free version.

Users of Echometer particularly appreciate the unique function of Echometer to insert Health Checks into their agile retrospectives: These agile Health Checks make a massive contribution to stimulating team reflection and actively involving every team member in the retrospective.

To summarize, even alternative retrospective software tools such as Parabol do not have the unique features of the Echometer retrospective tool, which are both simple and effective. Therefore, it can be said that Echometer is the best software app for conducting agile sprint retrospective meetings.

Yes, in Echometer you can get anonymous feedback from the team.

Echometer is one of the few online retrospective tools that can be used to collect feedback anonymously.

In Echometer, feedback can even be collected anonymously before the retrospective via asynchronous surveys, which is unique among online retrospective tools and distinguishes Echometer positively from tools such as the retrospective software Parabol.

Yes, Echometer offers a generous free version of the online retro tool that can be used permanently free of charge for one team. This includes all functions for team retrospectives.

You only have to switch to a paid version for additional functions such as SSO, multiple teams or an unlimited number of retrospectives.

Further information on the variants of Echometer's retro tool can be found on the pricing page here: Retro-Tool Price List

The greatest strengths of the Echometer retrospective tool are its impact on time savings, participant engagement and productivity.

  • With hundreds of ideas for retrospective templates in combination with the integrated surveys, Echometer makes it very easy to prepare great retrospectives in just a few minutes.
  • Thanks to the guided steps and the playful and interactive retrospective board, implementation is child's play, focused and results-oriented at the same time.
  • The integrated tracking of measures and team health makes it easier to recognize trends in the team at an early stage and ensure that measures from retrospectives are not forgotten

Combined with the unique features of the agile Health Checks and flexible whiteboards, Echometer is one of the best, if not the best, retrospective tool on the market, even better than the better-known Parabol retrospective tool.

Yes, Echometer's retro tool is technically secure and GDPR-compliant.

Several European financial institutions and insurance companies have chosen to purchase Echometer's retrospective tools over other alternatives due to strict regulatory requirements.

The data is stored and securely processed in Germany. The contract for commissioned data processing with details on the technical and organizational security measures of Echometer's processing can be viewed here: https://echometerapp.com/gdpr-and-security/

Echometer's tool for retrospectives offers the following integrations:

  • Jira (for easy tracking of measures from retrospectives in Jira boards)
  • Google login
  • SSO (only in paid version)

Echometer are particularly positive about the increase in the effectiveness of retrospectives and the improved measurability of team development through Echometer.

Here are some officially confirmed quotes from users and customers of the Echometer software tool, all of whom hold leadership positions in agile teams:

Duane Hill, Scrum Master Coach:

  • "Echometer is like a combination of Miro and a really smart retro board. It even provides metrics on the effectiveness of my coaching so I can easily spot trends in team development. I really love this tool – highly recommended for anyone who wants to make their retrospectives more effective!"

Lena Tölke, Agile Coach at Deutsche Bahn Sales:

  • "Thanks to the targeted questions in Echometer, we keep coming up with new insights for our further development in retrospectives and can make these transparent and measurable for all team members."

Clemens Schöne, Scrum Master at Communardo Products:

  • "Echometer is like the combination of Mural and EasyRetro – I am thrilled! With Echometer, remote retros can work much better and even be fun!"

Patrick Böttcher-Exner, management position at Relaxdays GmbH:

  • "One major advantage is that Echometer allows us to carry out and track both remote and on-site retrospectives in one tool."

Carina McLane, Senior Software Developer at Volvo:

  • "As a Scrum Master, it's not about the tools, but this one really makes the work a lot more enjoyable. After two years of experience with Echometer, I can recommend it to anyone who wants to enrich their retrospectives and understand their team better!"

Echometer is the perfect retrospective software tool for busy team managers, team leaders, engineering managers, but also scrum masters and Agile coaches in distributed or hybrid agile teams ("remote teams").

Users particularly appreciate how much time the tool saves for retrospective moderators and how it increases the engagement of participants in the retrospective. Therefore, people who value time savings, retrospective effectiveness and engagement benefit most from the functions of Echometer.

In addition, Echometer offers an easy, playful introduction to retrospectives and is therefore particularly suitable for teams that do not yet have much experience with retrospectives or are just starting out with agile working methods.

The Echometer retrospective software works as follows:

  • Simple preparation of retrospectives using templates for retro formats, surveys and whiteboards
  • Intuitive and step-by-step implementation of retrospectives. Possible both online and on-site. Simply use the QR code on site so that participants can take part via their smartphone with the Mobile Companion app.
  • Automatic follow-up through export functions and integrated tracking of developments and measures including retro archive.

The implementation of a retrospective in Echometer is as follows:

  • The retrospective board allows the agile team to start with a fun welcome screen where they can wait for the rest of the team while playing an interactive game.
  • Once all participants of the retrospective have arrived, continue with an icebreaker question. Echometer has several icebreaker question templates, including both open-ended questions and visual whiteboard templates with workshops and small games.
  • After the icebreaker, you reach the screen for tracking measures: Here, the team reviews the open actions from past retrospectives and decides whether to keep, close or discard the actions. This step is unique to Echometer and significantly improves the quality of the continuous improvement process of agile teams.
  • Then it's on to Team Health Check: all team members answer various questions, for example a question about satisfaction in the team or questions about psychological safety. This type of question increases engagement in the retrospective, even with introverted team members, as well as the creation of agile KPIs to track the mood in the team over time.
  • Then you continue with the retrospective board, where everyone can leave anonymous feedback on open questions – if this has not already been done in advance via a survey. There are hundreds of retrospective templates for different retrospectives on the Echometer retrospective board.
  • Feedback is first written face down on the retro board so that the participants do not influence each other. The moderator can then reveal the feedback column by column.
  • Once the feedback on the retro board has been uncovered, presented to the team and any queries about feedback have been clarified, the prioritization, i.e. the voting, can continue.
  • Voting in Echometer is anonymous. During the voting process, you can see how many votes have already been cast and how many are still open.
  • At on-site retrospectives, you can also vote using your smartphone.
  • As soon as the voting is complete, you can derive measures. To do this, you can either create a measure directly for the feedback or open the feedback on a new whiteboard to analyze the problem in more detail and brainstorm ideas for measures.
  • The brainstorming of measures on a separate whiteboard within the retro is a point of differentiation for Echometer compared to other tools for retrospectives such as Parabol. In Echometer, you can create a separate whiteboard for each topic within the retro and thus optimally control the focus of the discussion.
  • Finally, Echometer enables the retrospective to be concluded by anonymously asking the entire team about the ROTI score on a scale of 0 to 10 (i.e. the "Return on Time Invested"): This helps the team and in particular the retrospective moderator to continuously improve the quality of the retrospectives within the team itself.

Given this unique, structured and flexible retrospective process, combined with the range of functions, Echometer is often described as the best tool for agile retrospectives.

Further questions?