achieving ready ready user stories

Post on 22-Nov-2014

1.909 Views

Category:

Education

1 Downloads

Preview:

Click to see full reader

DESCRIPTION

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

TRANSCRIPT

Achieving ready-ready stories

Gil Nahmias, csp

Consider an organization

PO (BA)

Team

TeamPO (BA)

Chief PO

And a team Story Board

DefineEpics

Identify Stories

Elaborate + Add Acceptance Tests

Selected – READYREADY

Analyze Develop + TEST

Deploy DONEDONE

ABC

D

F E

GH

Who’s usually engaged?

DefineEpics

Identify Stories

Elaborate + Add Acceptance Tests

Selected – READYREADY

Analyze Develop + TEST

Deploy DONEDONE

ABC

D

F E

GH

And a team Story Board

DefineEpics

Identify Stories

Elaborate + Add Acceptance Tests

Selected – READYREADY

Analyze Develop + TEST

Deploy DONEDONE

ABC

D

F E

GH

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

After a while…

Ready Ready Story

Ready Ready Story

Ready Ready Story

Ready Ready Story

Ready Ready Story

Epic

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?

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?

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

Defect analysis

Defect analysis

Design Defect?

Implementation Defect?

Other Defect?

Requirement Defect?

Defect analysis

Design Defect?

Implementation Defect?

Other Defect?

.

.

.

Communication

Knowledge

Availability

Requirement Defect?

Retrospect to improve “Ready-Ready”

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

how to present it to the organization?

Presenting to the org - format

KPIOrg

support

Presenting to the org

KPIOrg

support

To provide direction

To help them achieve the goal

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”

Presenting to the org

Another example:

Lead time

More PO Availability

Lab time

Protect team when

reviewing DoD

That’s just a starting point

Start experimenting...

NOW!

Drop me a line

gil@agilesparks.com

myagile.co.il

top related