User story slicing

User story slicing

May 2, 2023

By: Ankit Tandon 1

What is a user story? May 2, 2023

2

What is a user story?May 2, 2023

3

User stories are short, simple descriptions of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system

User stories are part of an agile approach that helps shift the focus from writing about requirements to talking about them. All agile user stories include a written sentence or two and, more importantly, a series of conversations about the desired functionality – Mike Cohn

Shared documents are not shared understanding May 2, 2023

4

Customer: Hi, I’ll like to order a cake

Employee: Sure. What would you like to be written on it?

Customer: Please write ‘So Long, Alicia’ in purple

Employee: Sure

Customer: And put stars around it

Employee: No problem. Will send across

So here is the cake.. May 2, 2023

5

Another one.. May 2, 2023

6

User Story examples

May 2, 20237

As an ABC bank customer I want an ability to view past transactions so that I can track my finances

As an Agile enthusiast I want to learn user story slicing so that I can slice user stories better

INVEST

May 2, 20238

Activity Time

May 2, 20239

Write stories for the following:

Problem Statement: Buy an air ticket onlineGroup into 3-5 peopleFollow INVEST principleFormat: As a _ I want to _ so that _

Why Slicing is important?

May 2, 202310

-Large stories are harder to estimate-Reduces risk-Makes prioritization easier-Improves flow-Reduces waste-Small wins boosts team’s confidence

And, last but not the least- Your job is to change the world

Slicing Metaphor

May 2, 202311

Slicing Metaphor

May 2, 202312

Vertical Slicing

May 2, 202313

Horizontal Slicing

May 2, 202314

Vertical Slicing techniques

May 2, 202315

Activity

May 2, 202316

Problem Statement: e – commerce portal : Make payment

Story: As a buyer I want to make payment for the goods added in shopping cart so that I receive my products

Technique 1 – By workflow

May 2, 202317

As customer I want to log in with my account so I don't have to re-enter my personal information every time;

As customer I want to review and confirm my order, so I can correct mistakes before I pay;

As customer I want to pay for my order by COD, so that I can confirm my order;

As customer I want to pay for my order with credit card, so that I can confirm my order;

As customer I want to receive a confirmation e-mail with my order, so I have proof of my purchase;

Technique 2 – By Business Rules

May 2, 202318

As a seller I want to charge for same day delivery because faster delivery costs significantly more

As a seller I want to decline customers from outside India, because the shipping expenses make these orders unprofitable;

As a seller I want to update ordered products from stock so other customers see a realistic stock

As a product manager I want only a valid discount coupon to process so that I can offer right discount for the right product

Technique 3 – By Platform

May 2, 202319

As a buyer I want to make payment for the goods added in shopping cart on desktop so that I receive my products

As a buyer I want to make payment for the goods added in shopping cart on tablet so that I receive my products

As a buyer I want to make payment for the goods added in shopping cart on mobile so that I receive my products

Activity Time

May 2, 2023

http://www.slideshare.net/nashjain/techniques-for-effectively-slicing-user-stories-by-naresh-jain

20



Technique 4 – By Roles and Operations(CRUD)

May 2, 2023


21



Lets try to decompose it

May 2, 202322

Business POV

-Add new role-Delete existing role-Copy existing role-Search roles-Update permissions

Technical POV

-Left and Right pane-Client side search-Tree structure for permissions-CRUD services for roles-Read and Update services for permissions

Slice 1

May 2, 202323

Read Only View of Roles and Permissions

-Left & Right pane-Display permissions in a table-Read service for roles-Read service for permissions




Slice 2

May 2, 202324

Ability to update permissions

-Tree structure for permissions-Update service for permissions




Slice 3

May 2, 202325

Add new roles

-Copy functionality in UI -Create services for roles




Slice 4

May 2, 202326

Delete existing roles-Delete functionality in UI-Delete services for roles

Client side search functionality




Evolution

May 2, 202327

Evolution May 2, 202328

Activity

May 2, 202329

Problem Statement: E – commerce portal : Search for products

Story: As a buyer I want to search for products so that I can view and order them

Technique 5 – By Data type

May 2, 202330

As customer I can search for a product by its product number, so I can quickly find a product that I already know;

As customer I can search for products in a price range, so that the search results are more relevant;

As customer I can search for products by their color, so that the search results are more relevant;

As customer I can search for products in a product group, so that the search results are more relevant

Activity

May 2, 202331

Problem statement: Contact dormant customer by email

Technique 6 – By Technical Tasks (Hamburger)

May 2, 2023

https://gojko.net/

32

Identify tasks


May 2, 2023

https://gojko.net/

33

Identify option for tasks


May 2, 2023

https://gojko.net/

34

Trim the burger


May 2, 2023

https://gojko.net/

35

Take the first bite

Other slicing techniques

May 2, 202336

Happy / Unhappy path Acceptance criteria Now vs Later Spike

Evaluate your slice

May 2, 2023

http://agileforall.com/

37

Is each story 1/10 to 1/6 of your velocity

Does it satisfy INVEST criteria

Is there a scope of de –prioritization or deletion

Any obvious story to start with that gets early value, learning, mitigates risk etc

Good to go. There may be other better techniques though

Try some other slicing

technique

Slicing cheat sheet

May 2, 202338

User Story slicing cheat sheet

Can we slice this user story vertically on..

1. Workflow Steps? What steps does a user perform? Are all steps necessary (right now)? Can steps be simplified?

2. Business Rules? What business rules apply to this story? Are all rules necessary? Can simpler rules suffice?

3. Operations? What operations does the story need? Are all operations (CRUD-create, read, update, delete) necessary now ?

4. Roles? What are the required roles? Are all necessary now?

5. Datatypes and Parameters? What datatypes are supported (different search options)? What parameters are needed?

6. Platform? Which platforms are supported? Are all platforms needed (right now)? Are some platforms harder to implement?

7. Happy / Unhappy flow? What are different Happy / Unhappy flows? Are all unhappy flows needed (right now)?

8. Optimize now vs Optimize later? What are the required optimizations? Are all optimizations needed (right now)?

9. Technical Tasks? Thinking more along technical tasks than user stories? Are all technical tasks needed (right now)? Are there any low value / high effort tasks that can be delayed?

10. Spike? Still not sure about how to slice the story? Write a spike

May 2, 202339

References..

May 2, 202340

https://gojko.net/2012/01/23/splitting-user-stories-the-hamburger-method/


http://blog.agilistic.nl/8-useful-strategies-for-splitting-large-user-stories-and-a-cheatsheet

Jeff Paton – User Story Mapping







User story slicing

Software

Transcript of User story slicing