Navigation Section
Monitoring & Controlling Process ITTOs
References
A project doesn’t stay on track by luck — it stays on track by design.
Monitoring & Controlling – The Feedback Loop of Project Reality
Monitoring and Controlling is where data meets decision. In this process group, you’re no longer asking, “Are we ready to start?” — you’re asking, “Is this still working?”
The ITTOs here don’t launch work — they measure it, judge it, and adjust it. They track what’s happening, compare it to what was planned, and help decide what changes (if any) are needed. And when change is necessary? These processes handle how it’s approved, documented, and communicated.
Each process in this group serves as a checkpoint — some passive (monitoring), others active (controlling). Together, they keep the project aligned with its intent, even when conditions shift. Below, we’ll explore the ITTOs living inside these containers — not as trivia, but as the tools that Power judgment, correction, and course recalibration.
Monitor and Control Project Work
This is the high-altitude, wide-angle process that oversees everything — Scope, Schedule, cost, Risk, Quality, and Stakeholder Engagement. The ITTOs here are tuned for visibility and actionable insights.
Inputs include Performance data, forecasts, the Project management plan, and updates from executing processes. Tools like [[3-glossary#earned Value|Earned Value]] Management (EVM), trend analysis, Forecasting, and root-cause analysis help interpret what’s working and what’s drifting.
Outputs? You’re looking at work Performance Reports, Change requests, and updates to baselines. This process doesn’t do the work — it ensures the work stays on track, or pivots cleanly when it doesn’t.
Perform Integrated Change control
This is where Change requests go to be judged. The ITTOs here help evaluate each proposed modification for Impact, feasibility, and Alignment with project goals.
Inputs include Change requests themselves (of course), but also the plans and documents that might be affected. Tools include expert judgment, decision-making models, and often a formal [[3-glossary#Change control board|Change control board]] (CCB).
The key output — approved or rejected Change requests — feeds back into every other group. This is the firewall that prevents change chaos. Without it, your project turns into a suggestion box with a Gantt chart.
Validate Scope and [[3-glossary#control Scope|Control Scope]]
Validate Scope ensures the work being delivered is what was promised — and that it’s officially accepted. The ITTOs focus on verification: [[3-glossary#Scope Baseline|Scope Baseline]], Requirements Documentation, and Inspection.
[[3-glossary#control Scope|Control Scope]], on the other hand, checks whether any unplanned expansion (aka [[3-glossary#Scope creep|Scope creep]]) is sneaking in. Inputs include Performance data, WBS documents, and change logs. Data analysis tools help evaluate variance between what was planned and what’s showing up.
Together, these processes answer: Are we building the right thing — and only the right thing?
Control Schedule and Control Costs
These two processes help ensure the project stays realistic about time and money. Their ITTOs often overlap, but they track different pain points.
Control Schedule draws from the [[3-glossary#Schedule Baseline|Schedule Baseline]], Performance data, and forecasts. You’ll see Critical path analysis, what-if scenarios, trend analysis, and variance evaluations. When the timeline slips, this is where it’s spotted.
Control Costs uses similar tools, but adds Budget-focused inputs: funding Requirements, cost forecasts, and actual expenditures. Techniques like reserve analysis and EVM come into play, allowing you to compare Baseline vs. actual vs. projected cost.
Outputs for both include updated forecasts, Change requests, and new Performance Reports — the raw materials for realignment.
Control Quality and Control Resources
Control Quality examines the outputs of the project — deliverables, processes, and Documentation — to ensure they meet Standards. Inputs include [[3-glossary#Quality Metrics|Quality Metrics]], test results, and Lessons learned. Tools include inspections, sampling, and control charts. The output? Verified deliverables, Quality Reports, and, if needed, Change requests.
Control Resources watches how people, equipment, and materials are actually being used. You’ll track Availability, usage logs, and capacity. When gaps or overloads appear, this process flags them. It answers the question: Do we have what we need — and are we using it well?
Monitor Communications and Monitor Stakeholder Engagement
These processes listen more than they talk. They track whether planned Communication is happening — and whether stakeholders are responding as expected.
Monitor Communications checks if the message is getting through. Inputs include the communications management plan, project documents, and Feedback. Outputs are Performance insights and, if needed, updates to how information is being shared.
Monitor Stakeholder Engagement goes deeper: are stakeholders engaged, satisfied, Informed? Or are they silent, disengaged, or pushing back? The ITTOs here include interpersonal Feedback loops, monitoring tools, and direct observation. Outputs often include recommendations for re-Engagement or Mitigation.
Monitor Risks and Control Procurements
Monitor Risks evaluates whether the responses you planned are still working — or whether new risks have emerged. Inputs include the [[3-glossary#Risk register|Risk register]], response plans, and actual Performance data. Tools like audits, reassessments, and Data analysis techniques allow you to assess Probability, Impact, and proximity in real time.
Control Procurements ensures that what was promised by vendors is being delivered — and that Contracts are still valid. Inputs include agreements, procurement Documentation, and Inspection Reports. Outputs often include payment approvals, updated Contracts, and sometimes formal claims administration.
What You Should Take Away
Monitoring and Controlling is not a single moment — it’s a continuous rhythm of observing, analyzing, deciding, and acting. The ITTOs here form the nervous system of the project. They gather data, interpret it, and Trigger changes that keep the project alive and aligned.
On the exam, look for clues like:
- Performance data is being reviewed
- Forecasts are being updated
- Change is being considered, requested, or approved
- A project is off course — and someone Needs to respond
That’s the Monitoring and Controlling mindset: diagnose, decide, and adjust.
Questions Worth Exploring
- What distinguishes a change request from an Issue — and how do ITTOs handle both?
- How does monitoring Risk differ from controlling Scope?
- What tools help you determine when Stakeholder Engagement is failing?
- How do outputs from [[3-glossary#Quality control|Quality control]] feed back into the monitoring cycle?