User Stories - Pega

[Pages:19]User Stories

Short, simple descriptions of a feature told from the perspective of the customer

What is a User Story?

From Mike Cohn:

? "User Stories are a part of an Agile approach that helps shift the focus from writing about requirements to talking about them..."

? "All Agile User Stories include a written sentence or two, and, more importantly, a series of conversations about the desired functionality."

Source: 00 Month 0000

Footer (Edit footer for all slides with View > Header & Footer)

2

The 3 C's of User Stories

?CARD ?CONVERSATION ?CONFIRMATION

00 Month 0000

Footer (Edit footer for all slides with View > Header & Footer)

3

The INVEST Model

INVEST is an acronym that captures the ideal qualities of User Stories:

? Independent: The User Story is not dependent on other Stories. ? Negotiable: The User Story can be changed, rewritten, or split (prior to being

committed to a sprint). ? Valuable: The User Story must deliver value to the end user. ? Estimable: The Development Team must be able to estimate the User Story's size. ? Small: Every User Story has to be sized appropriately to fit into a Sprint. ? Testable: The User Story is capable of being tested.

00 Month 0000

Footer (Edit footer for all slides with View > Header & Footer)

4

What's the difference between User Stories and Requirements?

USER STORIES

REQUIREMENTS

Who creates?

"3 Champions" to Full Teams

Typically only the Business

Level of detail Time to create When to create? Primary Info Transmission Hand-offs Change Control

Just enough; open for negotiation

Quick, placeholder for further conversations and elaboration

Create when/as needed; reflect current needs

Collaboration emphasized, write down only what's needed after discussion Low amount of hand-off; expectation for collaboration Experiment, learn, expectation for change

High level of detail, specific; tends to cover all possible combinations

Can be laborious, taking significant time to complete

Created far in advance; reflect needs at a particular point in time, typically in the past

Written documentation

Tendency for high amount of hand-offs ? business to IT, IT to Quality, Quality to...

Lock down then implement significant effort process for changes

00 Month 0000

Footer (Edit footer for all slides with View > Header & Footer)

5

User Story Format

?As a... [Who? - Insert the User]

?I would like to... [What? - Insert what they want to do]

?so that... [Why? ? Insert the Business Value]

00 Month 0000

Footer (Edit footer for all slides with View > Header & Footer)

6

Example Stories ? Hypothetical Promotion Enrollment:

00 Month 0000

Footer (Edit footer for all slides with View > Header & Footer)

7

Implementation Details vs. Value of Implementation

00 Month 0000

Footer (Edit footer for all slides with View > Header & Footer)

8

 ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download