liz september 2014. a story about software that matters

51
Capability Red Liz Keogh @lunivore September 2014

Upload: reginald-webster

Post on 18-Jan-2018

219 views

Category:

Documents


0 download

DESCRIPTION

“Hunt the value.” - Chris Matts, Feature Injection Value Mapping

TRANSCRIPT

Page 1: Liz September 2014. A story about software that matters

CapabilityRed

Liz Keogh@lunivoreSeptember 2014

Page 2: Liz September 2014. A story about software that matters

A storyabout

software that matters

Page 3: Liz September 2014. A story about software that matters

“Hunt the value.”

- Chris Matts,Feature Injection

Value Mapping

Page 4: Liz September 2014. A story about software that matters

Vision

Makes moneySaves money

Protects moneyPrimaryStake-holder

Page 5: Liz September 2014. A story about software that matters

Goal

Neededto go liveIncidental

Stake-holder

Page 6: Liz September 2014. A story about software that matters

Themes / Feature Sets

A themedgroup offeaturesBusiness

Analyst

Page 7: Liz September 2014. A story about software that matters

Scenario

An examplethat illustrates

system behaviourand howit delivers

value

Dev, tester,analyst

Page 8: Liz September 2014. A story about software that matters

Feature

User interfacecomponent

which enablesa capability

UIDesigner

Page 9: Liz September 2014. A story about software that matters

Story

A slice througha featureto enable

fasterfeedback

Often adeveloper

Page 10: Liz September 2014. A story about software that matters

Code

Ideas turning intorealityDeveloper

Page 11: Liz September 2014. A story about software that matters

Other ways of asking “Why”?

What will bedifferent?

What will that get for youthat you

don’t already have?

What will you, or the users, or the system,be able to do

that you can’t do already?

Page 12: Liz September 2014. A story about software that matters

The Innovation Cycle

CommoditiesDifferentiators

RepeatabilityBuilding on

Spoilers

Page 13: Liz September 2014. A story about software that matters

Etymology

capere -

to grasp, lay hold, take, catch; undertake;

take in, hold; be large enough for;

comprehend

- etymonline.com

Page 14: Liz September 2014. A story about software that matters

Themes / Feature Sets

Business Analyst

Capability:

The ability to do somethingreally well

Page 15: Liz September 2014. A story about software that matters

Continuous vs. Discrete Capabilities

If you can’t test it,monitor it.

Page 16: Liz September 2014. A story about software that matters

Put some numbers on them!

We want to be able toupdate the front page

more quickly.in 5 minutes.

Page 17: Liz September 2014. A story about software that matters

Breaking everything down up-frontis Waterfall!

Visio

n

Goal

Capa

bilit

y

Scen

ario

Feat

ure

Stor

y

Code

Page 18: Liz September 2014. A story about software that matters

If a project has no risks,

don’t do it.

Page 19: Liz September 2014. A story about software that matters

Cynefin

Simple

ComplicatedComplex

ChaoticWith thanks toDavid Snowden and Cognitive Edge

Page 20: Liz September 2014. A story about software that matters

Estimating Complexity

5. Nobody has ever done it before4. Someone outside the org has done it before (probably a competitor)3. Someone in the company has done it before2. Someone in the team has done it before1. We all know how to do it.

Page 21: Liz September 2014. A story about software that matters

Estimating ComplexitySelf-

driving

cars

MendingWatches

GPS

Dates

MannedMarsMission

AppleFanBase

SAP User

Registration

(unless you’re in the Energy business)

OMG OMG OMG!

Page 22: Liz September 2014. A story about software that matters

Breaking Things Down

With thanks toMichael James

Page 23: Liz September 2014. A story about software that matters

Fractal beauty

VisionGoal

Goal

Goal

Capability

Capability

Scenario

Scenario

Scenario

Feature

Feature

Feature

Story

Story

Code

Code

Code

Page 24: Liz September 2014. A story about software that matters

GoalScenario

Goal

Scenario

A Real Project

VisionGoal

Capability

Capability

Scenario

Scenario

Feature

Feature

Feature

Story

Code

Code

Code

Whoops,forgot

Oops, didn’t know about

that…Look what I

found!

