• Scrum
    • Scrum introduction
    • Scrum Artifacts
    • Scrum Events
    • Scrum Roles
    • Scrum Timeline
  • Project management
  • Professional Scrum Master Guide
  • Project management Guide
  • PM Books
  • Scrum
    • Scrum introduction
    • Scrum Artifacts
    • Scrum Events
    • Scrum Roles
    • Scrum Timeline
  • Project management
  • Professional Scrum Master Guide
  • Project management Guide
  • PM Books
  • Home
  • Scrum
  • Definition of Done
Categories:
  • Scrum
  • Scrum artifacts

Definition of Done

Mat Siems

December 30, 2016
Like 0
Categories:
  • Scrum
  • Scrum artifacts
SHARE THIS PAGE

Definition of Done

Discover shared understanding of done, decided by Scrum Team, might have mulitiple DOD across different team of same project,

DOD description:

  • There should be a shared understanding of what it means for a piece of work to be Done.
  • This definition of Done must be discussed and agreed upon by the Scrum Team at the beginning of the project so that future Increments would be releasable.
  • When multiple Scrum Teams are working on a single project, it might not be possible to use the same definition of Done for all teams (might be working on items of different natures) so  each Scrum Team will define its own definition of Done and delivers its items based on that definition.
  • The integration of those definitions of Done should be capable of creating a potentially releasable Increment in the project level.

Get the book

Tags:
  • decided by Scrum Team
  • might have mulitiple DOD across different team of same project
  • shared understanding of done
SHARE THIS PAGE

Mat Siems

Related Posts

Successful Project Manager - Art and Science of shipping products

Share it on your social network:

Or you can just copy and share this url