Writing Effective User Stories

Basic Functionality

User Story

This is the sample template that we are widely using when it comes to user stories.Use the template when it is helpful, but don’t feel obliged to always apply it. Experiment with different ways to write your stories to understand what works best for you and your team.

Acceptance Criteria

Also as a PO or Proxy PO you need to make sure to write the acceptance criteria in order to accept the story. This is something very important and this will help your QA team a lot when they write test scenarios and test cases.

Definition of Done

Many organizations use this method in different ways. Some have DOD user story wise and some have DOD by release wise. It’s up to you to select the best method which suits your company but I prefer this using release wise rather story wise because ideally DOD cannot change story to story. But in a nutshell here you have to mention what are the important items to be completed before sending it for the UAT (User Acceptance Testing)or Customer demonstration.

User Story

As an online buyer
I want to use my credit card to purchase an item
So that I can immediately purchase my item from the web-store

Acceptance Criteria

· Accept Visa and Master cards

Definition of Done

· Unit test case completion 100%

Tips for writing effective and good user stories

A very well written user story will meet the criteria of Bill Wake’s INVEST acronym

Bill Wake’s INVEST acronym
  • Think from user perspective
  • Make your story Simple and Concise
  • Acceptance Criteria
  • Discuss your stories with the teams
  • Don’t hesitate to add NOTES
  • Keep the UIs aligned with user stories

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store