How to Write Good User Stories Using [3 Key] Components

Sharing buttons:

hello guys welcome to yet another video

from prefect being a YouTube channel in

this video we're going to discuss how to

write a good user story we've already

cut the key components which makes a

good user story and later you're gonna

use a case study and write out a sample

user story so if you have a lot of lot

to cover so let's get started

there are three key components of a good

user story number one who what and why

who requires it what is required and why

is it required so this provides a

context for the user story the second

component is the acceptance criteria so

in order for a user story to be termed

as delivered the acceptance criteria

needs to be satisfied so this kind of

helps the development team and also the

testing team to work on their unit test

cases and the QA test cases and ensures

that the required functionality for a

particular user story is delivered

component number three supporting models

so these are supporting documents or

analysis models like screen mock-ups

process flow a screen a navigation flow

data models business rules so these are

some artifacts which are which can be

added to the user story which provides

more context and more background and

more information to the development team

and also to the testing team and this is

will really help if the team are not

sitting together and they are like

widely distributed and these three

components will really help the product

the project team to understand the

entire user story and help it to be

delivered correctly

okay let's start to look at a case study

and build out a sample use a story which

will help to understand this concept

better so James is a behaved who is

working with a client called vegan

Gardens so they're a restaurant and

they're looking for a mobile app which

will allow their customers to book a

table the features they are looking for

our registration login table booking

feature confirmation message once the

booking is confirmed and also to display

only the available time slots to the

customer so James is documenting these

features using user stories let's take

feature number five that is to display

the available time slots to the

customers and build a sample user story

using the three components which we just

discussed so let's start to look at a

user story example for the feature of

showing the time slots to the customer

only when a table is available so let's

build out the three components which we

just spoke of so the component number

one is who what and why and the template

which can help to frame this is it's a

commonly used template across it is azor

who I want what is required so that why

is required so this is a basic kind of a

template which can be used to capture

this information so let's let's see an

example for this so as a customer I want

to only see the time slots when a table

is available so that I can make my

reservations so basically this explains

that the customer using the mobile app

should only see the time slots when our

table is available so that they can make

the reservation if a time slot is not

available it's fully booked then it

should not be displayed to the customer

so that's what this user story kind of

tackles and this is what the

who and what and why is being set up so

let's look at the second part which is

acceptance criteria so the template

which can be used for this is given when

and then so this is a beer it's called a

behavior driven development approach

so this basically kind of documents the

acceptance criteria in the form of

scenarios so which gives clear-cut

understanding of what is required to the

both the dev one the testing team so

given is a context what are the

preconditions when an event event is

what what has happened and then

describes the outcome what should happen

in these conditions so let's look at an

example for this so given I'm I'm

registered and logged on to the vegan

garden mobile app then I select book a

table button and select the date and the

number of guests so that's the event

then I can only see the time slots when

a table is available

let's look at component number three of

the users history which is the

supporting models so as earlier spoke

about the more supporting models can be

screen mock-ups process Maps data models

business rules anything which can help

to support the user story with better

understanding and more context and

background which are required again it

should be relevant for the development

and also the IT teams the testing team

so let's look at a screen mock-up

navigation for this feature so an

example is the first box is the you know

just a mock-up of the Wigan Gardens

mobile app so this is it book at a a

book a table button so when the when a

customer clicks on it they are directed

to a screen call screen where they can

select the date and the number of guess

and once they select the data number of

guess and then they click the next

button they would be redirected to

another screen which shows the list of

time slots which are available so in

this example if you see we have shown

6:00 to 7:30 p.m. as one time slot and

then there is 9 to 10:30 p.m. as under

this time slot which can be selected

usually the I'd time slot is one and

half hours for this particular

restaurant so if you see here the time

slot from 7:30 to 9:00 p.m. is missing

because it's not available so we just

wanted to demonstrate how it will look

and this screen navigation flow can be

can can be attached as a supporting

model so that the development team and

also the testing team gets an idea okay

what is free you know it helps them to

better visualize what we have put in

words in component one and two

so that covers it I think we have

covered the three key components for

writing a good user story so in the next

whenever you are writing a user story

can refer this video and then you know

you can use it as a reference and start

writing out the user story so if you

enjoyed this video I would highly

recommend to go and subscribe to our

channel right now the reason I would ask

you to real subscribers we post a video

every week on business analysis

technique tools and interview

preparation and tutorials which will

help you to become a better ba so please

go out and subscribe to our channel and

click on the notification icon if you

have not already done so and so that you

can continue learning and become a

better ba until the next video

see ya