CREATING USER STORIES FOR TESTERS
Even though the product owner is responsible for managing the product backlog, anyone in the project can create user stories. That means that even testers can create them, which they can ideate from instances such as running into bugs or revising user stories during product backlog refinement.
Creating User Stories
When the Scrum team consults with the product owner and the customers what features should be developed for the software product, they break down and summarise the requirements into statements called “user stories.”
User stories are tools to describe features from the user’s point of view. They are high-level definitions of requirements that state who the user is, what the user wants, and what the benefit would be. A user story would often follow this format:
As a <state user here>, I want to <state action here> so that <state purpose or benefit here>.
A user story is meant to be short and simple, enough to fit on a note card or sticky note, and it should contain just enough information for the Scrum team to start working with. Let’s take a look at this user story:
US-001: As a new user, I want an easy registration process so that I can use the site as soon as possible.
It follows a user story template, but is it a good user story?
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: