Coursify

What Are Project Metrics? Types of Project Metrics with Examples

What Are Project Metrics? Types of Project Metrics with Examples

Verified Sources
Sep 12, 2026

Project metrics are used to measure how a project is progressing and performing. In project management, project metrics are data-driven indicators that help teams compare actual progress against plans and identify corrective actions early—especially across dimensions like schedule, cost, scope, quality, and risk.2

A helpful way to think about metrics is that they provide evidence (numbers/formulas) that support decisions, stakeholder reporting, and continuous improvement. While “metrics” and “KPIs” are related, KPIs typically refer to a smaller set of metrics tied directly to goals/success criteria.

Mermaid overview of the typical metric “flow”:

Key terms you’ll see below: KPI; baseline; variance; earned value; threshold.

Footnotes

  1. ProjectManager.com — Top Project Metrics You Need to Track - Defines project metrics as data sets/formulas used to measure progress, success, and performance. ↩

  2. Saviom — Top 7 Project Metrics Every Manager Should Monitor - Defines project metrics, distinguishes from KPIs, and lists major metric areas (scope, cost, time/schedule, quality, etc.). ↩ ↩2

  3. Adobe Workfront — Metrics for Project Management: KPIs & Success - Explains why metrics matter for measuring success quantitatively for projects. ↩

Earned Value Management (EVM) Made Easy (PV, EV, AC, SPI, CPI)

Types of project metrics (and why they matter)

Different projects prioritize different outcomes, so there are many possible metrics. However, most project metric sets organize around a few core control areas: scope, cost, schedule, and quality—and often include risk and resources as well.2

Below are common metric types, with an example calculation/interpretation for each.

Footnotes

  1. Plaky — Project Management Metrics: How to Track Project Progress - Organizes project metrics into groups including scope, cost, schedule, and quality and explains scope creep concerns. ↩

  2. Saviom — Top 7 Project Metrics Every Manager Should Monitor - Defines project metrics, distinguishes from KPIs, and lists major metric areas (scope, cost, time/schedule, quality, etc.). ↩

How to select and use project metrics (practical method)

  1. 1
    Step 1

    List what “success” means (e.g., on-time delivery, within budget, acceptable defect levels).

  2. 2
    Step 2

    For schedule/cost, establish planned values and budgets. For quality, define acceptance criteria (e.g., defect limits).

  3. 3
    Step 3

    Pick metrics for scope stability, cost performance, schedule performance, quality outcomes, and risk indicators.

  4. 4
    Step 4

    Make sure every metric can be computed consistently from tracked data (timesheets, burn charts, defect logs, risk registers).

  5. 5
    Step 5

    Define what happens if a metric goes above/below a limit (e.g., investigate, escalate, replan).

  6. 6
    Step 6

    Track how metrics change over time to identify early warning signals.

Common Project Metric Categories

Illustrative emphasis—most projects monitor multiple categories, but leadership often focuses on the top ones.

1) Scope metrics

scope metrics measure the size/boundaries of the work and help detect scope creep using change and completion measures.

Example (scope stability using change request rate):

  • Suppose the project has a baseline scope of 30 planned deliverables.
  • During the month, 4 new deliverables are added via approved change requests.
  • Scope change rate can be expressed as:

Scope Change Rate=New/Added Scope ItemsBaseline Scope Items=430=0.133≈13.3%\text{Scope Change Rate}=\frac{\text{New/Added Scope Items}}{\text{Baseline Scope Items}}=\frac{4}{30}=0.133 \approx 13.3\%

Interpretation: a higher rate suggests increasing boundary churn and potential downstream cost/schedule impacts.

Key terms: deliverables; change request; scope creep.

Footnotes

  1. Plaky — Project Management Metrics: How to Track Project Progress - Organizes project metrics into groups including scope, cost, schedule, and quality and explains scope creep concerns. ↩

2) Cost metrics (Budget vs Actual)

Cost metrics track budget control and financial efficiency.

A widely used “cost efficiency” metric in Earned Value Management is the CPI:

From earned value concepts, cost performance index is defined as:

