usecase

Creating Effective User Stories

http://www.pluralsight.com/courses/creating-effective-user-stories

User story

  • placeholder for conversation
  • Independent
  • Negotiable
  • Valuable – for end user
  • Estimate-able
  • Small
  • Testable

Are:

  • Brief – designed to
  • High level – defer details

Are not:

  • Detailed – defers design to last responsible moment
  • Set in stone – designed to be flexible

The story format

As a {role} I want to {achievement} So that {confirmation}

  • {role} == group of people
  • {achievement} == what we want to achieve
  • {confirmation} == result of action, acceptance criteria

Epics

  • general goal – consists of multiple stories
  • any story in epic must be done, otherwise cannot make sense

Themes

  • stories are related but are in different epic
  • story can be delivered independently
  • use labels

Persona

  • differentiation of user role – specification
  • picture (real person) & name, details, goals of using system
  • www.romanpichler.com

Split user stories Vertically

Splitting vertically

  • deliver smaller pieces of functionality
  • have more testable
  • positive vs negative path
  • scalebility, secure, reliability => measurement
  • spikes –