Program Quality Management: Seven Checks Every Programme Needs
Program quality management means planning, auditing, trending and reporting quality across all of a programme's projects, so outcomes meet strategy and deliver benefits, rather than inspecting each project's deliverables individually.
By Sanjeev Kumar, Founder · Updated 19 Nov 2026

Key takeaways
- Programme quality management is the programme manager's work of planning, auditing, trending, change-controlling and reporting quality across every project. Testing deliverables stays with the project teams.
- In PMI's PgMP outline, 7 of 72 tasks mention quality. None asks the programme manager to inspect anything.
- Seven yes-or-no checks, each with a pass and a fail test, show where your programme's quality management is thin.
- Independent assurance, meaning someone outside the delivery teams checking that quality planning and controls exist, is the check programmes find hardest to pass, because the people who plan and deliver are often the people who report.
In this article
- 1How can you test your programme's quality management in seven checks?
- 2Does one programme quality plan roll up every project's plan? (Program Life Cycle, Task 9)
- 3Are quality indicators defined once for the whole programme? (Task 14)
- 4Does someone outside the project teams audit the results? (Task 21)
- 5Is quality trended beside cost and schedule? (Task 25)
- 6Does every change request state its effect on quality? (Task 28)
- 7Does the closing report compare final quality with plan? (Task 31)
- 8Does the governance board see quality KPIs next to benefits? (Governance, Task 4)
- 9What does your score tell you?
- 10Where does quality appear in PMI's PgMP® outline?
- 11What does programme quality management involve above project level?
- 12Why do project quality guides leave a programme manager short?
- 13Who should own quality when every project manager owns their own?
- 14How do we help you prepare for the PgMP® quality tasks?
- 15Frequently asked questions
A programme manager sits somewhere other than the project teams, one level above the individual projects. Each project already has its own quality plan and its own testers, and the programme manager is asked a different question: does the sum of all this deliver what the programme was set up for?
PMI, the Project Management Institute, points to an answer in its outline for the Program Management Professional (PgMP®) exam. Quality is treated as a set of programme-level decisions and reviews, not as inspection work. That is a useful way to organise your own programme, whether or not you ever sit the exam.
Five projects can each pass their own quality checks while the programme still misses its benefits, because each check stopped at its own project's boundary. The gap between those two results is where programme quality management has to work, and the seven checks that follow test whether your programme covers it.
How can you test your programme's quality management in seven checks?
Run the seven checks below against your own programme documents. Score one point for each pass. A check passes only if you can point to a document or record, not if the practice is "understood". The pass and fail tests are our recommendation; the outline wording only supplies the task each check follows.
Does one programme quality plan roll up every project's plan? (Program Life Cycle, Task 9)
Pass: one approved document names each project's quality plan and the common standard they must meet. Fail: each project holds its own plan and nobody has compared them. The outline asks for plans for supporting programme functions, "for example, quality, risk, communication, and resources", to be integrated with the plans for the constituent projects.
Are quality indicators defined once for the whole programme? (Task 14)
Pass: each key performance indicator (KPI) has a written definition, a unit, an owner and a threshold, and every project reports it the same way. Fail: two projects both report "defect rate" but count it differently. The outline asks for KPIs that implement a scope and quality management system within the programme.
Does someone outside the project teams audit the results? (Task 21)
Pass: a named auditor with no delivery role in the audited project, a schedule of audits and a log of findings. Fail: project managers only self-report. The outline asks for the quality, risk, communication and resourcing plans to be executed "by auditing the results", so that outcomes align with strategy and deliver the expected benefits.
Is quality trended beside cost and schedule? (Task 25)
Pass: quality variance sits in the same report as cost and schedule variance, as a trend (values tracked over successive reporting periods) and not only the latest value. Variance is the gap between planned and actual values. Fail: quality gets discussed only after a defect escapes. If you already compute cost and schedule variance, our earned value formula guide shows the programme roll-up to put beside it.
Does every change request state its effect on quality? (Task 28)
Pass: the change form has a mandatory quality-impact entry, and no change is approved with it blank. Fail: changes are assessed for cost and date only. The outline lists quality alongside scope, schedule, cost, contracts, risks and rewards as things changes must control. See programme change management for who owns adoption.
Does the closing report compare final quality with plan? (Task 31)
Pass: the programme performance report sets final values against planned values for scope, quality, cost, schedule and resources. Fail: the closing report covers budget and dates only. Our programme closure guide has a gate sheet for the handover.
Does the governance board see quality KPIs next to benefits? (Governance, Task 4)
Pass: the pack for each stage gate includes quality KPIs alongside benefits indicators. A stage gate is a formal review at which the governance board decides whether the programme proceeds to the next phase. Fail: the board sees schedule and spend only. The outline lists quality among the indicators evaluated to monitor benefits across the life cycle, and Task 3 ties approvals to stage gate reviews. Our stage gate process guide covers who decides at each gate.
What does your score tell you?
Our recommendation, not an official scale:
- 6 or 7: the structure is sound, so spend your effort on the quality of the evidence.
- 3 to 5: fix checks 1 to 3 first, because a shared plan, shared definitions and independent audit are what make the later reports trustworthy.
- 0 to 2: start with a single page that defines three KPIs for every project, then add an audit.

