As we were talking about the Definition of Done, it got some conversations going to talk about the Definition of Ready. Does your team have a definition of ready for your stories? What do you include in your definition? Acceptance Criteria?Test Cases? Has your team looked into creating a Definition of Ready? Do you use this DoR as a guideline to know when a story is ready to be worked on?

One possible outcome of spending time gathering Acceptance Criteria for stories is that you have now collected information that can be easily used as test cases. How else do you go about gathering test cases? Some things to think about when writing test cases: Test Cases need to be simple and transparent Test Cases can & should be written by everyone(different people provide different perspective) Tests should be able to be rerun and always produce the same results

Last week I asked questions about Definition of Done, one item that should probably be part of every DoD is Acceptance Criteria. Last week I left a lot of question with no answers, this week, I’m going to provide a few thoughts along with my questions. When do you write your acceptance criteria? Backlo What is the point of acceptance criteria? define boundaries get consensus and understanding of story serve as a basis for tests help with planning and estimations get definition of expectations of product owner What must Acceptance criteria include?

When do I consider things done? Does everyone on my team know what it means for something to be considered done? Do we have a Team Definition of Done? Do we always follow the DoD? Do I speak up if I don’t think everything is really done? Do we see value in our DoD? Are there additional things that we can do to improve the quality of what we deliver?