discussion 3
docx
keyboard_arrow_up
School
Northeastern University *
*We aren’t endorsed by this school
Course
6810
Subject
Information Systems
Date
Dec 6, 2023
Type
docx
Pages
2
Uploaded by EarlFlagZebra29
Hello all,
A user story is a short explanation of the requirements of a user and how
these requirements can be met written in an easily understandable language
barring any technical information. In other words, a user story is the “who”,
“what”, and “why” of the requirement of a user (Rehkopf, n.d.).
There are five steps involved in creating a user story in Scrum:
Step 1: Outlining the acceptance criteria i.e. the set of requirements
to be met for a user story to be considered complete.
Step 2: Decide on a user persona. A User persona is basically a
representation of an Ideal customer which is created based on
extensive market research conducted by the marketing company
(Boogaard, 2011)
Step 3: Breaking down the user stories into tasks and subtasks
based on their complexity so that it is more manageable.
Step 4: Story mapping. It is used to add structure to your work like
putting the tasks in an ordered format.
Step 5: Feedback. Getting feedback from users and incorporating
the information you gained from doing so (
What is a User Story?
d.).
In order to make sure you are designing a process in the correct way it is
important to understand what your end goal is. Acceptance criteria gives a
clear-cut picture of what is to be expected from a user story. It also helps in
determining the definition of “done”.
User stories are the requirements of a user as defined by them. It mainly
focuses on the problems of the user and why such problem arises (Levison,
2019). The solution to that problem is not the main focus of a user story.
Acceptance criteria are a list of specific requirements that define the work to
be done on a user story. Each user story has different acceptance criteria
based on the problem and the solution to that problem (Levison, 2019). The
definition of “done” is a set of requirements that are supposed to be met by
the team while working on the project (Levison, 2019). Definition of “Done” is
not different for each user story. It usually includes factors like the quality of
work of the team and the completeness of a specific task (Levison, 2019).
References:
What is a User Story?
(n.d.). Wrike Agile Guide.
https://www.wrike.com/agile-
guide/user-stories-guide/
Links to an external site.
Boogaard, K. (2011, March 11). How To Create a Marketing
Persona.
Wrike.
https://www.wrike.com/blog/how-create-marketing-
persona/
Links to an external site.
.
Levison, M. (2019, December 10).
What Is Acceptance Criteria vs. Done vs.
User Stories
. Agile Pain Relief.
https://agilepainrelief.com/blog/definition-of-
done-user-stories-acceptance-criteria.html
Links to an external site.
Rehkopf, M. (n.d.).
User Stories | Examples and Template | Atlassian
.
Atlassian.
https://www.atlassian.com/agile/project-management/user-
stories
Links to an external site.
Regards
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help