A project manager is working on a project that is using an agile approach. The project manager wants to ensure that the team delivers high quality. What should the project manager do?

While establishing a clear definition of done is important for ensuring that user stories meet certain criteria before they are considered complete, this practice alone does not emphasize the importance of ongoing testing throughout the project lifecycle. The DoD acts as a guideline but does not inherently ensure high quality if testing is not integrated early and continuously.

User acceptance testing (UAT) is a critical step that typically occurs at the end of the development cycle to validate that the product meets user needs. However, relying solely on UAT does not support high quality in an agile context. Quality should be built into the process from the beginning, rather than being assessed only at the end.

While user-driven development and automated testing are beneficial practices that can enhance quality, simply implementing these elements without ensuring early and continuous testing does not guarantee that high-quality outcomes are achieved. Quality assurance needs to be woven throughout the project, not just added in as a feature.