Writing User Stories Effectively ( http://www.directi.com | http://wiki.directi.com | http://careers.directi.com )‏ Licensed under Creative Commons Attribution Sharealike Noncommercial By, Janeve George [email_address]

Creative Commons Sharealike Attributions Noncommercial Few Instruction It's a workshop not a presentation !!! Parking Lot Perks

It's a workshop not a presentation !!!

Parking Lot

Perks

Creative Commons Sharealike Attributions Noncommercial Overview What are User Stories? Some interesting BuzzWords The story of writing User Stories User role modeling Gathering User Stories Managing Epics and Tiny Stories Pros and Cons of User Stories User Stories gathering workshop References

What are User Stories?

Some interesting BuzzWords

The story of writing User Stories

User role modeling

Gathering User Stories

Managing Epics and Tiny Stories

Pros and Cons of User Stories

User Stories gathering workshop

References

Creative Commons Sharealike Attributions Noncommercial What are User Stories? It is the primary development artifact in XP/Agile development methodology High level requirements document Focuses on Who, What and Why of a feature and not How 3Cs of an User Story (coined by Ron Jeffries) Card: A brief description Conversation: Further information of the User Stories Confirmation: Test to confirm completeness and acceptance

It is the primary development artifact in XP/Agile development methodology

High level requirements document

Focuses on Who, What and Why of a feature and not How

3Cs of an User Story (coined by Ron Jeffries)

Card: A brief description

Conversation: Further information of the User Stories

Confirmation: Test to confirm completeness and acceptance

Creative Commons Sharealike Attributions Noncommercial What are User Stories?

Creative Commons Sharealike Attributions Noncommercial What are User Stories?

Creative Commons Sharealike Attributions Noncommercial What are User Stories? A well-written User Story follows the INVEST model (coined by Bill Wake): I ndependent N egotiable V aluable E stimable S mall T estable User stories can describe Feature Non-Functional Feature Bug Fixes

A well-written User Story follows the INVEST model (coined by Bill Wake):

I ndependent

N egotiable

V aluable

E stimable

S mall

T estable

User stories can describe

Feature

Non-Functional Feature

Bug Fixes

Creative Commons Sharealike Attributions Noncommercial Some Interesting BuzzWords The Customer Team Epics Themes User Role Modeling Story Writing Workshop User Proxies

The Customer Team

Epics

Themes

User Role Modeling

Story Writing Workshop

User Proxies

Creative Commons Sharealike Attributions Noncommercial Story of writing User Stories Brainstorming initial set of User Roles Organize the set of User Roles Consolidate the set of User Roles Refine the set of User Roles Choose one User Role to start with Write as many Cards as possible for the User Role Discuss and refine the set of Cards Prioritize for iteration Compile a reliable set of Confirmations Pin down every valuable Conversation Refined set of User Role Refined set of User Stories Step in process Development Artifacts

Creative Commons Sharealike Attributions Noncommercial User Role Modeling User Roles Various types of users Role Modeling Brain storming Organizing Consolidating Refining Personas Imaginary representation of an User Role Could use pictures too Extreme Characters

User Roles

Various types of users

Role Modeling

Brain storming

Organizing

Consolidating

Refining

Personas

Imaginary representation of an User Role

Could use pictures too

Extreme Characters

Creative Commons Sharealike Attributions Noncommercial Gathering User Stories User Interviews Select right interviewees Ask open-ended, context-free questions Questionares Best if there is a large user population When you need answers to specific questions Observation Best fot In-House developments Story writing Workshops Effective during the initial phase of the project / release

User Interviews

Select right interviewees

Ask open-ended, context-free questions

Questionares

Best if there is a large user population

When you need answers to specific questions

Observation

Best fot In-House developments

Story writing Workshops

Effective during the initial phase of the project / release

Creative Commons Sharealike Attributions Noncommercial Guidelines for good User Stories Start with Goal Stories Slicing the cake Write closed stories Size it for the Horizon “ I as a (role) want (something), so that (benefit)” Colored cards

Start with Goal Stories

Slicing the cake

Write closed stories

Size it for the Horizon

“ I as a (role) want (something), so that (benefit)”

Colored cards

Creative Commons Sharealike Attributions Noncommercial Managing Epics and Tiny Stories Epics are too large to estimate and can be split into multiple stories Epics represents Complex functionality Placeholders for low priority stories Types of Epics Compound Stories Complex Stories Different ways to split Epics Various small actions in the Epic Along the boundaries of Data Depending on complexity

Epics are too large to estimate and can be split into multiple stories

Epics represents

Complex functionality

Placeholders for low priority stories

Types of Epics

Compound Stories

Complex Stories

Different ways to split Epics

Various small actions in the Epic

Along the boundaries of Data

Depending on complexity

Creative Commons Sharealike Attributions Noncommercial Managing Epics and Tiny Stories Tint stories are too short Its better to Combine multiple tiny stories Group them into Themes

Tint stories are too short

Its better to

Combine multiple tiny stories

Group them into Themes

Creative Commons Sharealike Attributions Noncommercial Creating User Stories Sequentially numbered Customer Focused Written from a User's perspective Better if written by the user Avoid technical jargons Shouldn't be too short nor too long Should be complete and testable Should be able to implement by two people in a single iteration Avoid infrastructure, technology or service elements

Sequentially numbered

Customer Focused

Written from a User's perspective

Better if written by the user

Avoid technical jargons

Shouldn't be too short nor too long

Should be complete and testable

Should be able to implement by two people in a single iteration

Avoid infrastructure, technology or service elements

Creative Commons Sharealike Attributions Noncommercial Pros and Cons of User Stories Short and Easy to modify as in when requirements changes Allow projects to be broken into small increments Easier to estimate the development effort Completed User stories can go for development It drives the creation of Acceptance tests Initial learning curve They require close customer contact Rely more on competent developers

Short and Easy to modify as in when requirements changes

Allow projects to be broken into small increments

Easier to estimate the development effort

Completed User stories can go for development

It drives the creation of Acceptance tests

Initial learning curve

They require close customer contact

Rely more on competent developers

Creative Commons Sharealike Attributions Noncommercial References User Stories Applied: For Agile Software Development by Mike Cohn http://www.agile-software-development.com/search/label/user%20stories http://agilesoftwaredevelopment.com/blog/vaibhav/good-user-story-invest

User Stories Applied: For Agile Software Development by Mike Cohn

http://www.agile-software-development.com/search/label/user%20stories

http://agilesoftwaredevelopment.com/blog/vaibhav/good-user-story-invest

Questions??? [email_address] http://directi.com http://careers.directi.com

Online Library Portal A User Stories gathering workshop [email_address] http://directi.com http://careers.directi.com

Retrospective!!! [email_address] http://directi.com http://careers.directi.com