Notes on Earned Value Management, Critical Path, and Value-Driven Project Execution

Key Concepts and Definitions

  • ROI vs Value: The focus is not only on budget spent but on the value delivered to the business. Value is what the business gains relative to the money spent; must be measured throughout the project lifecycle.
  • Ad value management: The approach of measuring value delivered for money spent; the key question: For that money spent, what value did the business receive?
  • Earned Value Management (EVM) as integrated framework: uses Planned Value (PV), Earned Value (EV), and Actual Cost (AC) to measure schedule and cost performance; projects are asked to show value to management.

Earned Value Management Metrics

  • Planned Value (PV): Budgeted value of work planned to be completed by a point in time.

  • Earned Value (EV): Budgeted value of work actually performed (BCWP).

  • Actual Cost (AC): Actual cost incurred for the work performed (ACWP).

  • Cost Variance (CV): CV = EV - AC

  • Schedule Variance (SV): SV = EV - PV

  • Cost Performance Index (CPI): \mathrm{CPI} = \dfrac{EV}{AC}

  • Schedule Performance Index (SPI): \mathrm{SPI} = \dfrac{EV}{PV}

  • Interpretation

    • CPI > 1 indicates cost under run (spending less than earned value) • CPI < 1 indicates cost overrun.
    • SPI > 1 indicates ahead of schedule; SPI < 1 indicates behind schedule.
    • A target “sweet spot” is often around 1.0 to 1.5 for CPI/SPI depending on context; e.g., CPI ≈ 1.2 and SPI ≈ 1.2 might indicate modest under-run and ahead schedule. In some conversations, figures like 1.5 or 1.2 k are used illustratively; adapt to budget scales ($1.5M, $1.2M, etc.).

  • Practical example interpretations from the video:

    • If EV is higher than PV and AC, you are delivering more value than planned and/or spending efficiently; if EV trails PV or AC trails EV, flags exist.
    • Underruns and overruns affect manager communications and risk; the prudent PM keeps the manager posted and explains the plan to catch up.
    • When cost overruns occur (AC > EV), CPI < 1; cost underruns (AC < EV) yield CPI > 1.

  • Example figures from the transcript

    • Months: PV = 33, AC = 30 in a given view of project health; earned value discussion showed value realized vs planned; interpret as: EV would be a separate value; if EV > PV and EV > AC, project healthy; if EV < PV or EV < AC, watch for red flags.
    • In a more real-world phrasing: if client value is 45,000 and EV is 50,000 but actual cost is 30,000, the project may be healthy; if EV is 30,000 and PV is 33,000 and AC is 30,000, the health is mixed; careful to compare EV to PV and to AC.

  • Additional context: The video explains the dynamic nature of EVM in practice, including the tendency for leadership to request quick estimates and for risk to show up as CPI/SPI drift; the need for transparency and prompt communication with stakeholders.

Value Realization and Business Impact

  • The central question: Are we delivering value for the money spent? Value is the net business impact, not just the budget;

    • ROI could be considered in some contexts; EV (earned value) emphasizes value delivered vs spent; ad value management emphasizes tying spending to business value.
    • “Definition of Done” (DoD): The stakeholder-defined acceptance criteria; not just internal completion; if DoD isn’t met, business value isn’t realized.
    • Reusability and cross-project value: A component (e.g., an API or engine) developed for one project can generate value across multiple programs or products; this broader value should be tracked and communicated; patents or reuse can enhance organizational value beyond the single project.

  • Practical guidance:

    • Expect management asks: Is there enough budget to complete? Will you need more money? Communicate early and propose catch-up plans.
    • When underspending occurs early, plan to burn the savings in subsequent weeks; consider adding resources to accelerate upcoming work; ensure the plan is realistic and aligns with next-week deliverables.
    • The business impact of value is realized when the product or service delivers utility to users; stakeholder alignment is critical.

Critical Path, Schedule, and Nonfunctional Requirements

  • Critical Path concept:
    • The longest sequence of dependent tasks that determines the project duration; any delay in a task on the critical path delays the entire project.
    • Noncritical paths may have slack; tasks on those paths can be delayed without delaying the project, but only if other tasks keep the critical path on track.
    • The video uses analogies to illustrate:
    • Recipe with 10 ingredients from 10 suppliers: if one ingredient is late, the entire recipe is delayed; this is the CP concept.
    • Building a house: foundation and frame may define a short path for core construction, but other tasks like backyard finishing may be noncritical if not in contract scope; still, the overall project completion depends on the critical path.
  • Definition of Done (DoD): End-user or stakeholder acceptance triggers completion; a product is truly complete only when it works for the stakeholder and can be used as intended; DoD evolves with stakeholder feedback.
  • Nonfunctional requirements (NFRs):
    • Functional requirements specify what the system should do; NFRs specify how it should perform (quality attributes).
    • Examples: reliability (car should start and run), availability, performance, security, portability, maintainability, usability.
    • In PM, NFRs should be included in the scope to prevent leakage of critical constraints; ensure the product remains sustainable and maintainable after delivery.
  • Sustainability and self-sufficiency: The delivered system or component should remain usable and valuable after the project closes (self-sustaining value). Include checks for long-term viability.

