In the context of PRINCE2 7, Quality Assurance (QA) is a governance function that operates independently of the project management team. Unlike Quality Control, which focuses on inspecting specific products to ensure they meet acceptance criteria, Quality Assurance focuses on the processes and stan…In the context of PRINCE2 7, Quality Assurance (QA) is a governance function that operates independently of the project management team. Unlike Quality Control, which focuses on inspecting specific products to ensure they meet acceptance criteria, Quality Assurance focuses on the processes and standards used to create those products. It provides confidence to corporate, programme, or portfolio management that the project is complying with the organization’s Quality Management System (QMS) and relevant policies.
A critical distinction in PRINCE2 is that the project management team is responsible for Quality Control (checking the products) and Project Assurance (checking the project’s performance on behalf of the Project Board), whereas Quality Assurance is generally an external corporate function. QA audits the project to ensure it is 'doing the right things in the right way.'
The primary roles of Quality Assurance within the Quality practice include:
1. **Process Compliance:** Verifying that the project is adhering to the organization’s standard processes, methods, and templates.
2. **System Effectiveness:** Checking that the quality management procedures defined in the Project Initiation Documentation are actually working and effective.
3. **Standardization:** Ensuring consistency across different projects within the portfolio.
While Project Assurance reports to the Project Board, Quality Assurance reports to the corporate or programme management organization. However, these roles often communicate to avoid duplication of effort. For example, Project Assurance might rely on QA reviews to confirm that the project's quality planning is robust. Ultimately, QA acts as the organization's independent watchdog, ensuring that the project does not deviate from broader corporate governance and that lessons learned are captured to improve future quality standards.
Mastering Quality Assurance in PRINCE2 Practitioner v7
What is Quality Assurance? In the context of PRINCE2, Quality Assurance (QA) is a function independent of the project management team. It provides a check that the project direction and management are adequate and that the project complies with relevant corporate, programme management, or customer standards and policies. While the project team focuses on delivering products (Quality Control) and the Project Board monitors the project's progress (Project Assurance), Quality Assurance ensures that the processes used to manage the project are working correctly and adhere to the organization's Quality Management System (QMS).
Why is it Important? Quality Assurance is vital because it provides confidence to corporate, programme management, or the customer that the project is being conducted appropriately. It ensures that: 1. The project is consistent with organizational standards. 2. Lessons learned are being applied and captured. 3. The project is not deviating from the wider organizational governance requirements.
How it Works QA activities are typically planned and performed by a dedicated quality department or function within the corporate or programme organization. They are not part of the project management team. Their activities might include: - Auditing the project's use of PRINCE2 and internal standards. - Reviewing the Quality Management Approach to ensure it aligns with corporate policy. - Providing independent feedback to corporate management regarding the project's compliance.
Quality Assurance vs. Project Assurance The most common area of confusion in PRINCE2 is distinguishing between Quality Assurance and Project Assurance. - Quality Assurance: Independent of the project. Responsible to the Corporate/Programme Management. Checks compliance with corporate standards. - Project Assurance: A responsibility of the Project Board. Checks that the project is viable and delivering for the business, user, and supplier interests. It is internal to the project's governance structure.
How to Answer Questions on Quality Assurance When facing a Practitioner scenario regarding Quality Assurance, follow these steps: 1. Identify the Actor: Is the person performing the check a member of the Project Board, or are they from an external corporate department? If they are external/corporate, it is likely Quality Assurance. 2. Identify the Object: Are they checking a specific product for defects (Quality Control), checking the project's business justification (Project Assurance), or checking if the project manager is following the correct corporate processes (Quality Assurance)? 3. Check the Hierarchy: QA reports to Corporate/Programme management, not the Project Manager.
Exam Tips: Answering Questions on Quality Assurance - Look for 'Independent': If the scenario mentions an 'independent check' initiated by the corporate organization, think QA. - Standards and Policies: If the question is about aligning the project with the 'Corporate Quality Management System' (QMS), this involves QA. - The Trap: Do not confuse QA with the Senior Supplier's responsibility for technical quality. The Senior Supplier provides Project Assurance from a supplier perspective; QA provides process assurance from a corporate perspective. - Terminology: In PRINCE2, the Project Board is responsible for Project Assurance, but they may ask Quality Assurance personnel to assist them. However, the accountability for Project Assurance remains with the Board, while QA remains a corporate function.