Avoid definitions that indicate stories or projects need to meet extensive requirements to achieve a done state. Scrum teams strive to deliver a lean product and add to it incrementally based on a defined value chain.

The 'definition of done' indicates a level of quality a story or product must obtain before it is ready for release. For a user story, these requirements may state that the acceptance criteria must be met and the feature must pass sprint review. For a product release, it may require that the product be tested in development and test environments, the code is documented, the feature set has stakeholder approval, or the users are trained.

I would help a new Scrum team to understand that the definitions we decide on are flexible and should be in line with the governance of their company or industry. The criteria we define should add value, avoid risk, and avoid rework. I also encourage teams to consider integration points and develop criteria that assure that their releases do not adversely affect other systems or solutions. Finally, I help teams understand that they might need to reduce their story development capacity in some sprints to accommodate some of the criteria we define for the 'definition of done.'