Where are the quality measures for the product formally described?

The Definition of Done is a crucial element in the Scrum framework that specifies the quality measures for the product. It outlines the criteria that must be met for the product increment to be considered complete. This includes aspects such as coding standards, testing requirements, documentation, and any other relevant measures that ensure the product is of high quality and ready for release.

Having a clear and comprehensive Definition of Done helps the Scrum Team understand the expectations regarding quality and ensures consistency across increments. By having these quality measures formally described in the Definition of Done, the team avoids ambiguities regarding what "done" truly means, which ultimately leads to delivering a product that meets stakeholder expectations and maintains high quality.

In contrast, Quality Guidelines may offer practices or standards for ensuring quality, but they are not as formalized or specific as the Definition of Done. The Product Roadmap focuses on the strategic direction and features planned over time, rather than detailing quality measures. User Stories capture customer requirements but do not directly address the quality criteria for those requirements. Thus, the Definition of Done is the most appropriate and effective place for formally describing the quality measures for the product.