CPI=EVAC\text{CPI}=\frac{\text{EV}}{\text{AC}}

Example:

  • Planned work (by today) has earned value EV = $80,000
  • Actual cost incurred AC = $100,000

Then:

CPI=80,000100,000=0.8\text{CPI}=\frac{80,000}{100,000}=0.8

Interpretation: CPI < 1 indicates cost performance worse than planned—i.e., you’re spending more than you’ve “earned” in value for the work completed.2

Key terms: EV; AC; CPI.

Footnotes

  1. PMI — The practical calculation of schedule variance - Provides CPI and SPI definitions (CPI = EV/AC and SPI = EV/PV) and interpretation vs 1.0. ↩

  2. Deltek — Cost Performance Index: A Guide for Project Managers - Describes CPI as a cost efficiency ratio and notes what CPI indicates. ↩

3) Schedule metrics (Plan vs Progress)

Schedule metrics detect whether progress is ahead/behind plan.

Earned Value offers the SPI:

SPI=EVPV\text{SPI}=\frac{\text{EV}}{\text{PV}}

Example:

  • Earned value EV = $80,000
  • Planned value (what should be done by today) PV = $100,000

Then:

SPI=80,000100,000=0.8\text{SPI}=\frac{80,000}{100,000}=0.8

Interpretation: SPI < 1 indicates the project is behind schedule relative to the plan.2

Key terms: PV; SPI.

Footnotes

  1. PMI — The practical calculation of schedule variance - Provides CPI and SPI definitions (CPI = EV/AC and SPI = EV/PV) and interpretation vs 1.0. ↩

  2. Deltek — Cost Performance Index: A Guide for Project Managers - Describes CPI as a cost efficiency ratio and notes what CPI indicates. ↩

4) Earned Value (integrated) metrics: CPI & SPI together

When you need an integrated view across schedule and cost, use earned value metrics as an early warning system. Earned Value Management (EVM) is a performance measurement approach that integrates scope , schedule , and cost to evaluate project health.

Example using both together:

  • EV = $80,000
  • AC = 100,000100,000 \Rightarrow$ CPI = 0.8 (cost inefficiency)
  • PV = 100,000100,000 \Rightarrow$ SPI = 0.8 (schedule behind)

Interpretation:

  • The same point in time shows both cost and schedule underperformance.
  • This strongly suggests the project needs corrective actions rather than only minor adjustments.2

Key terms: EVM; EAC; ETC.

Footnotes

  1. Profit.co — EVM Formulas and Metrics Explained: CPI, SPI & EAC - Explains EVM as integrating scope, schedule, and cost and includes CPI/SPI/CV/SV/EAC relationships. ↩ ↩2

  2. PMI — The practical calculation of schedule variance - Provides CPI and SPI definitions (CPI = EV/AC and SPI = EV/PV) and interpretation vs 1.0. ↩

5) Quality metrics (defect and rework)

Quality metrics focus on whether the output is correct/reliable, not just whether it’s on time and on budget.

Two commonly used software quality metrics are:

  • defect density
  • defect rate

Example (defect density):

  • After a release, you observe 18 defects.
  • Code size for the release is 30,000 LOC (lines of code).
  • Defect density (per 1,000 LOC) is:

Defect Density=1830,000/1,000=1830=0.6 defects per 1,000 LOC\text{Defect Density}=\frac{18}{30,000/1,000}=\frac{18}{30}=0.6 \text{ defects per 1,000 LOC}

Interpretation: a higher defect density indicates a more error-prone delivery and may correlate with insufficient testing/review or requirement ambiguity.

Key terms: defect density; defect escape rate; QA.

Footnotes

  1. Cortex.io — 24 Agile Metrics for Engineering Leaders to Track - Defines defect density and why it is used to assess quality. ↩

6) Risk metrics (exposure and probability-weighted impact)

Risks are typically stored in a risk register. risk metrics help prioritize mitigation work.

Example (risk exposure):

  • Risk A: probability = 30%, cost impact if it happens = $200,000
  • risk exposure can be approximated as:

