User Stories Real Example. How to create user stories. Example of Acceptance Criteria and Definitions of Done

Agile product managers and product owners really need to be skilled in creating user stories. This real User Stories example is part of a project management course in which the creation of real User Stories is an important part of the training. Example of Acceptance Criteria and Definitions of Done are provided with maximum realism.

How to create real user stories. A real example

The following is a condition of the exercise:

Create 3 Real Product Backlog Items.

For your innovative machine, create two User Stories and one in a functionally descriptive format. 3 total items. Use your old task list from your project, or come up with a new, more realistic one.

You can create them for the machine body or the software part with the GUI of your choice. You may find it easier for the software part.

The condition is that all your user stories and all their content, attributes and sketches should be as realistic as possible and be able to serve for the actual development of functionalities.

You do not need to put your user stories in Jira or any other online tool or software.

Use a simple document. Arrange the attributes and all content transparently.

User Story 1: User registration

Size: 13

Priority: High

Component: User registration

Release: Release 1

Status: Upcoming

Attachment:

Acceptance criteria:

  • User need to provide a username (e-mail), first and last name with no more than 256 symbols
  • User need to provide a phone number with the format as +XX XXX XX XX XXX
  • User need to input his date of birth
  • Password can not be smaller than 8 symbols and maximum of 25 symbols with the following requirements:
    • Using minimum one Capital letter
    • Using minimum one small letter
    • Using minimum one Number
    • Using at least one Special symbols
  • User has to agree to the Terms and Conditions by checkbox before being able to submit the input, if not he is not able to submit the data
  • User is only able to submit and to open the page via secure encrypted URL by default
  • After submit user received an email with a unique confirmation link
  • Password and Repeat password has to be while the user provides input with *
  • User must provide input to the following:
    • Username/email
    • First and Last name
    • Date of birth
    • Password and 
    • Repeat password 

Definition of done:

  • Software is design within Security and Policy by Design principles and guides.
  • UAT tests are approved and tested.
  • Source code is uploaded into GitLab repository.
  • GUI is design following Responsive Design principles and Mobile test environment.
  • E-mail is sent to the user with a unique link to confirm that he is the owner of the email provided in the form.
  • QA Manager provides a sign-off that all the test results are positive – passed.
  • Product Manager provides a sign-off that all the features are properly implemented and tested.
  • DevOps team pushes – deploys the feature into the Production environment.

User Story 2: Activate Two-Factor Authentication (2FA)

Size: 8

Priority: High

Component: Security 

Release: Release 2

Status: Upcoming

Acceptance criteria:

  • To activate two-factor authentication user must provide a phone number
  • If the user provided a phone number during registration there should be only a button to activate 2FA from user settings.
  • If there is no user phone number provided during the registration process (as it is not a requirement) then the user will be asked to provide first phone number in format +XX XXX XX XX XXX.
  • After the user provided the phone number SMS is going to be sent with unique verification six numbers, validated only for 10 minutes, after the 10 minutes the number is not valid.
  • After activating the 2FA everytime when the user is login with username and password will receive a unique 6 digit number on his phone.

Definition of done:

  • Software is design within Security and Policy by Design principles and guides.
  • UAT tests are approved and tested.
  • Source code is uploaded into GitLab repository.
  • GUI is design following Responsive Design principles and Mobile test environment.
  • SMS is sent to the user with a unique link to confirm that he is the owner of the phone number.
  • QA Manager provides a sign-off that all the test results are positive – passed.
  • Product Manager provides a sign-off that all the features are properly implemented and tested.
  • DevOps team pushes – deploys the feature into the Production environment.

User Story 3: User registration – confirmation (functional format)

  • The platform has to be able to validate user profile, via email or SMS.
  • The platform is able to send SMS with 6 digit code to verify his identity via phone.
  • Generated code has to be unique and not be able to use it after 10 minutes time frame.
  • After successful verification of an SMS code (2FA) it has to be kept into the database for audit purpose, with username, phone number, timestamp, and IP address.  
  • Users should be able to receive SMS after 1 minute after clicking the activate 2FA function.
  • If the user provided his phone number during the registration process, then he should be able from the user setting to activate 2FA without provided his phone number, if not then he has to be able to provide an input of his phone number.

More Scrum and Agile-related resources

Product Backlog management

The product backlog is a popular term in product management and is considered as a list of…

Unfinished Product Backlog Items in Scrum and Agile teams

What happens to all of the Unfinished Product Backlog Items? Nobody asks this question but it is important. In most of my Scrum classes, there are students who…

How to manage support work in Scrum

Scrum is not that easy and different issues may arise. A recurring question I am often asked is…

Transparency in Scrum teams and Agile organizations

We will discuss the transparency in Scrum teams and Agile organizations. It is a very popular term in Scrum literature and modern Agile…

Scrum problems, causes of failure and mistakes

Scrum can cause problems and may lead to failure in some organizations. Common Scrum issues always have to do with…

Product Development workshop from the Lean guru Reinertsen

Lean Product Development is not just a product management practices following some processes. Last year I was fortunate enough to attend a…

The Agile 2020 Conference about Product management

The Agile 2020 Conference sessions are distributed into Tracks to help you find sessions about particular topics. Check on the tracklist. Then go to the…

Leave a comment

Your email address will not be published. Required fields are marked *