Breaking Down Stories - Concept to Sprint Ready PDF

PlayUP
Social games and live sport

Breaking Down Stories

Concept to Sprint Ready

Reginald de Silva

MAY Breaking Down Stories
2011
©PlayUp Interactive Entertainment 2

What is a Story? PlayUP

A Story describes a particular user feature or function in a manner that
business representatives and technical team members can understand.

Stories:
• Describe features or functionality that is testable and has business value
• Express requirements in simple terms and can be estimated, measured
and tracked
• Communicates between all parties
• Not too small
• Not too big – i.e. can be completed within one sprint
• May also be non-functional
• Are used by the entire project team including business Subject Matter
Experts
2011

Story Attributes PlayUP

The acronym "INVEST" can remind you that good
stories are:
I - Independent
N - Negotiable
V – Valuable (can also mean Vertical)
E - Estimable (or Estimatable)
S - Small
T – Testable
2011

Why are Stories important? PlayUP

• Communication
• Planning - short and long
• Seeing the “Big Picture” with some granularity

2011

The 3 C’s PlayUP

Stories are more than words...

• Card – story text
• Conversation – discuss the details
• Confirmation – record acceptance tests

2011

User Roles PlayUP

• Broaden the scope from looking at one user
• Allows users to vary by:
 What they use the software for
 How they use the software
 Background
 Familiarity with the software / computers
• Used extensively in usage-centred design

2011

Why Story index cards? PlayUP

• You can’t fit much text onto an index card!

• Tactile qualities get everyone involved

2011

Story Cards PlayUP

Story cards are used for:
• Sprint planning
• Estimation sessions
Story-01
• Product or Project Backlog and Sprint story card wall
User creates a new
Story-02
Cards might include: customer record
User creates a
• Story ID
• Story Title customer record
• Estimate M 4
• Business priority
M 4

2011

Story Conventions PlayUP

STORY NARRATIVE CONVENTION

“As <role>
I want <function>
so that <business value>”

ACCEPTANCE TEST CONVENTION

“When I do this <action>,
I expect this <result>”

SCENARIO CONVENTION

Given some initial context (the givens),
When an event occurs,
Then ensure some outcomes.

2011

A process that I like to follow to
PlayUP
help articulate scenarios... Social games and live sport

Agreed
terminology
Domain Model Glossary Scenarios
(ubiquitous
language)

2011

Backlog PlayUP

• Each project will have a backlog – a prioritised and
estimated list of remaining work (story cards) to be done

• Over the course of the project, the backlog is re-prioritised
so that the team always works on the most valuable feature
next

• Stories can also be added and removed from the backlog

2011

A process that I like to follow to
PlayUP
help build the Backlog... Social games and live sport

As-Is To-Be
Process Process Epics Stories Backlog
Maps Maps

2011

Another process that I like to
follow to help build the Backlog... PlayUP

Business Functional Carding
Epics Stories Backlog
Requirements Requirements session

2011

... And another process that I like to

Business Carding
Stories Backlog
Requirements session

2011

... And another process that I like to

Business
Stories Backlog
Concept

2011

Story format and content
PlayUP
that I like... Social games and live sport

• Story name is the business narrative

• Scenarios are used to describe key behaviours and business value

• Scenarios are used for acceptance

• Files such as UI mock ups, UI prototypes and spreadsheets are attached

2011

Story Example PlayUP

• A Story describes a valuable As a sales assistant
I want to create a new customer record
So that I can invoice the customer and
feature in a manner that both contact them as required

business and IT team Scenario 1: New customer record created

Given the sales assistant is logged in
members can understand. to the customer database
And has selected to create a new record

When the create a customer record form is
displayed

• Stories are written in clear, Then the sales assistant can enter the
customers first name
concise acceptance criteria And can enter the customers surname
And can enter the customers contact phone
number
scenarios and focus on And can enter the customers mailing
address
business value! And can enter the customers email address
And can save the record

2011

Story Card Wall
Ready for Sprint In Development In Testing Social gamesDonelive sport
and

Story-1
User creates a
customer
record 3

Story-2
User views a
customer
record 3

Story-3
User edits a
customer
record 2

Story-4
User deletes a
customer
record 1

Provides visibility of sprint progress Stories move across the wall from left to right

Story estimation PlayUP

Story complexity and effort is estimated using “Story points”
Relative estimation using a scale such as:
• Fibonacci - 0, 1, 2, 3, 5, 8
• 1, 2, 4, 8, 16
• 1, 2, 3
• T-shirt sizes – S, M, L, XL
• etc.

Estimation is team based...
• Team discusses requirements for each story
• Developers and Testers provide an individual points estimate for each story
• Estimates are discussed until team consensus is reached

2011

Velocity PlayUP

The team’s throughput for an iteration is called its ‘Velocity’.

A team’s velocity takes into account what has been achieved previously, team size,
experience levels and planned leave.

Velocity is usually measured using burn-up/burn-down charts:

Sprint Sprint

2011

Sprint planning PlayUP

At the beginning of each sprint, the team
plans for the next sprint:
• Team discusses planned velocity
(throughput)
• Business representatives advise on priority
• IT team members advise on technical risk
• Team agrees on stories to be delivered
2011

Breaking Down Stories - Concept to Sprint Ready PDF

Recomendados

Recomendados

Más contenido relacionado

Similar a Breaking Down Stories - Concept to Sprint Ready PDF

Similar a Breaking Down Stories - Concept to Sprint Ready PDF (9)

Último

Último (20)

Breaking Down Stories - Concept to Sprint Ready PDF