ISO 21502 Foundation — Lesson 3: Risk, Quality, Change, Communication, Stakeholders, Issues, and Performance Control

Learning Objectives

• Map the roles, prerequisites, decisions, and evidence shaping risk, Quality, Change, Communication, Stakeholders, Issues, and Performance Control for a cross-functional project team establishing consistent governance and delivery controls for a business transformation initiative.
• Build project control and decision register through a controlled activity with reviewable checkpoints.
• Resolve an approved change is not reflected in the baseline, validate the correction, and record the accepted result.

Detailed Topics

• Risk
• Quality
• Change
• Communication
• Stakeholders
• Issues
• Performance Control
• Decision ownership, prerequisites, and acceptance evidence for risk, Quality, Change, Communication, Stakeholders, Issues, and Performance Control
• Security, compliance, resilience, documentation, and support implications for project management foundation

Instructor Demonstration

The instructor demonstrates risk, Quality, Change, Communication, Stakeholders, Issues, and Performance Control within a cross-functional project team establishing consistent governance and delivery controls for a business transformation initiative, records each material decision in project control and decision register, and contrasts the accepted state with the controlled exception where an approved change is not reflected in the baseline.

Hands-On Exercise

Complete a controlled exercise focused on risk, Quality, Change, Communication, Stakeholders, Issues, and Performance Control. Establish the expected outcome, produce project control and decision register, introduce the case where an approved change is not reflected in the baseline, apply a reversible correction, and rerun the original acceptance checks.

1. Confirm the requirement, stakeholders, environment, assumptions, inputs, and expected result.
2. Perform the project management foundation workflow and capture evidence before and after each material decision.
3. Test normal, boundary, failure, security, compliance, recovery, and operational conditions where relevant.
4. Document the root cause, correction, rollback, owner, support action, and next improvement priority.

Scenario Analysis

• Identify the business or assurance decision required within a cross-functional project team establishing consistent governance and delivery controls for a business transformation initiative.
• Compare control strength, evidence quality, operational impact, cost, resilience, and stakeholder trade-offs.
• Define escalation, communication, recovery, acceptance, and follow-up requirements for project control and decision register.

Troubleshooting Guidance

When an approved change is not reflected in the baseline, separate the visible symptom from its governing requirement, verify source evidence and recent changes, test one reversible hypothesis, and update project control and decision register only after the corrected state passes normal and boundary checks.

Validation Checklist

• project control and decision register identifies the approved baseline, accountable owner, inputs, and expected result.
• Evidence confirms risk, Quality, Change, Communication, Stakeholders, Issues, and Performance Control under normal and relevant exception conditions.
• The response to “an approved change is not reflected in the baseline” is reversible, tested, and supported by before-and-after records.
• Residual project management foundation risk, support ownership, deadlines, and the next action are recorded.

Lesson Outcome

Learners can apply Risk, Quality, Change, Communication, Stakeholders, Issues, and Performance Control, explain the choices made, and defend the result using project control and decision register.