HKSM

Key Points

• Built from analyzed performance information, not raw data.
• Common formats include status reports, dashboards, EVM summaries, and burn charts.
• Content and cadence should match stakeholder needs and governance expectations.
• Show status against baselines, variances, trends, and forecasts.
• Include brief commentary, risks/issues, and recommended actions.
• Must be timely, accurate, and traceable to source data.

Purpose

Provide clear, decision-ready insight into project performance. Help sponsors, teams, and governance bodies understand status, issues, and what actions are needed next.

Data Sources

• Work performance data from schedule tools, cost systems, and task trackers.
• Analyzed metrics such as CPI, SPI, burn-up/burn-down, velocity, defect trends, and throughput.
• Baselines and plans: scope baseline, schedule baseline, cost baseline, and release plans.
• Logs and registers: risk register, issue log, change log, decision log, and impediment list.
• Quality results: test reports, audit findings, inspections, and acceptance records.
• Forecasts and estimates: EAC/ETC, completion dates, capacity forecasts, and backlog health.

How to Compile

• Define the audience and objectives (executive, team, sponsor, steering committee).
• Select the reporting cadence and channels (weekly email, dashboard, governance meeting).
• Collect current data from trusted systems and validate for accuracy and completeness.
• Compute KPIs and variances against baselines and thresholds.
• Analyze trends, root causes, and implications for scope, schedule, cost, and quality.
• Draft concise narrative: what happened, why it matters, and proposed actions.
• Visualize the key metrics using simple charts and traffic-light indicators.
• Highlight risks, issues, changes, and decisions needed by stakeholders.
• Review for clarity and consistency; obtain approvals if required by governance.
• Version, store in a shared location, and distribute to the intended audience.

How to Use

• Guide decision-making in status and governance meetings.
• Trigger corrective or preventive actions when thresholds are breached.
• Communicate priorities and trade-offs to stakeholders and teams.
• Support forecasting and re-planning based on trends and outcomes.
• Track benefits realization, risk exposure, and change impacts over time.

Sample View

• Overall status: Green (on scope), Amber (schedule), Green (cost), Amber (quality).
• Schedule: SPI 0.93; critical path slipped 5 days; forecast completion 2 weeks late.
• Cost: CPI 1.02; EAC within budget; pending approval for $50k change.
• Scope: 82% of planned deliverables complete; 3 change requests under review.
• Quality: Defect density trending up 10% week-over-week; test coverage at 78%.
• Risks and issues: High risk of vendor delay; 2 high-priority issues escalated.
• Actions: Add test resources; negotiate vendor buffer; re-baseline if variance persists.

Interpretation Tips

• Compare against baselines and control thresholds, not just last period values.
• Look for patterns across scope, schedule, cost, and quality to spot systemic issues.
• Validate assumptions behind forecasts; challenge overly optimistic recovery plans.
• Check data lineage and timing to avoid acting on stale or partial information.
• Balance leading indicators (trends, throughput) with lagging results (defects, costs).
• Focus discussions on risks, impacts, and clear next steps, not just status colors.

PMP Example Question

A sponsor asks for a concise document that shows current status, trends, and recommended actions for an upcoming decision gate. What should the project manager provide?

1. Work performance data.
2. Work performance information.
3. Work performance reports.
4. Project documents updates.

Correct Answer: C — Work performance reports

Explanation: Reports synthesize analyzed information into decision-ready summaries with recommendations. Data and information alone do not provide the tailored, actionable view stakeholders need.