USERS STORIES VS. USE CASES 1

USERS STORIES VS. USE CASES

Kristyn Greenwood

WHAT IS NEW?

USERS STORIES VS. USE CASES 2

Persona

Heuristic

User story Use case

User-centered designEthnography

Contextual inquiry

Affinity diagram

Bodystorming

WHAT IS NEW?

USERS STORIES VS. USE CASES 3

Persona

Heuristic

User story Use case

User-centered designEthnography

Contextual inquiry

Affinity diagram

Bodystorming

USER STORIES Stories that represent The experience of the user When interacting with a product/service To accomplish a task or a goal

Requirements / Recommendations Minimum of one per requirement (may lead to creation or documentation of

requirement) As small/simple as possible Agile format

(In software development and product management, a user story is one or more sentences in the everyday or business language of the end user or user of a system that captures what a user does or needs to do as part of his or her job function. - Wikipedia)

USERS STORIES VS. USE CASES 4

USER STORIES: EXAMPLE As a [role/persona], [I/Name] want to [action] so that [goal] As a service manager, I want to be notified when EV is activated for my organization so that I can inform my team that they can start signing.

As a workgroup signer, Mike wants to be able to select an EV certificate when signing his code so that his applications will be accepted by the Microsoft Store.

Additional Details PreConditions Persona Assumptions

USERS STORIES VS. USE CASES 5

USE CASES A Format to describe A list of steps of interaction Between a user and a system for a particular feature It focuses on :

Pre-condition of the system, how the user interacts with the system, how the system behaves and shows what is the end state of the system.

(In software and systems engineering, a use case is a list of steps, typically defining interactions between a role (known in Unified Modeling Language (UML) as an "actor") and a system, to achieve a goal. The actor can be a human or an external system. - Wikipedia)

USERS STORIES VS. USE CASES 6

USECASE: EXAMPLES

PRESENTATION IDENTIFIER GOES HERE 7

USER STORIES VS. USE CASES

USERS STORIES VS. USE CASES 8

USER STORIES VS. USE CASES

USERS STORIES VS. USE CASES 9

Purpose

Set experience of design at a high level

Describe how functionality behaves in a system level

USER STORIES VS. USE CASES

USERS STORIES VS. USE CASES 10

Perspective

User perspective System perspective

USER STORIES VS. USE CASES

USERS STORIES VS. USE CASES 11

Timing

Communicate ideas among the stakeholders at the early stage of design

Guide development after design but before coding

USER STORIES VS. USE CASES

USERS STORIES VS. USE CASES 12

Format

A couple sentences or a paragraph, or it could be a series of drawing comics,

etc.

Well structured forms

USER STORIES VS. USE CASES

USERS STORIES VS. USE CASES 13

Examples

USER STORIES VS. USE CASES

USERS STORIES VS. USE CASES 14

Examples

USER STORIES VS. USE CASES

USERS STORIES VS. USE CASES 15

Examples

USERS STORIES VS. USE CASES 16

Examples

USER STORIES VS. USE CASES

USERS STORIES VS. USE CASES 17

Examples

SPLITTING USER STORIES Why

Easier to comprehend Easier to create acceptance criteria Can be completed in a sprint Encourages discussion

How Look for cleavage lines.

Personas - if 2 involved perhaps 2 stories Data – behavior might vary by data type being handled

Don’t split right away. Wait until Story is prioritized as high or risky

Evidence of a Bad Split Along Process or Procedures Lines

Do this, than this… Along Architecture Lines

Develop, Test, Production Hard to Understand Customer Value is not clear

USERS STORIES VS. USE CASES 18

SPLITTING USER STORIES - EXAMPLE

PRESENTATION IDENTIFIER GOES HERE 19

USERS STORIES VS. USE CASES 20