## 4.7 Quality PM2-Agile references two different but complementary quality types – the quality of the development process and the quality of the outputs of the process. As PM2 states, project quality management aims to ensure that the project will meet the expected results in the most efficient way and that the deliverables will be accepted by the relevant stakeholders. Quality is the result of collaborative work, common understanding and empathy between all the stakeholders. It is an indicator of success, when the end user perceives the outputs of the process as useful and intuitive. In PM2- Agile, the quality of the development process is managed by tailoring the approach that best fits the project environment and by frequently involving the whole Agile Project Core Team (A-PCT), the Business Manager (BM) and the User Representatives during each timeboxed cycle of work. Altogether, they must focus exclusively on generating outcomes that will be perceived as valuable by the Project Owner’s organisation. To achieve fit-for-purpose deliveries, close collaboration between the Project Owner (PO) and the Solution Provider (SP) organisations along with the use of Agile tools and techniques is necessary. Timeboxed cycles of work and frequent user demos provide the time and space for collaborative improvement. This allows the Agile Project Core Team (A-PCT) to assess if the solution is heading in the desired direction by providing maximum value to the business stakeholders.