achieving ready ready user stories

20
Achieving ready-ready stories Gil Nahmias, csp

Upload: gil-nahmias

Post on 22-Nov-2014

1.909 views

Category:

Education


1 download

DESCRIPTION

How to get Ready-Ready user stories in agile? Software requirements made easy

TRANSCRIPT

Page 1: Achieving Ready Ready User Stories

Achieving ready-ready stories

Gil Nahmias, csp

Page 2: Achieving Ready Ready User Stories

Consider an organization

PO (BA)

Team

TeamPO (BA)

Chief PO

Page 3: Achieving Ready Ready User Stories

And a team Story Board

DefineEpics

Identify Stories

Elaborate + Add Acceptance Tests

Selected – READYREADY

Analyze Develop + TEST

Deploy DONEDONE

ABC

D

F E

GH

Page 4: Achieving Ready Ready User Stories

Who’s usually engaged?

DefineEpics

Identify Stories

Elaborate + Add Acceptance Tests

Selected – READYREADY

Analyze Develop + TEST

Deploy DONEDONE

ABC

D

F E

GH

Page 5: Achieving Ready Ready User Stories

And a team Story Board

DefineEpics

Identify Stories

Elaborate + Add Acceptance Tests

Selected – READYREADY

Analyze Develop + TEST

Deploy DONEDONE

ABC

D

F E

GH

Page 6: Achieving Ready Ready User Stories

And a team Story Board

DefineEpics

Identify Stories

Elaborate + Add Acceptance Tests

Selected – READYREADY

Analyze Develop + TEST

Deploy DONEDONE

ABC

D

F E

GH

“customer” of the column = team

Page 7: Achieving Ready Ready User Stories

After a while…

Ready Ready Story

Ready Ready Story

Ready Ready Story

Ready Ready Story

Ready Ready Story

Epic

Page 8: Achieving Ready Ready User Stories

Definition of ready

Ready Ready Story Qualit

y

QuantityAre there just enough stories waiting on the team to develop?

Do the stories form a good viable software?

Page 9: Achieving Ready Ready User Stories

Definition of ready

Ready Ready Story Qualit

y

Quantity

Relevance

Achievability

Is the story aligned with the epic / business goal?

What are the chances of completing the story in time?

Page 10: Achieving Ready Ready User Stories

Ideas for “Ready-ready” process

Ready Ready Story Qualit

y

Quantity

Relevance

Achievability

1-2 sprints worth ahead

- Approve by Chief

PO- Prioritize

- INVEST + “As a..” syntax- Can be estimated by team in < 15min- Estimated in < 5 days- Lead time < 5 days- Tests & AT defined- Approve API / UI mockups- Approve by Team- Measure % time story was actually worked on

Page 11: Achieving Ready Ready User Stories

Defect analysis

Page 12: Achieving Ready Ready User Stories

Defect analysis

Design Defect?

Implementation Defect?

Other Defect?

Requirement Defect?

Page 13: Achieving Ready Ready User Stories

Defect analysis

Design Defect?

Implementation Defect?

Other Defect?

.

.

.

Communication

Knowledge

Availability

Requirement Defect?

Retrospect to improve “Ready-Ready”

Page 14: Achieving Ready Ready User Stories

?Now, when we know what we want to do,

how to present it to the organization?

Page 15: Achieving Ready Ready User Stories

Presenting to the org - format

KPIOrg

support

Page 16: Achieving Ready Ready User Stories

Presenting to the org

KPIOrg

support

To provide direction

To help them achieve the goal

Page 17: Achieving Ready Ready User Stories

Presenting to the org

For example:

Story can be estimated by team in 15 mins

PO gets time to

learn the needs betterTech guru

avail in planning

Practice “Sniffing Era”

Page 18: Achieving Ready Ready User Stories

Presenting to the org

Another example:

Lead time

More PO Availability

Lab time

Protect team when

reviewing DoD

Page 19: Achieving Ready Ready User Stories

That’s just a starting point

Start experimenting...

NOW!

Page 20: Achieving Ready Ready User Stories

Drop me a line

[email protected]

myagile.co.il