HKSM

A structured evaluation of project performance against plans and objectives, conducted at defined intervals. It analyzes progress, variances, trends, and forecasts to decide corrective or preventive actions and communicate results.

Key Points

• Technique to assess planned versus actual performance and agree on next steps.
• Focuses on variances, trends, and forecasts, not just status reporting.
• Uses both quantitative metrics (for example, schedule and cost indices, defect rates) and qualitative insights.
• Produces decisions such as corrective or preventive actions, change requests, and updates to plans and logs.
• Cadence and format are set by project governance and stakeholder needs.
• Effective reviews are evidence-based, time-boxed, and documented for traceability.

Purpose of Analysis

To determine how well the project is performing, why it is performing that way, and what should be done next. Reviews increase transparency, enable timely control actions, and support informed decision making across stakeholders.

Method Steps

• Plan the review cadence, agenda, roles, and decision rights.
• Gather and validate performance data and baseline references.
• Analyze variances, trends, forecasts, and constraints; identify root causes.
• Discuss findings with stakeholders and confirm shared understanding.
• Decide on corrective or preventive actions and any change requests needed.
• Record outcomes, owners, due dates, and communication updates.
• Follow up on action execution and measure effectiveness in the next review.

Inputs Needed

• Approved baselines and plans (scope, schedule, cost, quality, risks).
• Work performance data and reports (for example, progress, EVM, throughput, defect logs).
• Issue log, risk register, change log, and assumptions log.
• Resource usage, capacity, and availability information.
• Stakeholder feedback and acceptance or quality results.
• Agreements, governance rules, and decision thresholds or control limits.

Outputs Produced

• Documented decisions, action items, and owners with target dates.
• Updated forecasts (schedule, cost, benefits, delivery outlook).
• Change requests for baseline updates or scope, schedule, or budget changes.
• Updates to plans, risk and issue records, and stakeholder communications.
• Lessons learned entries and improvement backlog items.

Interpretation Tips

• Look for trends and patterns over time rather than reacting to a single data point.
• Compare like-for-like: use the current approved baseline and consistent measurement methods.
• Validate data quality and context before drawing conclusions.
• Distinguish normal variation from signals that exceed thresholds or control limits.
• Link findings to objectives and constraints to prioritize actions that deliver the most value.

Example

In a monthly review, the team reports SPI 0.88 and CPI 1.05. Root cause analysis shows delayed external approvals affecting the critical path. The team agrees to fast-track two tasks, requests a change to add a part-time coordinator for approvals, updates risks and communications, and schedules a follow-up check on SPI next month.

Pitfalls

• Treating the meeting as a status readout instead of analysis and decision making.
• Focusing on vanity metrics and ignoring outcome-focused indicators.
• Blame-oriented discussions that discourage transparency.
• Overloading the agenda, leaving no time for root cause and action planning.
• Failing to record decisions and owners, leading to weak follow-through.
• Rebaselining without proper change control or adequate evidence.

PMP Example Question

During a monthly performance review, CPI is 0.92 and SPI is 1.04. The sponsor asks to rebaseline scope, schedule, and budget immediately. What should the project manager do next?

1. Approve the rebaseline to satisfy the sponsor.
2. Conduct root cause analysis and agree on corrective actions; submit change requests if needed.
3. Add resources to accelerate work without further analysis.
4. Update lessons learned and close the review with no actions.

Correct Answer: B - Conduct root cause analysis and agree on corrective actions; submit change requests if needed.

Explanation: Performance reviews should analyze causes and define actions before altering baselines. Rebaselining occurs only through approved change control when justified.