This document describes how to decompose Agile requirements from high-level Epics down to smaller User Stories. It explains that Epics describe large initiatives or features, Features break Epics into more specific capabilities, and User Stories represent individual needs or tasks. Stories are not specifications but encourage conversation and acceptance criteria. They are arranged in a Usage Sequence to identify dependencies and prioritize the most important. Decomposing requirements this way allows for incremental delivery of working software in short iterations.

1. Decomposing Agile requirements
From Epics to User story

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

3. 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

4. • People
For
• Want to protect their sensitive data
Who
• Is a web-based software
The FX Protection
• Allow clients to protect their sensitive data
That
• Open source software
Unlike
• Will automatically notify about any applications which try to Access to your
confidential data
Our Product
Visión: Product Position

5. Epic
Feature
User Story
• Large initiatives delivering new
products, solutions, or services to
customers
• Comprised of a large collection of
features
• Capabilities that the product owner
is interested in
• Provides values to users
• Realized by some number of user
stories
• Represents a user’s need
• Planning ítem
• Causes a conversation to occur

6. Elaborate/Decomposing
High Level
• Epic
Medium Level
• Feature
Small Level
• User Story

7. 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

8. 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

9. The 3 C’s of a User Story
• Written on note cards
• Can be annoted with estimates,
values, notes, etc
Card
• Details of the story come out
through conversations with the
costumer
Conversation
• Acceptance test are defined to
confirm the story is completeConfirmation

10. Feature1 Feature2 Feature3 Feature4
Usage Sequence

11. Usage Sequence
Feature 1
User
Story
User
Story
Feature 2
User
Story
User
Story
User
Story
Feature 3
User
Story
User
Story
Feature 4
User
Story
Identify stories that
support features or
activities

12. Usage Sequence
Feature 1
User
Story
User
Story
Feature 2
User
Story
User
Story
User
Story
Feature 3
User
Story
User
Story
Feature 4
User
Story
Arrange stories so
most necessary are at
the top
More
important
Less
important

13. Mario Lucero – Agile Coach
Email:
agilecoach@mariolucero.cl
Twitter: metlucero
Blog:
http:://www.mariolucero.cl