Harry HochheiserDepartment of Biomedical InformaticsUniversity of Pittsburghharryh@pitt.edu

Harry Hochheiser, harryh@pitt.edu Baobab Health, February 2015Attribution-ShareAlikeCC BY-SA

User Stories

Harry Hochheiser, harryh@pitt.edu Baobab Health, February 2015

Key goal of user requirementsresearch?

• Contextual inquiry, scenarios, flow diagrams, storyboards…

• Building explicit, shared understanding

Harry Hochheiser, harryh@pitt.edu Baobab Health, February 2015

User Stories

• Short, micro-scenarios

• Contain users, goals and reason

• Justify endpoint in terms of motivations associated with a role

Harry Hochheiser, harryh@pitt.edu Baobab Health, February 2015

User Stories

• As a user, I want to goal, so that I can reason

Harry Hochheiser, harryh@pitt.edu Baobab Health, February 2015

User stories for LIMS?

• Ordering a test:

• As a doctor, I want to order an FBC test so that I can differentially diagnose my patient’s condition.

Harry Hochheiser, harryh@pitt.edu Baobab Health, February 2015

User story mapping Patton & Economy, 2014

• Cards for

• Users (AKA stakeholders)

• Goals

• Activities

• Details

Harry Hochheiser, harryh@pitt.edu Baobab Health, February 2015

User story map http://www.agileproductdesign.com/blog/the_new_backlog.html

Big stories

Harry Hochheiser, harryh@pitt.edu Baobab Health, February 2015

Building the map

1. Write out stories one task at a time

2. Organize stories -stack them if they happen at the same time

3. Explore alternatives - stack vertically

4. Simplify and distill

Harry Hochheiser, harryh@pitt.edu Baobab Health, February 2015

Examplehttp://winnipegagilist.blogspot.ca/2012/03/how-to-create-user-story-map.html

Harry Hochheiser, harryh@pitt.edu Baobab Health, February 2015

Examplehttp://winnipegagilist.blogspot.ca/2012/03/how-to-create-user-story-map.html

Harry Hochheiser, harryh@pitt.edu Baobab Health, February 2015

storiesonboard.com

Harry Hochheiser, harryh@pitt.edu Baobab Health, February 2015

Using the story map

• Determine which to tackle

• Review the tasks and stories to determine what is needed and how

• Develop storyboards, prototypes, etc.

Harry Hochheiser, harryh@pitt.edu Baobab Health, February 2015

Blood bank Activities

1. Intake of request

2. Grouping

3. Matching

4. Selection of bags

5. Inventory intake

6. Communication of results

Harry Hochheiser, harryh@pitt.edu Baobab Health, February 2015

Plan

• Develop user stories for Blood bank use of LIMS

• Map them out

• Develop prototypes

• Tablet

• Dashboard

Harry Hochheiser, harryh@pitt.edu Baobab Health, February 2015

• When are we done?

• How many are enough?

• How can they be used to develop designs?

• How do they fit with other approaches?

Questions about user stories?