release planning with user stories

81
RELEASE PLANNING WITH USER STORIES Planning for Success

Upload: jamie-nicholson

Post on 07-Dec-2014

821 views

Category:

Documents


0 download

DESCRIPTION

 

TRANSCRIPT

Page 1: Release Planning with User Stories

RELEASE PLANNING WITH USER STORIES

Planning for Success

Page 2: Release Planning with User Stories

Introductions

Page 3: Release Planning with User Stories

Years of experience in Agile

Page 4: Release Planning with User Stories

Test first charts

Page 5: Release Planning with User Stories

In the context of Release planning…

What puzzles you?

What action do you want to take?

What ideas do you have?

What challenges do you have?

Page 6: Release Planning with User Stories

Introduction

Page 7: Release Planning with User Stories
Page 8: Release Planning with User Stories

BBC Process

Page 9: Release Planning with User Stories
Page 10: Release Planning with User Stories
Page 11: Release Planning with User Stories

VisionRealit

y

Actions

Decisions

Page 12: Release Planning with User Stories

Vision Value Drivers

Generating a

BacklogSizing Priority

Return on

Investment

Theming MMF and MVP

Risk Assessm

entPlanning Setting

GoalsReportin

g

Page 13: Release Planning with User Stories

Introducing the Product

Page 14: Release Planning with User Stories

Introducing the Product

The BBC has commissioned a new weather app.

The project has the go-ahead.

The requirements have been captured and written as user stories.

It’s your job to get a delivery plan together.

Page 15: Release Planning with User Stories

Vision Value Drivers

Generating a

BacklogSizing Priority

Return on

Investment

Theming MMF and MVP

Risk Assessm

entPlanning Setting

GoalsReportin

g

Page 16: Release Planning with User Stories

Vision and Value

Page 17: Release Planning with User Stories

VisionRealit

y

Actions

Decisions

Page 18: Release Planning with User Stories

Product Vision Statement

For

[defined market]

[product]

is the only

[product category]

that offers

[differentiator].

This means that

[benefit].

What makes it different………

What it means to the customer or user…………..

What it’s called…...………….

Who it’s for…………………..

What it does………………….

Page 19: Release Planning with User Stories

Vision

For

[people who value spending time outdoors],

[The Mobile Weather App]

is the only

[Mobile Weather Application]

that offers

[a personalised and community based service].

This means that

[others in the community of the app user share the experience and the BBC gains valuable feedback

on usage and lifestyles].

Page 20: Release Planning with User Stories

Vision Value Drivers

Generating a

BacklogSizing Priority

Return on

Investment

Theming MMF and MVP

Risk Assessm

entPlanning Setting

GoalsReportin

g

Page 21: Release Planning with User Stories

Value Drivers

Definition of value driver from Finance something adding value to product or

service an activity or organizational focus that

enhances the value of a product or service in the perception of the consumer and which therefore creates value for the producer.

Page 22: Release Planning with User Stories

The journey is the most important thing

Take my time to visit places along the way

Staying with local people will allow me to understand different cultures

Australia is a useful target, but could be somewhere else

Speed of getting there is not important

Five star luxury is not necessary, although the odd treat might be nice

Things I Value (Value more)

Things I don’t Value (Value less)

I want a Trip to AustraliaVa

lue

Drive

rs

Cons

trai

nts

Page 23: Release Planning with User Stories

Example of unclear Value

Original name: Service Data Capture Project

Revised name: Beneficiary Relationship Management System

Drivers: Remain aligned to capturing data

Result: Confusion. Some delivering a Case Management System, some delivering a Data Capture System. Wasted effort. Conflict. Overspend.

Page 24: Release Planning with User Stories

Value Drivers

Exercise In two groups,

discuss the Vision Statement and produce a list of things that are “important” to the product.

Prioritise and select the top three.

For

[people who value spending time outdoors],

[The Mobile Weather App]

is the only

[Mobile Weather Application]

