The PMO asks for earned value on an evolving backlog. What should we consider?
Measurement-method mismatchCheck whether scope and valuation are stable enough for the proposed measure to be meaningful. Use suitable outcome and flow evidence where assumptions do not hold, rather than manufacturing misleading precision.
What to do now
- Clarify the management decision needed
- Assess scope and baseline stability
- Explain measurement limitations
- Agree a defensible reporting approach with the PMO
When to escalate
The requested metric will materially mislead investment decisions.
The delivery owner and relevant governance authority
Example
A program reports accepted release outcomes and forecast cost rather than an unsupported earned-value calculation.
Mistake to avoid
Treating story points as financial value without a justified model.
Prevent a repeat
Check whether governance decisions use real delivery evidence rather than forcing incompatible reporting rituals.
Suggested ApprovedFlow setup
- Projects
- Tasks
- Documents
- Approvals
Keep decision milestones and iterative task work connected, with explicit evidence required at each approved gate. See the platform
Related cases
- How do we decide whether a hybrid approach is actually helping?Unexamined method value
- Our project plan and backlog disagree about scope. Which is authoritative?Competing scope representations
- How can a small organization get value from a PMO without hiring a large team?Lightweight portfolio coordination
- Our PMO collects reports but adds little value. What should it focus on?Administrative PMO without decisions