Don’t need this… Can’t

remember what this was for…

Page 25: Liz September 2014. A story about software that matters

GoalStory

Goal

Scenario

A Real Project

VisionGoal

Capability

Capability

Scenario

Scenario

Feature

Feature

Feature

Story

Code

Code

Code

Whoops,forgot

Oops, didn’t know about

that…Look what I

found!

Don’t need this… Can’t

remember what this was for…

Um

Er…

Oh!

Oh F… Dammit!

Hmm!

That’s funny!

Ooh, look!

Interesting! Sh..!Oops!

Page 26: Liz September 2014. A story about software that matters

We are uncovering better ways of developing software by doing it

VisionGoal

Goal

Goal

Capability

Capability

Scenario

Scenario

Scenario

Feature

Feature

Feature

Story

Story

Code

Code

Code

Page 27: Liz September 2014. A story about software that matters

We’re discovering how to discover stuff by doing it

Whoops,forgot

Oops, didn’t know about

that…Look what I

found!

Don’t need this…

Can’t remember what this was for…

Um…

Er…

Oh!

Oh F… Dammit!

Hmm!

That’s funny!

Ooh, look!

Interesting!

Sh..!Oops!

Page 28: Liz September 2014. A story about software that matters

Different levels of granularity

Page 29: Liz September 2014. A story about software that matters

Testing Code

Do the examplesnow work?Developer

Page 30: Liz September 2014. A story about software that matters

Testing a Story

What do ourstakeholders

and userswant to change

about this?

Often adeveloper

Page 31: Liz September 2014. A story about software that matters

Testing a Feature

Is this usable?Does it

deliver thecapability?

UIDesigner

Page 32: Liz September 2014. A story about software that matters

Testing Scenarios

Does theapplication

producethe outcomewe expected?

Dev, tester,analyst

Page 33: Liz September 2014. A story about software that matters

Testing Capability

Can we dowhat we

wanted to do,for the contexts

in whichwe wanted to do it?

Business Analyst

Page 34: Liz September 2014. A story about software that matters

Testing a Goal

Does thismeet our

stakeholder’sgoal?

IncidentalStake-holder

Page 35: Liz September 2014. A story about software that matters

Testing a Vision

Did we:Make moneySave money

Protect money?

PrimaryStake-holder

Page 36: Liz September 2014. A story about software that matters

Estimating Complexity5 4 3

2

1

Breaking things down

Tryingthings

out

Page 37: Liz September 2014. A story about software that matters

There’s always oneRed

Page 38: Liz September 2014. A story about software that matters

How to doCapability Red

Page 39: Liz September 2014. A story about software that matters

Before you askwhy,askwho

Page 40: Liz September 2014. A story about software that matters

Identify your Stakeholders

Page 41: Liz September 2014. A story about software that matters

Gatekeepers vs. Educators

Page 42: Liz September 2014. A story about software that matters

Value Streams

Page 43: Liz September 2014. A story about software that matters

Draw up the capabilities

Don’t forget the integration points!

Page 44: Liz September 2014. A story about software that matters

Put complexity estimates on

1

4 2

5

Pay particular attention to 4s and 5s

Page 45: Liz September 2014. A story about software that matters

See if you can narrow the MVP

1 5

Only one 4 or 5.Companies with high transaction costs

for going live might not be able to do this.

Page 46: Liz September 2014. A story about software that matters

Estimate, if it’s useful

20

200400

Keeps the PMO happy

Page 47: Liz September 2014. A story about software that matters

Double the 4s and 5s

20

200400

Unless you can explain why not!

Page 48: Liz September 2014. A story about software that matters

High-level, risk-first

Page 49: Liz September 2014. A story about software that matters

Risk (Newest Stuff) First

VisionGoal

Goal

Goal

Capability

Capability

Feature

Feature

Feature

Story

Story

Story

Scenario

Scenario

Code

Code

Code

Feature

Goal

Capability

ScenarioCode

Story

Page 50: Liz September 2014. A story about software that matters

If your stakeholdersdon’t trust you,

that’syour biggest risk

Page 51: Liz September 2014. A story about software that matters

Liz Keoghhttp://lizkeogh.com@lunivore