that offers

[a personalised and community based service].

This means that

[others in the community of the app user share the experience

and the BBC gains valuable feedback on usage and

lifestyles].

Page 25: Release Planning with User Stories

Vision

Value Drive

rs

Generating a

Backlog

Sizing

Priority

Return on Investmen

t

Theming

MMF and MVP

Risk Assessme

nt

Planning

Setting

Goals

Reporting

Page 26: Release Planning with User Stories

Backlogs & Roadmaps

What is the difference between a backlog and a roadmap?

Page 27: Release Planning with User Stories

Backlogs & Roadmaps

RoadmapItem

Epic orRequirement

Epic orRequirement

Epic orRequirement

RoadmapItem

Epic orRequirement

Epic orRequirement

Epic orRequirement

Epic orRequirement

Epic orRequirement

RoadmapItem

Epic orRequirement

Epic orRequirement

RoadmapItem

Epic orRequirement

Epic orRequirement

Epic orRequirement

Epic orRequirement

SeniorManagers

Team & Project Manager

Product Manager & Head Of

Page 28: Release Planning with User Stories

Why a backlog?

Helps you arrange your work Increases visibility Gives the project a focal point Lets you see what you’ve got Allows you to look ahead at what is

coming Is the project on a page Basis of basic project metrics

Page 29: Release Planning with User Stories

Planning by using a backlog

Priority 1Size 2

Priority 2Size 4

Priority 4Size 3

Priority 1

Priority 2

Priority 3

Priority 4

Priority 5

Priority 6

Velocity = 9

IterationOne

BacklogIteration 1 Plan

Priority 1Size 1

Priority 2Size 8

IterationTwo

Iteration 2 Plan

Priority 1Size 4

Priority 2Size 3

Priority 4Size 3

Iterationn

Iteration 3 Plan

Velocity = 9 Velocity = 10

Priority 7

Priority n

Page 30: Release Planning with User Stories

Backlog with swim lanes

Page 31: Release Planning with User Stories
Page 32: Release Planning with User Stories

Introducing the Backlog

User Stories

Page 33: Release Planning with User Stories

Understanding what’s in there Review the set of Stories

What can we use to understand and order the stories as given

Use priority ordering, based on the vision and value drivers already identified

Lay the stories out in one list, higherst priority at the top

Page 34: Release Planning with User Stories

Vision

Value Drive

rs

Generating a

Backlog

Sizing

Priority

Return on Investmen

t

Theming

MMF and MVP

Risk Assessme

nt

Planning

Setting

Goals

Reporting

Page 35: Release Planning with User Stories

Sizing

Page 36: Release Planning with User Stories

What do we mean by Sizing? Working out the relative complexity of

different User Stories. Most commonly done using Affinity

Sizing or Planning Poker. Best done in a group, by the team. They are estimates.

Page 37: Release Planning with User Stories

Vision

Value Drive

rs

Generating a

Backlog

Sizing

Priority

Return on Investmen

t

Theming

MMF and MVP

Risk Assessme

nt

Planning

Setting

Goals

Reporting

Page 38: Release Planning with User Stories

Priority

Page 39: Release Planning with User Stories

What do we mean by priority? We need to be organised about what we

do. Value to the customer should be a key

consideration. Needn’t be fixed, but needs to be more

stable the closer it comes to development.

What else can we prioritise by?

Page 40: Release Planning with User Stories

Vision

Value Drive

rs

Generating a

Backlog

Sizing

Priority

Return on Investmen

t

Theming

MMF and MVP

Risk Assessme

nt

Planning

Setting

Goals

Reporting

Page 41: Release Planning with User Stories

Return on Investment

Page 42: Release Planning with User Stories

How to calculate RoI

Page 43: Release Planning with User Stories

Vision

Value Drive

rs

Generating a

Backlog

Sizing

Priority

Return on Investmen

t

Theming

MMF and MVP

Risk Assessme