Where does quality appear in PMI's PgMP® outline?
Quality appears in 7 of the 72 tasks in PMI's PgMP Examination Content Outline. The March 2024 outline lists 72 tasks in total. We searched their wording for "quality" and found it in 7: tasks 9, 14, 21, 25, 28 and 31 in Program Life Cycle Management and task 4 in Governance.
The April 2011 edition names quality in the same seven tasks. The planning, executing, controlling and closing split comes from that edition's subdomains, which the March 2024 edition does not use. On that split the tasks fall as:
- planning (two)
- executing (one)
- controlling (two)
- closing (one)
- governance (one)
Initiating has none.
None of the seven asks a programme manager to inspect or test a deliverable. Quality control appears only in the knowledge list, as "Quality control and management tools and techniques", something the candidate must understand, not a task to perform. The programme-level verbs are plan, define indicators, audit, analyse variance, control change, report and review.
The two domains carry 44% (Program Life Cycle Management) and 14% (Governance) of the exam. Those weights are for the whole domains, not for quality alone.
What does programme quality management involve above project level?
Programme quality management involves the five components of quality management, applied across every project in the programme: a quality management system, independent quality assurance, quality planning, quality control and quality reviews (Department of Finance, Northern Ireland). Its definitions are worth keeping:
- Quality control is "the means of ensuring that the specified quality criteria are met".
- Independent quality assurance "independently checks that quality planning and controls are in place".
- A quality management system is the structures, procedures and processes an organisation uses to implement quality management.
For a programme, that page adds an "overarching view of the outputs of all the projects in a programme". That overarching view is the job. A programme is a group of related projects managed together to deliver benefits that none would deliver alone. Quality there means the combined outcome, not only each product.
Why do project quality guides leave a programme manager short?
Project quality guides stop at the project boundary, so they say little about what to do when five projects each pass their own checks and the programme still misses its benefits. In our reading, the five components above are a project-level model. A programme inherits them, but nobody in a project owns the integration.
Two confusions follow. The first is mixing up the organisation's quality management system with a programme's quality plan. The system is the standing structure. The plan is what this programme decides to measure, audit and report. Our recommendation: treat the organisation's system as an input, and write the programme's quality plan as yours.
The second confusion is deciding who checks. Quality control belongs with the project teams, because the Northern Ireland guidance gives the project manager the job of implementing it. Assurance is different: it checks the checking. If the same people plan, control and assure, nobody is assuring anything.
Who should own quality when every project manager owns their own?
Everyone delivering shares quality, but one person should be accountable for the programme's quality plan and audits. The Northern Ireland guidance calls quality "the collective responsibility of everyone on a project", while making the project board ultimately responsible for project assurance.
Our recommendation for a programme is to name the programme manager for checks 1 to 6 and the governance board for check 7. Accountability is easy to lose across several projects, because each project manager can honestly say their own quality is fine.

How do we help you prepare for the PgMP® quality tasks?
If you are working towards the PgMP® credential, we prepare you for these programme-level tasks through our PgMP® Self-Paced Mentorship Program. It provides structured learning, application guidance and exam preparation at your own pace. It includes studio-recorded video modules, recorded Q&A sessions, mind maps and 1,000+ exam-preparation questions with detailed explanations. The programme page lists modules on the programme life cycle and governance, the two domains where the quality tasks sit.
We also offer PgMP® Fast Track, a focused group mentoring programme, and PgMP® Application Writing Support, which helps you prepare, structure and review your application before you submit it to PMI. Application feedback continues until your application is approved. The seven checks above are also a practical way to recall the programme-level work you will need to describe.
As of November 2026, the PgMP® Self-Paced Mentorship Program costs US$549 per enrolment, PgMP® Fast Track US$1,000 and PgMP® Application Writing Support US$199. Pricing varies by programme and market, and enrolment is per programme, not a subscription.
Across our programmes we have mentored or trained 6,000+ professionals, with a 98.5% first-attempt success rate. The 98.5% first-attempt success rate is explained in our methodology note, including who is counted and the period covered.
Questions about a programme go to support@augmentconsultancy.com or +91 9816 360 116 (phone or WhatsApp). Book a free discovery consultation, available before enrolment, to check suitability, then enrol through the course store.
Frequently asked questions
Sources
- 1.PgMP® Examination Content Outline, March 2024, Project Management Institute
- 2.PgMP® Examination Content Outline, April 2011, Project Management Institute
- 3.Programme and project quality management, Department of Finance, Northern Ireland
- 4.PgMP® Self-Paced Learning, Augment Consultancy



