AgileEE 2011: My Lightening Talk about "Definiton of READY"
Upcoming SlideShare
Loading in...5
×
 

AgileEE 2011: My Lightening Talk about "Definiton of READY"

on

  • 3,919 views

My lightening talk from Agileee 2011, Kiev about "Definition of READY".

My lightening talk from Agileee 2011, Kiev about "Definition of READY".
Presentation shows why it is important to have stories READY for a sprint and how to get stories ready.

Statistics

Views

Total Views
3,919
Views on SlideShare
1,835
Embed Views
2,084

Actions

Likes
0
Downloads
11
Comments
0

4 Embeds 2,084

http://www.armerkater.de 1566
http://www.agile-nearshoring.com 516
http://www.armerkater.de&_=1325493211607 HTTP 1
http://translate.googleusercontent.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

AgileEE 2011: My Lightening Talk about "Definiton of READY" AgileEE 2011: My Lightening Talk about "Definiton of READY" Presentation Transcript

  • Definition of READY Avoid Processing Crap.Agile Eastern Europe 2011, Kiev, September 2011 Felix Rüssel
  • Creating Value & Problem in SprintsHow Value is created Usual Problems in Sprints Understand WHY & WHAT  No clear description, criteria, goals Have a clue HOW to do  Not possble to test/evaluate if It CAN be done (READY!) goal has been met  Missing Dates It is being DONE (suprise!surpise!) It is really DONE And it is required  Risks unknown  Dependencies: Teams, external So it creates Value stakeholders, technical constrains, …  Owner (business sponsor) unknown
  • READY & DONE on the Scrum Board Sprint BacklogREADY DONE Committed Sprint Acceptance Planning Development Reviewed Testing (PO) Release
  • READY & DONE impediment READY DONE IncrePBL DoR SBL IBL DoD ment
  • 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 Story Template Add Details Sprint Backlog READY Committed Discuss! Discuss! Discuss! Sprint Planning Story Epic Story Story Story Story Story StoryDetails Details Details Details, Details, Details Acceptance Tests
  • Results & Rate of Adoption  Impact of READY on effort /  Definition of Ready / READY State variance  Discussion started on conferences: Beginning 2009  Adoption rate still very low Results of a small research Mailinglist „scrumdevelopment“  http://groups.yahoo.com/group/scrumd evelopment, August 2011  „definition of done“: 1001  „definition of ready“: 6  „ready state“: 14Source:http://agile2009.org/files/session_pdfs/Going%20from%20Good%20to%20Great%20with%20Scrum%20Session.PDF
  • 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