nt

Planning

Setting

Goals

Reporting

Page 44: Release Planning with User Stories

Story Theming

Page 45: Release Planning with User Stories

What is story theming?

A collection of User Stories, a useful group which we want to use to help plan and deliver

Going through the process of theming helps to clarify what you have and what is missing

Themes can become the basis of planning or just inform the process

The important element is having the conversations driven by themes

Page 46: Release Planning with User Stories

Stories in the Backlog

Page 47: Release Planning with User Stories

Map Stories to ThemesTHEME 3

THEME 4

THEME 5

THEME 2

THEME 1

Page 48: Release Planning with User Stories

Approaches for Theming Stories Simplicity

Do the simplest thing you could possibly work first and get it working end to end. You have always got something to demonstrate. If that’s still too big then .....

By User or Persona Try focussing on a subset of users or a single user, start with the most

valuable. Select the Persona who provides maximum coverage or who provides

the greatest challenge (or risk).

Process Pick the “Happy Path” first, the path that is taken the majority of the

time. Add the edge cases and exceptions as you go, be prepared to look at alternatives if you run out of time or budget.

Data Set Limit the data set that you apply the functionality to, add others as

you build and learn from the first. For example: Customers in a CRM.

By Feature Arrange by groups of stories against a Feature and work out minimal

builds….

Page 49: Release Planning with User Stories

Exercise

In groups, look at the set of stories First of all, what possibilities are there for

grouping the stories Agree on one way and try it

What does it tell you about the backlog?

Page 50: Release Planning with User Stories

Non-functional Requirements Constraints on the design Can have an impact on all or many of

functional user stories Making adjustments:

Decompose the NFR into smaller requirements and prioritise e.g. the order of platform compatibility

Cumulative effect – each iteration should still maintain the NFR i.e. don’t drop it in later iteration

Use definition of done and acceptance criteria to maintain integrity of the NFR

Turn some NFRs into non-software functional product

Page 51: Release Planning with User Stories

Identifying NFRs

Review the user stories for the application

Identify which stories are non-functional. How are you going to manage their

implementation or challenge their existence?

Page 52: Release Planning with User Stories

Vision

Value Drive

rs

Generating a

Backlog

Sizing

Priority

Return on Investmen

t

Theming

MMF and MVP

Risk Assessme

nt

Planning

Setting

Goals

Reporting

Page 53: Release Planning with User Stories

Stories in the Backlog

Page 54: Release Planning with User Stories

Decide what Features are Required

FEATURE 1 FEATURE 2 FEATURE 3 FEATURE 4 FEATURE 5

For examplePAYMENTS RETURNS COMPLAINTS VOUCHERS

Page 55: Release Planning with User Stories

Map Stories to FeaturesFEATURE 1 FEATURE 2 FEATURE 3 FEATURE 4 FEATURE 5

Page 56: Release Planning with User Stories

Group Stories to Minimal Sets

FEATURE 1 FEATURE 2 FEATURE 3 FEATURE 4 FEATURE 5

Page 57: Release Planning with User Stories

Group Stories to Minimal Sets

FEATURE 1 FEATURE 2 FEATURE 3 FEATURE 4 FEATURE 5

Minimal Marketab

le Feature

Minimal Marketab

le Feature

Minimal Marketab

le Feature

Minimal Marketab

le Feature

Minimum Viable Release

Page 58: Release Planning with User Stories

Who uses MMF/MVPs?

Who cares about MMF and MVP/MVR?

Page 59: Release Planning with User Stories

Vision

Value Drive

rs

Generating a

Backlog

Sizing

Priority

Return on Investmen

t

Theming

MMF and MVP

Risk Assessme

nt

Planning

Setting

Goals

Reporting

Page 60: Release Planning with User Stories

Risk Management

Taking a risk-led view of the plan Can be performed pre- or post-planning What does the risk profile look like within

the plan?

Page 61: Release Planning with User Stories

