Your SlideShare is downloading. ×
0
Lightening Talk: definition of ready
Lightening Talk: definition of ready
Lightening Talk: definition of ready
Lightening Talk: definition of ready
Lightening Talk: definition of ready
Lightening Talk: definition of ready
Lightening Talk: definition of ready
Lightening Talk: definition of ready
Lightening Talk: definition of ready
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Lightening Talk: definition of ready

2,655

Published on

Published in: Technology, Sports
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
2,655
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
25
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Definition of READYWhen are you able to start? Agile Eastern Europe 2011, Kiev, September 2011 Felix Rüssel
  • 2. Creating Value & Problem in SprintsHow Value is created Usual Problems in Sprints Understand WHY and  No clear description, criteria, goals WHAT to do  Not possble to test/evaluate if Have a clue HOW it be can goal has been met It CAN be done (READY!)  Missing Dates (suprise!surpise!) It is being DONE It is really DONE  Risiks unknown  Dependencies: Teams, external And it is required stakeholders, technical constrains, … So it creates Value  Owner (business sponsor) unknown
  • 3. READY & DONE on the Scrum Board Sprint BacklogREADY DONE Committed Sprint Acceptance Planning Development Reviewed Testing (PO) Release
  • 4. READY & DONE impediment READY DONE IncrePBL DoR SBL IBL DoD ment
  • 5. READY as Quality Gate READY as pre-condition for „Hyperproductivity“ Responsible: Product Owner  May delegate work to make stories READY Team: Has right during Planning to refuse to commit on stories that are not READY Scrum Master enforces rules  Helps PO to increase the rate of READY stories  Scrum Master interferes when non-READY stories are discussed in a wild manner.
  • 6. How Product Backlog should look like Current Sprint (Stories, Tasks) READY (Stories) Preparing (Epics -> Stories) NEW (Ideas, Epics, Themes)
  • 7. 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
  • 8. Results & Rate of Adoption  Impact of READY on effort /  Definition of Ready / READY State variance  Discussion started on conferences: Beginnig 2009  Adoption rate still very low Results of a small research Mailinglist „scrumdevelopment“  http://groups.yahoo.com/group/scrumd evelopment  „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
  • 9. WHO?Felix Rüssel  Consultant for agile Methods, 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

×