Definition of READY Avoid Processing Crap.

Agile Eastern Europe 2011, Kiev,

September 2011 Felix Rüssel

Creating Value & Problem in Sprints

How Value is created

Understand WHY & WHAT

Have a clue HOW to do

It CAN be done (READY!)

It is being DONE

It is really DONE

And it is required

So it creates Value

Usual Problems in Sprints No clear description, criteria,

goals Not possble to test/evaluate if

goal has been met Missing Dates

(suprise!surpise!)

Risks unknown Dependencies: Teams, external

stakeholders, technical constrains, …

Owner (business sponsor) unknown

READY & DONE on the Scrum Board

Sprint Planning

Acceptance Testing (PO)

REA

DY

Release Development Reviewed

DO

NE

Co

mm

itte

d

Spri

nt

Bac

klo

g

READY & DONE

REA

DY

DO

NE

PBL SBL Increment

imp

ed

ime

nt

DoR IBL DoD

READY as Quality Gate

READY as pre-condition for „Hyperproductivity“ Jeff Sutherland

Responsible: Product Owner May delegate work to make stories READY

Team: Might refuse not READY stories during Planning

Scrum Master enforces rules Helps PO to increase the rate of READY stories

Scrum Master interfers when non-READY stories are discussed in a wild manner.

Product Backlog

Current Sprint (Stories, Tasks)

READY (Stories)

Preparing (Epics -> Stories)

NEW

(Ideas, Epics, Themes)

How it becomes READY

Sprint Planning

REA

DY

Co

mm

itte

d

Spri

nt

Bac

klo

g

Story Story

Details Details

Details, Details, Details

Acceptance Tests

Details

Epic

Story Story

Story

Story

Story

Story Template

Add Details

Discuss! Discuss! Discuss!

Source:

http://agile2009.org/files/session_pdfs/Going%20from%20Goo

d%20to%20Great%20with%20Scrum%20Session.PDF

Results & Rate of Adoption

Impact of READY on effort / variance

Definition of Ready / READY State Discussion started on conferences:

Beginning 2009 Adoption rate still very low

Results of a small research Mailinglist „scrumdevelopment“

http://groups.yahoo.com/group/scrumdevelopment, August 2011

„definition of done“: 1001

„definition of ready“: 6 „ready state“: 14

WHO?

Felix Rüssel Consultant for agile, project management and virtual

teams www.agile-rescue.com

Nearshore Scrum Teams www.agile-nearshoring.com

Agile methods since 2004 German Blog (~2008): www.armerkater.de