Webinar
/ Scaling Agile

Defining Done, Ready, and NO for Distributed Teams

David A. Koontz |  61m 43s

Earn Scrum Education Units (SEUs)

Earn credit towards renewing your certifications.

1 SEUs Earned
Log in to earn SEUs Log in
My SEUs
0 0
Log in to earn SEUs Log in
SEUs
1 SEUs Earned
My SEUs
0 0

The Scrum Guide is pretty clear on the criticality of the definition of Done: "When a Product Backlog item or an Increment is described as "Done," everyone must understand what "Done" means. However, the Scrum Guide ALSO says that the definition of Done can "vary significantly per Scrum Team." This lead us to examine when and how the definition of Done should vary, how distributed teams should create their definition of Done, and what other agreements can help the team be productive, including a definition of Ready and a definition of NO.

About the author

David A. Koontz
David A. Koontz is an Agile Transition Guide for organizations wishing to explore and discover their unique path to Lean/Agile software development. Previously a software engineer with 20+ years developing software solutions within a variety of industries. David uses his experience in group dynamics, systems thinking and the power of the Agile philosophy to unleash a team’s full potential. He enjoys mentoring individuals and coaching teams. David believes in empowering the team with self-organization, setting them on the path to achieve the team's purpose and providing them the proper intrinsic motivation to move the team along the productivity curve toward ultra performance. David has experience teaching Scrum and XP practices to multiple groups that evolved into Agile teams delivering quality software and value to customers.