YDS: What is the Difference Between Acceptance Criteria and the Definition of Done?
ฝัง
- เผยแพร่เมื่อ 16 ต.ค. 2024
- What is the Difference Between the Acceptance Criteria and the Definition of Done? Let's explore the options this situation presents. All of this and more are discussed in today's episode of Your Daily Scrum with Todd Miller and Ryan Ripley.
What do you think? Let us know in the comments!
Take a Professional Scrum with Kanban Course with Todd, Ryan, and Daniel Vacanti!
www.eventbrite...
Buy Fixing Your Scrum: Practical Solutions to Common Scrum Problems -
amzn.to/3fMpH5a
Join Ryan and Todd in a Professional Scrum Master course:
www.scrum.org/...
And make sure you subscribe to the channel!
DISCLAIMER: Links included in this description might be affiliate links. If you purchase a product or service with the links that I provide, I may receive a small commission. There is no additional charge for you! Thank you for supporting the channel so we can continue to provide you with free content each week!
FTC DISCLAIMER: This video is not sponsored by anyone.
Sharing Scrum knowledge to help you grow as a Scrum Practitioner and to solve complex problems.
#scrum #agile #scrummaster
![[UNCUT]"ทนายตั้ม" แฉยับ! ความลับสวรรค์ ใครคือ "บิ๊กเทวดา" ของบอสพอล l คนดังนั่งเคลียร์ l 15 ต.ค. 67](http://i.ytimg.com/vi/ru9fpSaUwdA/mqdefault.jpg)
very well laid out!!! you guys explained it in 5 min...perfect for some quick videos to see at office lunch time
I’ve been coaching my POs to write acceptance criteria in the past tense and describing the done increment, instead of using verbs of what they will do. Rather than “Create an interactive exercise,” something like “Includes 3 minute interactive exercise.” It’s a subtle shift, but sometimes helps them visualize and then express the outcome, rather than the actions to get there.
That's a great idea. It's incredible how much a simple shift in language can help! Thanks for sharing, Robert!
At about 3:10 I feel like you explained it well.
I interpreted this as:
Acceptance criteria states how to build the right product backlog item
Definition of done is how to build the product backlog item right
A definition of done, could be that the acceptance criteria is met
So your product owner should lay out clear acceptance criteria, so that the scrum team (developers) can then break that down into tasks, with definitions of done - so it is done right.
@Todd: I've seen it somewhere as well. The one I've seen added an extra step though, and was based on accountabilities.
- Product owner: Build the right thing (related to prioritisation of PBI's in the Product Backlog, and stakeholder management/engagement)
- Development Team: Build the thing right (relates heavily on the Definition of done, and highlights the quality aspect)
- Scrum Master: Build it fast (relates to the process and especially the potential optimisation possibilities that can be found during Sprint Retrospective - I'm not sure I agree with this one though)
I love this - what a great summation of DoD and ACs 👏
Great Series on Applying empiricism on Artifacts in Scrum. Thanks a lot to AFH !
Inspiring, loved the visuals, simple and effective🧐 thank you Ryan and Todd
Well I've been treating these as the same thing for the last month 😅 whoops. To be fair I've not even gone on my CSM yet. Thanks for this. It is easy to remember.
Three Commitments and How they provide focus and EMPHASIZE Empiricism in Scrum execution? (Series !! :) )
Another great episode, guys!
I loved it, I'm going to teach this to my Scrum Team (phase forming just in case🥳 ), thanks @Agile for Humans, Absolutely valuable the video 🥳🥳🚀
6:07 - I heard this first from the book Unlocking Agility by Jorgen Hesselberg
Thank you! We always want to make sure we attribute references.
Great episode, but some new thinking from me.
Why is "building the RIGHT thing" optional, when "building the THING right" is a requried commitment?
..what if we built the wrong thing ... but we built the wrong thing RIGHT. Does it create value?
I think both of those statements are applicable "built the right thing, build the thing right"
Can we say then that AC is story specific while DOD applies to the increment?
Yes. We hope that message came through in the video. You are 100% correct!
So, the ACs are conditions on which the Product Owner will deem the user story (I'm assuming the team uses them) and accepted at the code review, while the DoD is a set of regulations/validations/a checklist for the increment (and as a result, the user stories outcome). That's how I would describe it. We shouldn't put into AC stuff that we already have in our DoD, while only specifics to this particular user story. Also, AC are a good first guess to slice a user story into smaller deliverable chunks, while the DoD is ONE and cannot be split. There is only one DONE :)
Yup, nailed it 👍