Program vs Project and Year-by-Year Budgeting

  • Distinguishing program vs project:
    • A program contains multiple related projects coordinated to achieve strategic outcomes; programs may span multiple years.
    • Projects have start and end; programs oversee several projects and their interdependencies.
  • Year-by-year budgeting and audits:
    • In practice, funding is often allocated by year or quarter; long multi-year funding requires planning to satisfy audits and regulatory requirements.
    • The speaker warns against funding a multi-year project as a single long project; instead, break into annual projects, with yearly sign-offs and updates to avoid tax and regulatory issues.
    • If business support is uncertain, negotiate an annual bucket that can be replenished; ensure resources are retained and not released mid-year; avoid drastic changes at year-end.
  • Practical approach:
    • Divide multi-year initiatives into yearly programs and evaluate yearly earned value; close out each year and start another with updated assumptions and risk profile.
    • Engage business partners early for commitment to annual budgets to prevent disruption and ensure continuity of resources.

Value, Reputation, and Leadership Ethics

  • Value communication and leadership:
    • Do not claim the entire value of the organization; attribute contributions to relevant projects; communicate results clearly; avoid credit hogging.
    • Leaders support the team and acknowledge their analysis; avoid taking credit; use the opportunity to strengthen trust with stakeholders.
  • Stakeholder transparency and governance:
    • Be transparent with stakeholders about material variances, especially when underspent or overspent is significant (e.g., millions); escalate to the manager first, then to the stakeholder if necessary.
    • Blind-siding can erode trust; keeping the manager informed helps manage communications and risk.
  • Practical governance tips:
    • When variances are minor, report with a plan to adjust; when major, coordinate a joint communication with the manager present; ensure the stakeholder feels informed and in control.
    • Use consistent communication patterns; avoid micromanagement; provide action items and next steps; keep leadership comfortable with the plan.

AI, Prompting, and Real-World PM Practice

  • AI as an enabling tool, not a replacement:
    • Use AI to draft plans, generate questions for business stakeholders, and brainstorm tasks; use Monte Carlo simulations to estimate times; use digital tools to augment planning.
    • Recognize AI can hallucinate; validate outputs with domain knowledge; do not rely on AI as the sole authority.
  • Prompting strategy:
    • Act as a domain expert; provide a one-page project description; request a comprehensive task list with estimates; use Monte Carlo for timing; draft user stories.
    • Be explicit about the role and expectations when engaging AI to ensure useful outputs.
  • Practical advice:
    • Bring business domain questions to meetings; show you have done homework; build trust with stakeholders by being prepared.
    • The key is not to replace human judgment but to augment it; use AI to accelerate analysis while maintaining governance and accountability.

Exam Approach and Real-World Scenarios

  • Exam constraints:
    • Examiners may not allow heavy tools like Rally or Excel; expect to evaluate using a simplified, highest-time path method.
    • The correct answer often corresponds to the critical path (the longest duration path in the task network).
  • Real-world scenario approach:
    • When faced with multiple potential paths, identify the critical path; evaluate if a path is critical; do not rely on the shortest path.
    • Understand that project health metrics must be interpreted in context of the entire project (EV, PV, AC; CPI, SPI).
  • Cultural and organizational dynamics:
    • Projects interact with the organizational culture; leverage ITTC and similar programs to facilitate planning and collaboration.
    • Group work and stakeholder involvement are essential; ensure group progress and alignment on the project choice.

Quick Recap of Key Formulae and Concepts

  • Earned Value Management metrics:

    • PV = Budgeted Value of Planned Work
    • EV = Budgeted Value of Work Performed (BCWP)
    • AC = Actual Cost
    • CV = EV - AC
    • SV = EV - PV
    • \mathrm{CPI} = \dfrac{EV}{AC}
    • \mathrm{SPI} = \dfrac{EV}{PV}

  • Interpretation rules:

    • CPI > 1: cost under budget; CPI < 1: cost overrun
    • SPI > 1: ahead of schedule; SPI < 1: behind schedule

  • Definition of Done and Nonfunctional Requirements integration:

    • DoD reflects stakeholder acceptance; NFRs include reliability, performance, security, usability, etc.

  • Value-focused PM practice:

    • Track not just spend but value delivered; communicate with stakeholders; plan for reuse and broader organizational value.

  • Critical Path thinking:

    • The CP determines project duration; manage CP tasks with particular vigilance; allow slack on non-critical paths when possible without compromising the schedule.

  • Yearly program management:

    • Break multi-year programs into yearly projects; plan annually; manage audits; ensure resources retention and stakeholder alignment.

  • Leadership and ethics:

    • Credit distribution, transparency, and accountability are core to credible leadership.

  • AI in project management:

    • Use AI to augment planning and analysis; validate outputs; maintain human oversight and governance.

  • Nonviolent language around risk and problem-solving:

    • Emphasize problem-solving and collaborative action when facing variances; maintain calm and professional communication with stakeholders.

  • Real-world final note:

    • The material emphasizes that project success is about delivering business value, managing cost and schedule, maintaining stakeholder trust, and ensuring long-term sustainability and reusability of solutions.