Scribd
Upload
3 views

User Stories and Requirements

The document outlines the concept of user stories, which are essential for defining product requirements from the user's perspective. It details the structure of a user story, the roles of users, and the benefits of using user stories in the Scrum framework. Additionally, it discusses the management of user stories within the product backlog and provides examples of user stories along with their intended benefits.

Uploaded by

apheleledube94
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
3 views

User Stories and Requirements

The document outlines the concept of user stories, which are essential for defining product requirements from the user's perspective. It details the structure of a user story, the roles of users, and the benefits of using user stories in the Scrum framework. Additionally, it discusses the management of user stories within the product backlog and provides examples of user stories along with their intended benefits.

Uploaded by

apheleledube94
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 17

User Stories & Requirements

• A user story is a simple description of a product requirement in terms


of what that requirement must accomplish for whom.
User story needs to have, at a minimum, the following parts:
✓Title: <a name for the user story>
✓ As a <user or persona>
✓ I want to <take this action>
✓ So that <I get this benefit>
User

A user is the user of the system.


• a manager
• a clerk
• a developer
• a librarian
• an owner etc.
Benefit

Benefit is the value a user will get of the system.


• a manager can see the audit report in one click, which will save his
time.
• a clerk could search a report, which will save his time.
• a librarian could search a book by category, thorough which he/she
will improve customer service.
• an owner can order an equipment, which will save him from hassle.
User Story: Customer’s Cash Withdrawal

• As a Customer, I want to withdraw cash from an ATM, So that I don't


have to wait in line at the Bank
Acceptance Criterion 1:

Given that the account is creditworthy

• And the card is valid


• And the dispenser contains cash,
When the customer requests the cash

• Then ensure the account is debited


• And ensure cash is dispensed
• And ensure the card is returned.
Acceptance Criterion 2:

Given that the account is overdrawn

• And the card is valid


When the customer requests the cash

• Then ensure the rejection message is displayed


• And ensure cash is not dispensed
• And ensure the card is returned.
Writing User Stories

• Product Owner is responsible for the Product Backlog and thus for the
User Stories. However, it does not mean that only product owner
writes the user stories. Anyone in the Scrum Team can write the user
stories, and the activity can be spread across the project as
requirements get refined and new functionalities get added.
Managing User Stories
• User Stories are managed in the Product Backlog. The User Stories are ordered
according to priority. The most prioritized user stories are refined to granular
level, while the least priority user stories are kept at a lesser detail level. For
every sprint, the most prioritized and hence more granulated user stories are
taken into the sprint backlog. If a user story is to be added to the product
backlog, its priority is first determined, and it is placed according to its place as
per the priority. The user stories can be reprioritized at any time. It is also
possible to remove any of the user stories if required.
Benefits with User Stories
• The major benefit of User Story lies in the user centric definition itself. This is because,
ultimately, it is the user who will be using the product in the relevant user scenarios. It
connects the end users to the team members.

• The syntax of the User Story itself ensures to capture the goal or benefit or value that the
user wants to achieve.

• Since the acceptance criteria forms part of user story itself, it will be an added advantage to
the Scrum Team.

• It is possible to make changes to a user story in course of the execution of the project. If
the scope of the user story becomes large, it needs to be split into smaller user stories. The
conditions in the acceptance criterion can also be changed.

• As working product increments are delivered to the users at the end of each sprint, the
scrum team can get feedback from the users in sprint review meeting. This enables
incorporation of feedback into the product continuously.
Following are 25 sample user stories can you put the benefit of each
• 1. As an administrator I want to be able to create a new user to the team when needed.
• 2. As a lawyer I want to see all my active cases on the main screen.
• 3. As a student I want to see all of my old transcripts on the board.
• 4. As a driver I want my GPS voice activated.
• 5. As a researcher I want to see last few searches I made.
• 6. As a user I want the ability to restore my password.
• 7. As a cashier I want to see total amount in cash register displayed.
• 8. As a pilot I want to know the best flight height to fly in current conditions.
• 9. As a police officer I want to see the previous tickets given to a driver.
• 10. As a post man I want to know estimated time to deliver today’s mails.
• 11. As a guitarist I want to know speed of my fingers on the string.
• 12. As a grass mower I want mower avoid hitting blade to hard things
• 13. As a runner I want to be warned of irregular heart rate.
• 14. As a blind person I want to be warned for a hard thing coming on my way.
• 15. As a student I want to shuffle my flash cards.
• 16. As a credit card user I want to be warned if spent more than a set amount.
• 17. As a kid I want to turn off all the toys not active for a while.
• 18. As a driver I want to be warned of the tire pressure.
• 19. As a student I want to be reminded my class schedule every morning.
• 20. As a manager I want to do what if analysis while planning.
• 21. As a tester I want to see all the bugs assigned to me with status.
• 22. As a ticket booker I want to be notified as soon as a ticket gets available on a full flight.
• 23. As a writer I want my work get auto saved after every few seconds.
• 24. As a reader I want to see list of most sold books in last 2 weeks.
• 25. As a cook I want to see most visited recipes.

You might also like