Risk Exposure=P×Impact=0.30×200,000=60,000\text{Risk Exposure} = P \times \text{Impact} = 0.30 \times 200,000 = 60,000

Interpretation: this yields a comparable “expected impact” number to rank risks for mitigation.2

Key terms: risk register; likelihood; impact.

Footnotes

  1. Adobe Workfront — Metrics for Project Management: KPIs & Success - Explains why metrics matter for measuring success quantitatively for projects. ↩

  2. Saviom — Top 7 Project Metrics Every Manager Should Monitor - Discusses risk-related metric monitoring as part of performance measurement and informed decision-making. ↩

7) Delivery speed metrics (lead time / cycle time / throughput)

For software and knowledge-work projects, teams often use cycle time and lead time to detect bottlenecks.2

Example (cycle time):

  • Work item starts development on Monday.
  • It is deployed to production on Friday.
  • Cycle time = 5 days.

Interpretation: if cycle time rises week over week, it often indicates bottlenecks in the process (reviews, testing, approvals). Cycle time is “active processing time,” while lead time usually includes waiting.

Key terms: cycle time; lead time; velocity.

Footnotes

  1. Waydev — Lead Time vs Cycle Time in Software Development - Distinguishes cycle time vs lead time and clarifies that cycle time focuses on development processing time. ↩ ↩2

  2. Zenhub Blog — Software Cycle Time: A Comprehensive Guide - Defines cycle time as start-to-finish elapsed time and contrasts with lead time including waiting. ↩

Metrics vs. KPIs vs. goals

Project Metrics Quick Deck

1 / 5
Question · Term

Project metric

Click to reveal
Answer · Definition

A quantifiable measure used to track and assess project progress/performance.

Footnotes

  1. ProjectManager.com — Top Project Metrics You Need to Track - Defines project metrics as data sets/formulas used to measure progress, success, and performance. ↩

Knowledge Check

Question 1 of 4
Q1Single choice

Which formula is correct for the Earned Value schedule performance metric?

Explore Related Topics

1

Understanding “MC”: Meanings, Contexts, and How to Interpret the Abbreviation

The abbreviation “MC” has multiple domain‑specific meanings, chiefly master of ceremonies in events and Monte Carlo in technical fields, with additional institutional uses.

  • Meaning depends on context; identify domain, neighboring words, and source to disambiguate.
  • In event settings “MC” = master of ceremonies, who introduces speakers and manages flow.
  • In statistics/AI “MC” = Monte Carlo methods, estimating expectations via E[X]≈1n∑i=1nxi\mathbb{E}[X] \approx \frac{1}{n}\sum_{i=1}^{n} x_i.
  • Academic or organizational documents may assign local codes (e.g., Maternal & Child Health), so always define the term on first use.
2

Complexity Analysis: Best Case, Worst Case, and Average Case

The material introduces best‑case, worst‑case, and average‑case complexity as three distinct functions describing an algorithm’s running time on inputs of size nn, explains how they are formally defined, and shows why worst‑case analysis is usually preferred.

  • Best case: Tbest(n)=min⁡I∈InT(I)T_{\text{best}}(n)=\min_{I\in\mathcal I_n} T(I), the minimum time over all inputs of size nn.
  • Worst case: Tworst(n)=max⁡I∈InT(I)T_{\text{worst}}(n)=\max_{I\in\mathcal I_n} T(I), giving a guaranteed upper bound.
  • Average case: Tavg(n)=∑I∈InP(I) T(I)T_{\text{avg}}(n)=\sum_{I\in\mathcal I_n}P(I)\,T(I), requiring an explicit input probability model.
  • Linear search illustrates the three cases: Θ(1)\Theta(1) best, Θ(n)\Theta(n) worst, and Θ(n)\Theta(n) average (expected n+12\frac{n+1}{2} comparisons).
  • Worst‑case analysis is favored because it needs no probabilistic assumptions and ensures reliability for all inputs, especially in real‑time or safety‑critical systems.
3

Mastering the Project Life Cycle: A Complete Visual Guide

Browse all research articles