Project Managers

The Project Management Social Network | Project Manager Jobs

I have just finished reading another article where a proponent of Earned Value seems to deliberately set out to do as much damage to the general acceptance of the methodology as possible!

From its inception EV has been plagued with confusion generated by acronyms. EV ‘experts’ used to prove how knowledgeable they were by confusing business managers with a barrage of acronyms and formula. Before the turn of this Century, a decade ago, leaders in the profession recognized one of the major barriers to acceptance of EV was a general lack of understanding and sought to simplify the ‘alphabet soup’ that was making EV too hard for busy managers to understand.

ANSI EIA 748 A released in 2002, AS 4817 2003 released in 2003 and the 2000 version of the PMBOK® Guide all adopted a common, simple set of acronyms:

EV = Earned Value instead of BCWP (Budgeted Cost of Work Performed)

PV = Planned Value instead of BCWS (Budgeted Cost of Work Scheduled)

AC = Actual Cost instead of ACWP (Actual Cost of Work Performed)

These standards between them cover some 90% of the world’s Earned Value community –the UK being a noticeable exception! The intention was (and is) to demystify the process of Earned Value so managers could understand the data their project ‘controls’ staff were generating and use the information to make wise decisions. A really great idea! EV is an extremely useful and powerful tool if the data being presented to management is understood and acted upon.

What I cannot understand is why, in 2011, so many self professed advocates of EV are so keen to continue to cause confusion by writing articles using the old, superseded acronyms (UK based authors writing for a UK audience excepted).

  • Is it to try to look clever by confusing the ‘dumb reader’?
  • Is it to attempt to re-wind history back to the 1990s?
  • Are they actually opposed to the general use of EV and seek to prevent its general adoption by spreading confusion?

The UK (where EV is used to a limited extent) is the only place that still published standards that use the old acronyms. These ‘standards’ are primarily from the Association for Project Management rather than British Standards.

Surely it’s time everyone used the same acronyms for the same item in an EV article and dragged themselves into the 21st century – it’s hard enough getting EV accepted in senior management circles without so-called experts and practitioners creating excuses for ‘not understanding’ by reverting to outdated acronyms, even in the UK??

What do you think?

Views: 30

Tags: Earned, Value

Comment

You need to be a member of Project Managers to add comments!

Join Project Managers

Comment by William Pirkey on November 30, 2011 at 8:29am
I was introduced to the BCWP/BCWS in the 90's when I first started in IT PM. It made no sense to me! The numbers I was getting--by the definition of the calculation--meant little to nothing since it had to be combined with another value to show variance. It was the variance that had to be managed.

When I started reading the PMBOK Guide, EV and AC made a LOT more sense.

SPONSORED LINKS

FOLLOW US
@projectnetwork


MOST ACTIVE MEMBERS THIS WEEK

POPULAR BLOG POSTS

© 2012   Created by Miles.

Badges  |  Report an Issue  |  Terms of Service