Definition of Done

The purpose of each Sprint is to deliver Increments of potentially releasable product functionality that adhere to the definition of "Done". The DoD is consistent across all Stories and drives the quality of work used to assess when a Story is Done. Each product has a definition of "Done" that is part of the conventions, standards or guidelines of the organization which must be followed by all Scrum Teams.

When a Product Backlog item or an Increment is described as "Done", everyone must understand what "Done" means. Although this may vary significantly per Scrum Team, members must have a shared understanding of what it means for work to be complete, to ensure transparency. This is the definition of "Done" for the Scrum Team and is used to assess when work is complete on the product Increment.

• DoD guides the Delivery Team in knowing how many Product Backlog items it can select during a Sprint Planning.

• Each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team’s current definition of "Done".

• Delivery Teams deliver an Increment of product functionality every Sprint. This Increment is useable, so a Product Owner may choose to immediately release it.

• If the definition of "Done" for an increment is part of the conventions, standards or guidelines of the Delivery organization, all Scrum Teams must follow it as a minimum.

• Each Increment is additive to all prior Increments and thoroughly tested, ensuring that all Increments work together.

As Scrum Teams mature, it is expected that their definitions of "Done" will expand to include more stringent criteria for higher quality. New definitions, as used, may uncover work to be done in previously "Done" increments. Any one product or system should have a definition of "Done" that is a standard for any work done on it.