HKSM

Ongoing oversight of the project to compare actual results to the plan, analyze variances and trends, forecast outcomes, recommend and route changes, and communicate performance so timely corrective and preventive actions can be taken.

Purpose & When to Use

This process keeps the project on course. It gathers performance data, turns it into insights, and drives decisions about corrective actions, risk responses, and change requests. Use it throughout the project, from early execution until closure, and run it on a regular cadence or whenever significant events occur.

• Confirm work aligns with the approved plan and baselines.
• Detect variances early and understand their causes.
• Forecast cost, schedule, and benefit outcomes to support decisions.
• Recommend actions and route changes through the formal change process.
• Provide clear performance reporting to stakeholders.

Mini Flow (How It’s Done)

• Collect current results and observations from execution as raw data.
• Convert data into information by analyzing scope, schedule, cost, quality, risks, and issues.
• Compare actuals to baselines; calculate key indicators and trends.
• Forecast outcomes, such as estimate at completion and expected finish dates.
• Identify needed actions: corrective, preventive, defect repair, or risk response adjustments.
• Prepare performance reports that summarize status, variances, forecasts, and recommendations.
• Submit change requests for any updates that affect baselines or approved plans.
• After approval, coordinate implementation and update plans and project documents.
• Communicate results and decisions to stakeholders and capture lessons learned.

Quality & Acceptance Checklist

• All KPIs and thresholds reviewed; outliers explained with documented root causes.
• Variance and trend analyses completed for scope, schedule, cost, quality, and benefits.
• Forecasts updated using consistent methods and current data.
• Recommended actions are specific, owned, and time-bound.
• Any baseline or scope change is supported by a submitted and approved change request.
• Risk and issue logs are current, with priorities, owners, and due dates.
• Approved changes traced to implementation and verified for effectiveness.
• Deliverable status aligns with acceptance criteria and quality standards.
• Stakeholders received clear reports appropriate to their information needs.
• No baselines updated without formal approval; all updates are version-controlled.

Common Mistakes & Exam Traps

• Confusing monitoring with doing the work; executing tasks belongs to directing and managing the work.
• Bypassing the change process; do not rebaseline or adjust scope without formal approval.
• Reporting data without analysis; exams expect variance, trend, and forecast insights, not raw numbers.
• Focusing only on schedule and cost; include scope, quality, risks, issues, benefits, and constraints.
• Implementing fixes immediately; first analyze impact and submit a change request when baselines are affected.
• Mixing up performance artifacts: data is raw, information is analyzed, reports are formatted for decisions.
• Ignoring emerging risks or stale issue logs; these must be reviewed and updated regularly.

PMP Example Question

A project shows CPI = 0.80 and SPI = 1.05. The sponsor asks to remove a feature to recover cost. What should the project manager do next?

1. Submit a change request and evaluate the impact on scope, cost, schedule, and benefits.
2. Rebaseline the project to reflect the removed feature.
3. Crash critical path activities to reduce total cost.
4. Update the risk register only, since schedule is ahead.

Correct Answer: A — Submit a change request and evaluate the impact on scope, cost, schedule, and benefits.

Explanation: Scope reductions require the formal change process and impact analysis before rebaselining or implementing. Crashing targets schedule, not cost, and rebaselining comes only after approval.