PMP Measuring Schedule Progress with the Right Method

Progress measurement matters because schedule control becomes misleading when the project uses the wrong way to judge what is actually complete. PMP questions in this area usually reward the project manager who chooses a progress measure that fits the delivery method and the nature of the work.

Measure What Completion Really Means

In predictive work, progress may be assessed through:

• completed activities
• milestone achievement
• earned value style measures
• baseline variance

In adaptive work, progress may be assessed through:

• completed backlog items
• iteration goals met
• throughput or velocity
• release progress

The stronger answer usually measures completed value or completed scope, not partial motion that only looks busy.

    flowchart TD
	    A["Delivery method and work type"] --> B["Choose progress measure"]
	    B --> C["Collect current status evidence"]
	    C --> D["Compare against schedule expectation"]
	    D --> E["Decide whether adjustment is needed"]

Why Method Fit Matters

The exam often tests whether the project manager is measuring schedule progress in a way that actually supports decisions. The weaker answer reports percent complete without any defensible basis or applies predictive metrics to adaptive work without translation.

The stronger answer usually asks:

• What does complete mean here?
• What measure best reflects true progress?
• Is the reported progress decision-useful?

Example

An adaptive team says a feature is 80% done, but nothing usable has been completed and tested. The stronger measure may be completed backlog items or release-ready increments rather than vague partial completion.

Common Pitfalls

• Reporting effort spent as if it equals progress.
• Using percent complete with no reliable basis.
• Ignoring methodology fit.
• Confusing activity volume with schedule advancement.

Check Your Understanding

Sample Exam Question

Scenario: A project manager receives a report showing that an adaptive team’s key feature is “90% complete.” When asked for evidence, the team says development is mostly done, but testing is incomplete and nothing is yet releasable. A stakeholder wants to count the feature as nearly finished for schedule reporting.

Question: Which action is most appropriate at this point?

• A. Report the feature as nearly complete because development effort is mostly done
• B. Stop measuring adaptive-team progress
• C. Reassess the progress measure and report status using a completion indicator that reflects releasable or definition-of-done criteria
• D. Convert the team to predictive delivery immediately

Best answer: C

Explanation: The strongest answer is C because PMP questions in this area reward meaningful progress measurement. If the feature is not truly complete by the team’s delivery standard, reporting it as almost done weakens schedule control.

Why the other options are weaker:

• A: Effort spent is not the same as schedule-complete value.
• B: The problem is weak measurement, not the existence of measurement.
• D: Changing methodology is unrelated to the immediate reporting issue.

Key Terms

• Progress measure: The method used to judge how much planned work is truly complete.
• Definition of done: The agreed condition that determines whether work can be considered complete.
• Schedule evidence: Actual information used to support status decisions.