Probability

Imp

act

Hig

hLo

w

Low High

Page 62: Release Planning with User Stories

Risk profile of projectFEATURE 1 FEATURE 2 FEATURE 3 FEATURE 4 FEATURE 5

Page 63: Release Planning with User Stories

Probability

Imp

act

10

00

0% 100%50%

70

40%

70*40%=28

12.5

3.528

39

45

2.8

16 28

1.06

9

Page 64: Release Planning with User Stories

Risk score of projectFEATURE 1 FEATURE 2 FEATURE 3 FEATURE 4 FEATURE 5

5

1

20

3

35

5

2

2 5

20

18

18

3

1

3

5

6

10

4

30

10

15

311

12

9

8

20

5

1

2

15

12

4

3

8

2

19

9

3

2

10

2

3

Total risk score: 80

Total risk score: 175

Total risk score: 123

Page 65: Release Planning with User Stories

Risk Profile by Release

R1

R2

R3

Tota

l ri

sk s

core

Page 66: Release Planning with User Stories

Risk Burn-down by Release Plan

Start R1Complete

R2Complete

R3Complete

Tota

l ri

sk s

core

Page 67: Release Planning with User Stories

Active Risk Burn-down

Spri

nt

1

Spri

nt

2

Spri

nt

3

Spri

nt

4

Spri

nt

5

Spri

nt

6

Spri

nt

7

Spri

nt

8

Spri

nt

9

Spri

nt

10

Spri

nt

11

Spri

nt

12

Spri

nt

13

Spri

nt

14

0

500

1000

1500

2000

2500

Risk managedRisk loaded

Ris

k S

core

Page 68: Release Planning with User Stories

Exercise

Draw a chart on a sheet, either as a risk zone or risk matrix

Place cards on sheet according to risk On front, colour code according to risk

category On back calculate risk score

Page 69: Release Planning with User Stories

Vision

Value Drive

rs

Generating a

Backlog

Sizing

Priority

Return on Investmen

t

Theming

MMF and MVP

Risk Assessme

nt

Planning

Setting

Goals

Reporting

Page 70: Release Planning with User Stories

Planning

Page 71: Release Planning with User Stories

Planning

Lay your stories out in the order you plan to have them done.

Remember to check your plans with your Product Owner.

Vision Sprint Goals Velocity Themes MMFs Value

What to do Also consider

Page 72: Release Planning with User Stories

Project Plan

Page 73: Release Planning with User Stories

Vision

Value Drive

rs

Generating a

Backlog

Sizing

Priority

Return on Investmen

t

Theming

MMF and MVP

Risk Assessme

nt

Planning

Setting

Goals

Reporting

Page 74: Release Planning with User Stories

Setting Goals

Page 75: Release Planning with User Stories

Setting Release Goals

A series of mini visions for the project Should tie in to the Project Vision Should be clear and concise Should be well communicated &

understood Up on a wall Everyone knows what it is

Exercise: Give your releases a goal

Page 76: Release Planning with User Stories

Vision

Value Drive

rs

Generating a

Backlog

Sizing

Priority

Return on Investmen

t

Theming

MMF and MVP

Risk Assessme

nt

Planning

Setting

Goals

Reporting

Page 77: Release Planning with User Stories

Reporting

Page 78: Release Planning with User Stories

Reporting – Burn Ups

Page 79: Release Planning with User Stories

What we can use for reporting Risk Return on Investment Story Points / Estimation MMFs MVPs Themes Business Value

Remember: it is better to collect the data and then not use it than to not collect it

then need it…

Page 80: Release Planning with User Stories

Review and Feedback

Page 81: Release Planning with User Stories

Agility in Mind Limited, 34 High Street, Market Lavington, Wiltshire SN10 4AG United Kingdom

Registered in England and Wales: 7289974

COPYRIGHT © 2012 AGILITY IN MIND LIMITED

For more information please contact:

Andrew [email protected] 800 759