What do you mean I need to write down what it means for work to be ready and done? That's pretty obvious, isn't it Klint??

Jeez, Klint...



Well guess what? Klint is right. How your team defines work that is ready to be picked up and when exactly it is fully completed may differ from the team next to you...and it should!



On this episode, Brian Tomlinson, Transformation Architect at Red Hat, joins us to talk about the importance of clearly defining when work is ready and done for your specific team - and how to do it. So take a danged break from your computer screen or phone and give it a listen already!

For this and other awesome team practices, check out the Open Practice Library for yourself! openpracticelibrary.com 🧙‍♀️🌠

=====

Definition of Ready

Definition of Done

Bearded Beaver

Referenced Practices:

Priority Sliders

Social Contract

Measuring Psychological Safety

Parking Lot

Start at the End

Red Hat Blog Series

DevOps Culture & Practice with OpenShift Book

=====

Hit us up on Twitter: @practicelibrary

Connect with Brian:

LinkedIn

Twitter

Blog

Connect with Matt 🧙‍♂

LinkedIn

Twitter

Connect with Jerry 🕺

LinkedIn

Twitter

=====

If you're liking this podcast so far, please review us on your fav podcast platform 👯