User Stories


WHAT ARE USER STORIES?

User stories are great to capture product functionality from the end users’ perspective. They clearly show what a specific user type can do with an application.
Each user story defines the following:
  • User type (for example: admin)
  • User’s intention
  • Value they get (from a specific functionality/feature)
User stories can be structured in the following ways:
  • Epic (contains more user stories; should be decomposed into smaller stories)
  • User stories
  • Smaller sub stories (more details about the stories)

WHY DO YOU HAVE TO CREATE USER STORIES?

Here are some reasons:
  • Clarifies software functionality
  • Easier to understand
  • Easier to remember
  • Easier to express business value
  • Makes product prioritization easier

PROCESS OF CREATING USER STORIES

1. VALIDATE USER NEEDS

The very first step you have to take is to clearly define the users who will use your product. It means you should create buyer personas (semi-fictional characters of your ideal users).
You need to be crystal clear what the problem your personas are facing and define the way your product will help them solve those issues. This is the foundation of your project, and you should be very thorough at this step; otherwise your whole project could easily go backward no matter how well your user stories are written.
Here is what you do:
  1. Conduct interviews with target users and understand their pain points related to your product’s focus. Here is a cool questionnaire guide that will help you ask the right questions during these interviews.
  2. It’s necessary to know what problems your target users are facing but you also have to make sure that the solution you provide actually solves that problem. These are just your early assumptions that need to be validated first.
Before writing any code, it’s highly recommended to create simple mockups that can be tested or reviewed by users. Just in case, here is a list of 20 easy-to-use mockup tools.
Prototypes are great to test your assumptions and help you get closer to building an app that provides real value.

3. WRITE USER STORIES FOCUSING ON USER TYPES (+ INVOLVE DEVELOPERS)

So, you know what user types will use your app and the epics are also identified. The next step is to get into the nitty-gritty details and break down what each epic means.
Here is the structure you should follow when writing user stories:
  • Who is the user?
  • What is his intention?
  • What value does he get from it?
This is a template you can use:
As a <user_type>, I want <his goal> so that <benefit, value>
Bill Wake, in his article from 2003, introduced a framework that helps everyone create good user stories. It’s called INVEST.
  • Independent: Each story should be independent (no overlapping) so it can be developed and delivered separately
  • Negotiable: Details will be clarified by the cooperation of the developers and customers
  • Valuable: It needs to be valuable for the users
  • Estimable: The story should be estimated. It doesn’t have to set exact time frame just a good estimate to schedule it in the project
  • Small: The stories need to be small enough to accurately estimate work it requires
  • Testable: It needs to be tested easily. Which also indicates that the requirements are well-defined.
In his blog, Roman Pichler suggests that you should add acceptance criteria to every user story describing the conditions that have to be met to consider a story done.
Definition of done is crucial for every project, in this blog post you can find some examples on how to define done in your project.

Tools for visualising user stories

You need to make sure that user stories are visible for every stakeholder of the project. To do so here are some cool tools you can use:
For structuring buyer personas, epics and user stories, here is a product canvas:
Product Canvas 2

Complement user stories with mockups

User stories are great to describe product functionality, but visual explanation is still missing from the picture. Adding mockups and sketches to user stories makes it even easier to understand the user journey and the core functionality.
Mockup creator tools
If you need more, check out our mockup tools collection.

4. DEFINE ACCEPTANCE CRITERIA FOR USER STORIES

Acceptance criteria define the boundaries of a user story, and are used to confirm when a story is completed and working as intended.Boost.co.nz
Acceptance criteria can be grouped into the following categories:
  • Functional Criteria: identifying user tasks, functions or business processes.
  • Non-functional Criteria: design and UI-related criteria.
  • Performance Criteria: criteria that are related to performance metrics such as loading time, response time.

Comments

Post a Comment

Popular posts from this blog

The Complete Guide to Vue.js User Authentication with Auth0

Image
  Learn how to secure a Vue.js application by implementing user authentication, which includes user login, logout, and sign-up, along with protecting Vue.js routes.   You'll enhance a starter Vue.js application to practice the following security concepts: Add user login and logout. Retrieve user information. Protect application routes. Call protected endpoints from an API. Look for the 🛠️️ emoji if you'd like to skim through the content while focusing on the build steps. This guide uses the Auth0 SPA SDK to secure Vue.js applications, which provides Vue.js developers with an easier way to  add user authentication to Vue.js applications using a Vue.js plugin.  The  Auth0 SPA SDK  provides a high-level API to handle a lot of authentication implementation details. You can now secure your Vue.js applications using security best practices while writing less code. This guide covers Vue.js 2. How does Auth0 work? With the help of Auth0,  you don't need to be...
Read more

Cloud Logging Strategies for Multi-Cloud Environments

Cloud logging enables you to centrally manage log data collected from multiple cloud resources. Log data is essential for measuring and optimizing cloud performance and security. However, it can be extremely difficult to effectively leverage log data from complex multi-cloud architectures. Often, simplicity and granular visibility are critical for ensuring efficient cloud logging. In this post, we’ll examine key components any multi-cloud logging strategy should account for, including tips for choosing tooling, determining structure, and creating logging processes.  What Is Cloud Logging? Cloud logging is a practice that enables you to collect and correlate log data from cloud applications, services, and infrastructure. It is performed to help identify issues, measure performance, and optimize configurations. Cloud logging relies on the creation of log files, collections of data that document events occurring in your systems. Log files can contain a wide variety of data, including ...
Read more

Azure Pipelines vs. GitHub Actions

Image
  I am a big fan of Azure Pipelines (and Azure DevOps). Being one for years. Azure Pipelines is a very mature and powerful tool. Azure DevOps/Pipelines was built with the enterprise in mind and it works really well for the enterprise world. It allows you to create workflows that automatically build, test, publish, release, and deploy code to provide end-to-end traceability of the software development lifecycle. . Then, out of the blue, Microsoft buys GitHub in 2018 and starts immediately expanding GitHub functionality. Over last two years, there have been so much innovation and improvement in GitHub functionality: advanced security, secret scanning, package management, codespaces, insights, dependabots, projects, innersource management, and of course, GitHub Actions. There is so much awesomeness to cover! But, let’s stay focused on GitHub Actions for now (and, perhaps, cover other items in future posts.) GitHub Actions is an excellent CICD tool to automate your software workflows t...
Read more