✅ Quality, Communication & Stakeholder Management
Study Notes — Page 6 | ClearPMPExam.com
Part A — Quality Management
Quality Management ensures that project deliverables meet the required standards — that you build the right thing correctly, and that the customer gets what they actually need.
Quality in PMP is not about making something perfect. It is about meeting agreed standards — no more, no less. Adding extra features or polish beyond what was agreed is called gold plating and is discouraged. The PMP philosophy is: build exactly what was promised, to the standard agreed, with zero defects.
🏥 Real Example — Pharma Campaign Materials
The client approved campaign materials that must pass medical accuracy review, follow CDSCO guidelines, and be reviewed by a medical writer. Quality Management ensures these standards are defined upfront, processes are followed, and each deliverable is inspected before delivery.
👉 If the team adds extra animations the client didn’t ask for — that’s gold plating. If they skip the medical accuracy review — that’s a quality failure. Both are problems.
1. The 3 Quality Processes — Plan, Manage, Control
Quality Management has three processes that happen at different stages of the project. The exam constantly confuses Manage Quality and Control Quality — know them precisely.
Plan Quality Management
Identify which quality standards are relevant and decide how to meet them. Define what “done correctly” looks like before work starts.
Output: Quality Management Plan, Quality Metrics
Manage Quality
Audit the processes being used — are the team following the right methods? Are standards being applied correctly? Focus is on HOW work is done.
Output: Quality Reports, Test & Evaluation Documents
Control Quality
Inspect the actual deliverables — do they meet the agreed standards? Focus is on WHAT was produced. Defects are identified here and sent for rework.
Output: Quality Control Measurements, Verified Deliverables
Manage Quality = auditing the PROCESS (“are we following the right steps?”) → Executing.
Control Quality = inspecting the PRODUCT (“does this deliverable meet standards?”) → Monitoring & Controlling.
Process first, product second. Audits in Executing, Inspections in Monitoring.
Manage Quality = Managing HOW it’s done (process audit). Control Quality = Controlling WHAT came out (product inspection). Manage = Method. Control = Check.
2. Cost of Quality (COQ) — What It Actually Means
Cost of Quality is the total cost of all activities related to quality — both the cost of achieving quality AND the cost of failing to achieve it.
COQ has two sides — the money you spend to prevent problems (good) and the money you lose when things go wrong (bad). The PMP philosophy is always: invest more in prevention because it is always cheaper than fixing failures later.
✅ Cost of Conformance — Money WELL spent
Prevention Costs
Doing it right the first time. Training, process documentation, quality planning, design reviews.
Appraisal Costs
Checking the work. Testing, inspections, audits, peer reviews before delivery.
❌ Cost of Non-Conformance — Money WASTED
Internal Failure Costs
Defects found before delivery. Rework, scrap, re-testing. Costs the team time and money.
External Failure Costs
Defects found by the customer after delivery. Warranty claims, reputation damage, legal liability. Most expensive of all.
Prevention costs < Appraisal costs < Internal failure costs < External failure costs. Money spent preventing defects is always cheaper than fixing them later — especially after the customer has seen them. The PMP always recommends investing in prevention.
3. Key Quality Tools — Know What Each One Does
These tools appear in both Plan Quality and Control Quality. The exam gives you a scenario and asks which tool is being used.
Ishikawa / Fishbone / Cause & Effect Diagram
Identifies the root causes of a problem. The defect is the “fish head” — the bones show all possible causes. Used in root cause analysis.
Pareto Chart
80/20 rule — 80% of problems come from 20% of causes. Bar chart ranked from most to least frequent. Focus your fix on the tallest bars first.
Control Chart
Tracks process performance over time against upper and lower control limits. If a data point goes outside the limits → process is out of control → investigate.
Histogram
Bar chart showing frequency distribution of data. Shows how often defects occur in each category. Good for spotting patterns in defect data.
Checklist
Structured list of items to verify. Ensures nothing is missed during inspection or process execution. Simple but powerful.
Scatter Diagram
Shows the relationship between two variables. If dots cluster along a line — there is a correlation. Used to test whether one thing causes another.
“Root cause of defect” → Fishbone / Ishikawa. “80% of problems from 20% of causes” → Pareto. “Process within limits?” → Control Chart. “Frequency of defects” → Histogram. “Relationship between two variables” → Scatter Diagram.
4. Gold Plating — Why It’s Wrong in PMP
Gold plating is adding extra features, functionality, or quality beyond what was agreed in the scope — without the client asking for it and without going through change control.
It sounds like a good thing — “we’re giving the client more than they asked for!” But in PMP, gold plating is a problem because it wastes time and budget, changes scope without approval, may introduce new defects, and sets unrealistic expectations for future projects. The right thing to do is deliver exactly what was agreed — nothing more, nothing less.
Exam rule: If the team adds unrequested features → that is gold plating → the PM should stop it. Any addition to scope — even a beneficial one — must go through formal change control first.
Part B — Communication Management
Communication Management ensures the right information reaches the right people at the right time in the right format. Studies show PMs spend up to 90% of their time communicating.
5. The Communication Channels Formula — Memorise This
This formula appears in almost every PMP exam. It calculates how many communication channels exist for a given team size. The more people, the exponentially more channels — showing why large teams are hard to manage.
Number of communication channels
Where n = number of people on the project team
🧮 Worked Example — Team Grows from 5 to 8 People
The exam gives two scenarios: “How many channels do 10 people have?” (single calculation) OR “Team grew from 5 to 8 — how many NEW channels were added?” (two calculations, subtract). Always calculate both before answering the second type.
6. Types of Communication — Know the Difference
Formal Written
Project reports, contracts, legal notices, project charter. Used for official and documented communication.
Formal Verbal
Presentations, speeches, formal briefings. Structured and planned verbal communication.
Informal Written
Emails, messages, texts, chat tools like Slack. Everyday communication between team members.
Informal Verbal
Casual conversations, hallway discussions, quick stand-ups. Relationship building and quick decisions.
Push Communication
Information is sent to specific recipients. Email, memos, reports. Sender decides what goes out. No guarantee it’s read.
Pull Communication
Information stored for people to access on their own. Intranet, SharePoint, knowledge bases. Used for large audiences.
Interactive Communication is a fourth type — real-time two-way communication between two or more people. Meetings, phone calls, video calls. Most effective for complex topics but not always practical for large teams.
Part C — Stakeholder Management
Stakeholder Management is the process of identifying everyone affected by the project and actively managing their engagement, expectations, and influence throughout the project lifecycle.
A stakeholder is anyone who can affect or be affected by the project — positively or negatively. This includes the client, the project sponsor, team members, end users, regulators, and even community members. The golden rule: identify stakeholders early and never stop managing them.
7. Stakeholder Engagement Levels — The 5-Level Ladder
Every stakeholder sits at one of five engagement levels. The PM’s job is to understand where each stakeholder is and move them towards the right level. The target is always Supportive or Leading.
Does not know the project exists or how it may affect them.
Action: Inform them. Share project information and its impact on them.
Knows about the project but is actively opposed to it or its outcomes.
Action: Engage directly. Understand concerns, address them, never ignore.
Never ignore a resistant stakeholderAware of the project but neither supporting nor opposing it.
Action: Educate them on benefits. Try to move them to Supportive.
Aware of the project and actively supportive of its success.
Action: Keep them informed and engaged. Leverage their support.
Target level for most stakeholdersActively engaged, advocating for the project, and driving its success from their position.
Action: Empower them. Use their influence to champion the project.
Ideal — best possible engagementThe most common wrong answer in stakeholder questions is to avoid or ignore resistant stakeholders. PMP always says: engage with them directly. Understand their concerns. A resistant stakeholder who is ignored becomes a project threat. One who is engaged may become neutral or even supportive.
“Unaware → Resistant → Neutral → Supportive → Leading” = “Uncle Robert Never Stops Leading”
8. The Power / Interest Grid — How to Manage Each Type
The Power/Interest Grid is a tool used in Identify Stakeholders to classify stakeholders and decide the right management strategy for each group. It plots stakeholders on two axes: how much power they have, and how much interest they have in the project.
Manage Closely
High Power + High Interest
Project sponsor, key clients. Most important group. Regular meetings, full information.
Keep Satisfied
High Power + Low Interest
Senior executives. Keep them happy but don’t overload them with detail.
Keep Informed
Low Power + High Interest
End users, subject matter experts. Share updates regularly. Their input is valuable.
Monitor
Low Power + Low Interest
Peripheral stakeholders. Watch but minimal effort. Keep on distribution list.
🏥 Real Example — Pharma Campaign Project
Manage Closely: Chief Medical Officer (high power, high interest) — weekly updates, involved in approvals.
Keep Satisfied: CEO (high power, low interest) — monthly executive summary, no detail overload.
Keep Informed: Medical writers, HCP target audience (low power, high interest) — regular briefings, their feedback shapes content.
Monitor: Legal team reviewing compliance passively (low power, low interest) — copy them on key documents, no meetings needed.
9. Quick Summary — Everything at a Glance
| Concept | One-line meaning | Exam trigger word |
|---|---|---|
| Plan Quality | Define standards and how to meet them — Planning | “define standards” / “quality planning” |
| Manage Quality | Audit processes — are we following the right steps? — Executing | “audit” / “process review” |
| Control Quality | Inspect deliverables — do they meet standards? — Monitoring | “inspect deliverable” / “test output” |
| Gold Plating | Adding unrequested features — not allowed without change control | “extra features” / “beyond scope” |
| Prevention Cost | Cost of doing it right first time — always cheapest | “training” / “quality planning” |
| Appraisal Cost | Cost of checking work before delivery | “testing” / “inspection” |
| Internal Failure | Defect found before delivery — rework | “defect found by team” |
| External Failure | Defect found by customer — most expensive | “defect found by customer” / “warranty” |
| Fishbone Diagram | Root cause analysis of a defect | “root cause” / “cause and effect” |
| Pareto Chart | 80/20 rule — focus on top causes | “80/20” / “most frequent defect” |
| Control Chart | Track process performance against limits over time | “within limits” / “out of control” |
| Comm Formula | n(n-1)÷2 — number of channels for n people | “how many channels” / “team size” |
| Push Communication | PM sends info to recipients — email, reports | “sent to” / “distributed to” |
| Pull Communication | Info stored for people to access themselves | “intranet” / “knowledge base” |
| Resistant Stakeholder | Knows project, opposed — must engage directly, never ignore | “opposed” / “against the project” |
| High Power, High Interest | Manage Closely | “key sponsor” / “senior client” |
| High Power, Low Interest | Keep Satisfied | “executive” / “steering committee” |
| Low Power, High Interest | Keep Informed | “end users” / “subject matter expert” |
| Low Power, Low Interest | Monitor | “peripheral” / “minor stakeholder” |
🎯 Practice Q&A — Test Yourself
Think of your answer first. Then click to reveal.
Control Quality = inspecting the PRODUCT during Monitoring & Controlling. Does the deliverable actually meet the agreed standards? Manage Quality looks at how work is done. Control Quality looks at what was produced.
Channels with 10: 10×9÷2 = 45
New channels added: 45 − 15 = 30 new channels. Adding just 4 people doubled the channels and added 30 more communication lines.
✅ Page 6 complete. Next up: Page 7 — Procurement, Leadership & Agile — Contract types, Tuckman’s model, conflict resolution, motivation theories, and Agile values.