Story in the Slaughterhouse (Seacon 2012)

Story in the SlaughterhouseEpics und große User Stories sauber filetieren

Sven RöpstorffSEACON 2012

Hamburg, 05.06.2012

What Are User Stories Actually?

What Are User Stories Actually?

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.

-- Mike Cohn

Card Conversation Confirmation

Triple-C

Card

As who I want what so that why

Conversation

Confirmation

Acceptance Criteria

INVEST in good User Stories

Splitting Patterns

Imagine ...

... a mobile app as a conference guide

Split vertically

Split by Workflow

Split by Workflow

As a participant I would like to rate sessions I visited to give feedback to the

speakers and the organizers

Split by Business Rule

Split by Business Rule

As a participant I want to use flexible times to search for sessions

- starting between x and y o’clock

- with a duration of 45 minutes

- starting early afternoon

- starting at 10am +/- half an hour

Split by Complexity

Split by data type

Split by data type

As a speaker I want to offer additional information to my session so that

potential participants can decide whether to attend

- text documents- videos- audiofiles and podcasts

Split by Data Entry

Split by Data Entry

As a participant I want to create a list of interesting sessions to ensure not to miss

one of them

- notepad- bookmarks- mark as favorite, show in favorite list- drag & drop to favorites- drag & drop to calendar

Split by effort

Split by effort

As a participant I want to pay with credit card

Acceptance Criteria:Visa, Master Card, Diners Club, American Express

As a participant I want to pay with one credit card (out of Visa, MC, DC, AE)- As a participant I want to pay with MC- As a participant I want to pay with DC- As a participant I want to pay with AE

Split by Quality

Split by Quality

As a content provider I want to manage the application content in an easy way

- manage = create, delete, edit- in an easy way:

a) sql-commandlineb) prepared scriptsc) web frontend

Split by user role

As a member of the support staff I want to get a unique error id from the calling user

As an iPhone app user I want to get a meaningful error message so that I know what to do next

Split by user role

As a user of the app I want to get a meaningful error message so that I know

what to do next

As a developer I want the app write stack traces including a unique error id

Split by Performance

Split by Performance

As a participant I want to search the session catalogue for certain keywords

- Slow, takes 15 seconds, search animation- fast, result after less than 2 seconds

Split by Research

Split by Research

As a participant I want to pay with credit card

Acceptance Criteria:Visa, Master Card, Diners Club, American Express

- investigate credit card processing- implement credit card processing

Which pattern to use?

EqualizeStory Size

Deprioritizeor trash

References

References

availableSeptember 2012

Get in touch

Sven RöpstorffAgile Project Manager & Coach

Email: [email protected]: @oedel

LinkedIn: http://www.linkedin.com/in/svenroepstorffXing: https://www.xing.com/profile/Sven_Roepstorff

Agile Lean Europe (ALE)

DrawingsChristian Pursch

TEML-Designswww.teml-designs.de

Credits

Photoswww.sxc.hu