The document discusses user stories and best practices for writing and reviewing them. It provides examples of a product canvas template that can be used to map out user stories, scenarios, workflows and other details. It also outlines attributes that user stories should have, such as being independent, negotiable, valuable, estimable, small and testable. Checklists are presented for reviewing user stories and defining requirements for a story to be ready. Patterns for splitting large user stories into smaller ones are also described.
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
0 ratings0% found this document useful (0 votes)
202 views
User Stories
The document discusses user stories and best practices for writing and reviewing them. It provides examples of a product canvas template that can be used to map out user stories, scenarios, workflows and other details. It also outlines attributes that user stories should have, such as being independent, negotiable, valuable, estimable, small and testable. Checklists are presented for reviewing user stories and defining requirements for a story to be ready. Patterns for splitting large user stories into smaller ones are also described.
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/ 20
User Stories
The untold details
By Ladislau Szilagyi www.euroQST.ro
The Product Canvas
Creating a product with a great user experience requires more than just user stories. While capturing the product functionality is important, the user journeys, the visual design, and the nonfunctional properties have to be described too. Stories should be complemented with other techniques including scenarios, storyboards, and design sketches. A Product Canvas is needed, containing: user stories, scenarios, workflows, storyboards, mockups, constraints, non-functional attributes 2
The Product Canvas
Here is an example:
The Product Canvas
Another example:
User Story Mapping
How to group Release Themes, Epics, User Stories
Reviewing user stories
A User Story should have the all of the INVEST attributes:
Independent Negotiable Valuable Estimable Small Testable 6
Checklist for User Story review
The story: As a (role), I want (to do or have something )
so that (I get this benefit) Whats in the scope: A list or statement of what everyone agrees will exist when this one story is done Whats out of the scope: A general statement or list of exclusions. Assumptions: About existing functionality or data access
Checklist for User Story review
Open questions and issues: Still to be resolved Design artifacts: At least one relevant sketch, screenshot, flowchart, design diagram Dependencies: What else should developers, testers and reviewers know to put this new story in context? What others stories must be complete before this one can go forward?
Checklist for User Story review
Acceptance tests: Gherkin syntax may be used: Given (the system's starting state) When (this action occurs) Then (the system delivers this result)
Testability issues: How easy to verify the acceptance
criteria? Personas: Any? 9
Definition of Ready
User Story defined
User Story Acceptance Criteria defined No testability issues User Story dependencies identified User Story sized by Delivery Team Scrum Team accepts User Experience artefacts Performance criteria identified, where appropriate Person who will accept the User Story is identified Team has a good idea what it will mean to Demo the User Story 10
Grooming the Product Backlog
11
Patterns for Splitting User Stories
12
Patterns for Splitting User Stories
Workflow steps Example: As a content manager, I can publish a news story to the corporate website. ...I can publish a news story directly to the corporate website. ...I can publish a news story with editor review. ...I can publish a news story with legal review. 13
Patterns for Splitting User Stories
Business rules variations Example: As a user, I can search for flights with flexible dates. ...as n days between x and y. ...as a weekend in December. ...as n days of x and y.
14
Patterns for Splitting User Stories
Major effort Example: As a user, I can pay for my flight with VISA, MasterCard, Diners Club, or American Express. ...I can pay with only one credit card type (of VISA, MC, DC, AMEX). ...I can pay with all four credit card types (VISA, MC, DC, AMEX).
15
Patterns for Splitting User Stories
Simple / Complex Example: As a user, I can search for flights between two destinations. ...specifying a max number of stops. ...including nearby airports. ...using flexible dates.
16
Patterns for Splitting User Stories
Variations in data Example: As a content manager, I can create news stories. ...in English. ...in Japanese. ...in Arabic.
17
Patterns for Splitting User Stories
Data entry methods Example: As a user, I can search for flights between two destinations. ...using simple date input. ...with a fancy calendar UI.
18
Patterns for Splitting User Stories
Defer performance Example: As a user, I can search for flights between two destinations. ...(slow - just get it done). ...(in under 5 seconds).
19
Patterns for Splitting User Stories
CRUD Example: As a user, I can manage my account. ...I can sign up for an account. ...I can edit my account settings. ...I can cancel my account.