Sure you know that Definition of Done is cool and valuable thing. But what's inside and what are the major riffs to avoid when covering? Get aware with basics and than proceed. P.S.: This is 1.0 version piloting; extension commencing.

1. Understanding the Black-Box
Dmytro Bibikov
SoftServe
2015
v.1.0

2. Planning
Analysis
Design
Coding
Testing
Performance
Pilot
User Acceptance
Architecture,
Infrastructure

3. › Definition of Done [DoD] != Definition of Ready [DoR]
› Definition of Done [DoD] != Acceptance criteria [ACC]
› Conditions of Satisfaction [CoS]:
– usually messed with either DoR or ACC so be careful
› DoD / DoR / ACC – Which one is the Egg?

4. › Just enough of all (there is no silver bullet
formula for that)
› It’s better to live with uncertainty than
to embrace false certainty
› Extend it as you go
› Align all the parties to avoid trip to ‘no
mans land’
› Never pull anything into a sprint that is
not ready, and never let anything out of
the sprint that is not done

5. › DoR:
– In simple terms, a user story needs to meet some criteria before
it can be picked up for a sprint.
– Involved in defining DoR: Team, PO, SM.
– In DoR, the team is the "client" and the product owner is the
"supplier."
› What happens when Team starts without DoR?

6. › What you need to know for DoR on story level:
– Why - What are the stakeholders or the business trying to
achieve? What is their goal or outcome? What is the
business context?
– What - What is the outcome vision? What is the end result
of the user story?
– How - What is the strategy to implement the user story? Is
the story small enough (i.e., story points versus team
velocity)?

7. › ACC:
– The acceptance of this criteria means that AAA is enabled
when an incident BBB is submitted. - See more at
– Differs from story to story
– Only defines that set of functionality is shippable
› DoD:
– Clear and concise list of requirements that the user story must
satisfy for the team to call it complete
– Common for each and every backlog item
– Defines when the story is shippable

8. › DoD:
– The term applies more to the product increment as a whole
– In most cases, the term implies that the product increment is
shippable
– The term is defined in the Scrum Guide
– Used as a way to communicate the following to the PO: Overall
Software Quality; Whether the increment is shippable or not
› ACC:
– The term applies to an individual PBI/Story
– The Acceptance Criteria are different for each PBI/Story
– Term is not defined in the Scrum Guide
– Used as a way to communicate to all involved that the requirements for a
particular PBI/story have been met

9. › Where is our ACC?!

10. › DoD and DoR are long-term contract for all the parties
› ACC is supplementary agreement per feature
› Failure in setting things up leads to ‘no mans land’ case
› Who should align in
each case / who is
involved?

11. DoR Release Story Task
ACC Epic Feature Story
DoD Release PBI Task

12. › Talk to your mates and colleagues both
shores. You might find out you don’t need
a Definition of Done at all, only a
common Definition of Ready. Because ...
› Nothing is ever done, only ready for the
next step:
– DoR spread through all the SDLC layers can
substitute DoD

14. › https://scrumcrazy.wordpress.com/2011/03/05/termin
ology-definition-of-done-vs-acceptance-criteria/
› http://www.quora.com/What-is-the-difference-
between-the-Definition-of-Done-DoD-and-the-
Definition-of-Ready-DoR-in-Agile-processes
› http://www.allaboutagile.com/definition-of-done-10-
point-checklist/
› https://www.mountaingoatsoftware.com/blog/clarifyi
ng-the-relationship-between-definition-of-done-and-
conditions-of-sa
› http://guide.agilealliance.org/guide/definition-of-
ready.html