Common issue repeated in almost all Scrum teams is figuring out when a specific Product Backlog Item can be considered Done. What we haven't established but will be critical going forward is a commonly known and widely understood Definition of Done (DoD)
Let's focus first on what each goal / PBI should contain: Acceptance Criteria; this is a simple checklist explaining unambiguous deliverables required to consider the goal Done
Although each PBI is named so it can fit neatly in a straightforward question "Did you <PBI title here>?", answer is not always a simple Yes or No (providing a seam to exploit ;)) so it must be backed up by a more detailed acceptance criteria checklist
Who defines acceptance criteria?
Product Owners do. Scrum teams can help suggest goals based on Product Owner provided Epic stories, but Product Owner is directly responsible to define clear expectations for each PBI while grooming Product Backlog
How can we, the Scrum team, help?
Acceptance criteria is as important to a Scrum team as it is to Product Owner. By having clearly defined expectations it won't be possible for Product Owner to say: "Hey, you haven't delivered the product in a cardboard box which was obviously expected"
Just make sure that you are clear with all deliverable expectations while grooming the Product Backlog - ask your Product Owner for clarification on each unclear goal at this time. You cannot go back after you commit to PBIs in a new Sprint, Product Owner will expect to see deliverables in order to provide you with an OK in the end
What is the DoD then?
1) Present deliverable to Product Owner as soon as it is ready
2) Answer unambiguously Yes to all items in the acceptance criteria checklist
3) Get an OK from Product Owner
If you followed through with the three steps above, feel free to mark a PBI Done
No comments:
Post a Comment