Implementing a project performance measurement system using Earned Value requires, at the very least, and as an absolute pre-requisite, an understanding of the key terms used within that domain.

The Australian Standard AS-4817-2006, “Project Performance Measurement using Earned Value”, outlines a set of key definitions, which I will list below. If you are a new entrant into the Earned Value world or a seasoned practitioner, check whether these terms ring a bell or better, make part of your daily terminology. If you are not certain what some of these terms mean it is time to get back to the literature (preferably the standard) and ensure they are as clear to you and unambiguous as possible.

  1. Activity
  2. Actual Cost
  3. Baseline
  4. Budget
  5. Budget at Completion
  6. Constraint
  7. Control Account
  8. Corrective Action
  9. Cost Variance
  10. Critical Path
  11. Direct Costs
  12. Earned Value
  13. Estimation at Completion
  14. Estimate to Complete
  15. Float
  16. Indirect Costs
  17. Management Reserve
  18. Milestone
  19. Network Schedule
  20. Other Direct Costs
  21. Performance Measurement Baseline
  22. Planned Value
  23. Project Budget
  24. Schedule Variance
  25. Undistributed Budget
  26. Variance at Completion
  27. Work Breakdown Schedule
  28. Work Package

If your goal is to establish a Performance Measurement Baseline (PMB) for your project you should be able to utilize each and every one of these terms before you could move into the more esoteric area of developing a PMB and subsequently monitoring your project’s performance using Earned Value.

Think about it!

Related posts:

  1. Overview of the Earned Value Performance Measurement Process
  2. The Australian Standard for Measuring Project Performance Using EV
  3. Earned Value Management (EVM) for Dummies – Part 2
  4. Earned Value Management (EVM) for Dummies – Part 1
  5. Implementing Earned Value Management in Agile

2 Comments

  1. Pingback: Mike Clayton

  2. Pingback: Shim Marom

  3. Pingback: Shim Marom

  4. Pingback: Barry Hodge

  5. Pingback: Cornelius Fichtner

  6. Pingback: Cornelius Fichtner

  7. Cornelius Fichtner

    Shim – I’d like to add on at the very top of the list:

    0. Define your Project Scope

    In my opinion this precedes everything else. If you cannot properly define your project scope you will not be able to identify/calculate any of the other KPIs.

    Reply

    • Hi Cornelius, thanks for commenting out.

      Although I agree in principle (defining the scope is rather important) I intentially included only those items specifically mentioned in the definition section of the guide. Cetainly for anyone to attempt involvement in project performane measurement they ought to have clear understanding of all project management aspects, including the need to define the scope.

      Cheers, Shim.

      Reply

  8. Pingback: Option Brasil

  9. Pingback: LabCEO/UFF

  10. Pingback: Juan Camilo Villamiz

  11. Pingback: jalsina1

  12. Pingback: Juan C

  13. Pingback: Overview of the Earned Value Performance Measurement Process | quantmleap

Leave a Reply

Your email address will not be published. Required fields are marked *

*


one + = 3

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

CommentLuv badge