breaking down agile requirements in agile methodology

13
Decomposing Agile requirements From Epics to User story

Upload: mario-lucero

Post on 11-May-2015

324 views

Category:

Technology


3 download

DESCRIPTION

Decomposing Agile requirements

TRANSCRIPT

Page 1: Breaking down agile requirements in Agile Methodology

Decomposing Agile requirements

From Epics to User story

Page 2: Breaking down agile requirements in Agile Methodology

Vision

• Describe the problem being solved• Describe a product solution• Provides a list of features delivered in the release• Create shared understanding of purpose

Page 3: Breaking down agile requirements in Agile Methodology

The problem of

•Customizing client profile

Affects

•People who want to customize their profile

The impact of which is

•Sensitive information has to be protected

A successful solution would

•Allow a user to select which applications can Access to his private data

Vision: Problem

Statement

Page 4: Breaking down agile requirements in Agile Methodology

For

• People

Who

• Want to protect their sensitive data

The FX Protection

• Is a web-based software

That

• Allow clients to protect their sensitive data

Unlike

• Open source software

Our Product• Will automatically notify about any applications which try to Access to your confidential

data

Visión: Product Position

Page 5: Breaking down agile requirements in Agile Methodology

Epic

Feature

Capabilities that the product owner is interested in Provides values to usersRealized by some number of user stories

User Story

Represents a user’s needPlanning ítemCauses a conversation to occur

Page 6: Breaking down agile requirements in Agile Methodology

Elaborate/Decomposin

g

High Level

• Epic

Medium Level

• Feature

Small Level

Page 7: Breaking down agile requirements in Agile Methodology

Epic1 Customize client’s profile

Feature1 Allow user to keep a profile

User Story1 As User I want to enter details to my profile

User Story2 As User I want to protect the Access to my private information so I need to choose what app can access to my data

Page 8: Breaking down agile requirements in Agile Methodology

User stories no son requerimientosUser stories are not requirements

They are not detailed specifications

They are short and easy to read

They don’t last longer and can be deprecated

Increase value released in days

Page 9: Breaking down agile requirements in Agile Methodology

The 3 C’s of a User Story

•Written on note cards•Can be annoted with estimates, values, notes, etcCard•Details of the story come out through conversations with the costumer

Conversation

•Acceptance test are defined to confirm the story is complete

Confirmation

Page 10: Breaking down agile requirements in Agile Methodology

Feature1 Feature2 Feature3 Feature4

Usage Sequence

Page 11: Breaking down agile requirements in Agile Methodology

Usage Sequence

Feature 1

User Story

User StoryIdentify stories that support features or activities

Page 12: Breaking down agile requirements in Agile Methodology

Usage Sequence

Feature 1

User Story

User StoryArrange stories so most necessary are at the top

More important

Less important

Page 13: Breaking down agile requirements in Agile Methodology

Mario Lucero – Agile Coach

Email: [email protected]

Twitter: metlucero

Blog: http:://www.mariolucero.cl