Michael Vizdos

View Original

Scrum Commitment: Definition of Done in Scrum [Video]


See this content in the original post

Video: Scrum Artifact Commitment - Definition of Done

This is from the official 2020 Scrum Guide by Ken Schwaber and Jeff Sutherland.

sg20video_dod.mvizdos.com

sg20_playlist.mvizdos.com

Please share the links above with your friends, teams, leaders, and other stakeholders within your organization. You’ll get bonus points for sharing them on your social networks and internal slack channels.



Scrum Artifact Commitment - Definition of Done as defined in the official 2020 Scrum Guide

Commitment: Definition of Done

The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.

The moment a Product Backlog item meets the Definition of Done, an Increment is born.

The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment. If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review. Instead, it returns to the Product Backlog for future consideration.

If the Definition of Done for an increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product.

The Developers are required to conform to the Definition of Done. If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done.


References and Additional Learning Resources


WORK WITH MICHAEL VIZDOS

CONSULTING | TRAINING

ImplementingScrum.com

START | PRACTICE | COACH | LEAD