story in the slaughterhouse (seacon 2012)

34
Story in the Slaughterhouse Epics und große User Stories sauber filetieren Sven Röpstorff SEACON 2012 Hamburg, 05.06.2012

Upload: sven-roepstorff

Post on 18-Jan-2015

387 views

Category:

Business


2 download

DESCRIPTION

These are the slides from my session "Story in the Slaughterhouse - Epics und User Stories sauber filetieren" from the SEACON 2012 Conference in Hamburg, Germany, on June 5th 2012

TRANSCRIPT

Page 1: 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

Page 2: Story in the Slaughterhouse (Seacon 2012)

What Are User Stories Actually?

Page 3: Story in the Slaughterhouse (Seacon 2012)

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

Page 4: Story in the Slaughterhouse (Seacon 2012)

Card Conversation Confirmation

Triple-C

Page 5: Story in the Slaughterhouse (Seacon 2012)

Card

As who I want what so that why

Page 6: Story in the Slaughterhouse (Seacon 2012)

Conversation

Page 7: Story in the Slaughterhouse (Seacon 2012)

Confirmation

Acceptance Criteria

Page 8: Story in the Slaughterhouse (Seacon 2012)

INVEST in good User Stories

Page 9: Story in the Slaughterhouse (Seacon 2012)

Splitting Patterns

Page 10: Story in the Slaughterhouse (Seacon 2012)

Imagine ...

... a mobile app as a conference guide

Page 11: Story in the Slaughterhouse (Seacon 2012)

Split vertically

Page 12: Story in the Slaughterhouse (Seacon 2012)

Split by Workflow

Page 13: Story in the Slaughterhouse (Seacon 2012)

Split by Workflow

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

speakers and the organizers

Page 14: Story in the Slaughterhouse (Seacon 2012)

Split by Business Rule

Page 15: Story in the Slaughterhouse (Seacon 2012)

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

Page 16: Story in the Slaughterhouse (Seacon 2012)

Split by Complexity

Page 17: Story in the Slaughterhouse (Seacon 2012)

Split by data type

Page 18: Story in the Slaughterhouse (Seacon 2012)

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

Page 19: Story in the Slaughterhouse (Seacon 2012)

Split by Data Entry

Page 20: Story in the Slaughterhouse (Seacon 2012)

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

Page 21: Story in the Slaughterhouse (Seacon 2012)

Split by effort

Page 22: Story in the Slaughterhouse (Seacon 2012)

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

Page 23: Story in the Slaughterhouse (Seacon 2012)

Split by Quality

Page 24: Story in the Slaughterhouse (Seacon 2012)

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

Page 25: Story in the Slaughterhouse (Seacon 2012)

Split by user role

Page 26: Story in the Slaughterhouse (Seacon 2012)

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

Page 27: Story in the Slaughterhouse (Seacon 2012)

Split by Performance

Page 28: Story in the Slaughterhouse (Seacon 2012)

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

Page 29: Story in the Slaughterhouse (Seacon 2012)

Split by Research

Page 30: Story in the Slaughterhouse (Seacon 2012)

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

Page 31: Story in the Slaughterhouse (Seacon 2012)

Which pattern to use?

EqualizeStory Size

Deprioritizeor trash

Page 32: Story in the Slaughterhouse (Seacon 2012)

References

Page 33: Story in the Slaughterhouse (Seacon 2012)

References

availableSeptember 2012

Page 34: Story in the Slaughterhouse (Seacon 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