Monitoring & Controlling: variance, change, course-correct
What you'll be able to do
Watch the numbers, find the variance, do something about it, log it.
- M&C runs in parallel with all other focus areas — not after.
- Monitoring observes; controlling responds.
- Tools: variance analysis, trend analysis, root-cause analysis.
Monitoring & Controlling tracks, measures, reviews, and regulates the progress and performance of the project. It runs *in parallel* with the other focus areas — it isn't a separate phase. The key benefit is to detect variances early enough to take corrective action before they become baseline-breaking failures.
PMBOK distinguishes monitoring (observe, measure, report) from controlling (analyse variance, decide a response, implement the change). Variance analysis compares actual to plan; trend analysis projects whether the variance is likely to widen, narrow, or stay stable; root-cause analysis explains why the variance occurred.
The most common controlling tool the exam tests is integrated change control. Whatever the variance, the response — corrective action, preventive action, defect repair, or scope change — flows through integrated change control to keep baselines consistent. The exception is *workarounds*: small unanticipated responses to risks that have already occurred and that don't change the plan.
Key points
- M&C runs in parallel with all other focus areas — not after.
- Monitoring observes; controlling responds.
- Tools: variance analysis, trend analysis, root-cause analysis.
- Integrated change control keeps baselines synchronised.
Ask a PMBOK tutor
Paste this lesson plus your question into a fresh chat. Claude is a strong PMP study coach — try asking for additional worked examples, a comparison across PMBOK editions (6e vs 7e vs 8e), or a tougher scenario.