The History of Earned Value Management

By Victor Hoang · Updated Oct 23, 2026

Picture the early 1960s. The Pentagon's contractors were building missiles and spacecraft that had never existed. The government shared the cost risk. Each month, contractors reported what they'd spent against what they'd planned to spend.

Earned value management took shape in the United States in the 1960s. PERT/Cost was adopted in 1962. The Air Force wrote the first earned value criteria for the Minuteman missile in 1963 to 1965. The Department of Defense issued its Cost/Schedule Control Systems Criteria (C/SCSC) in December 1967. Its ideas are older than those dates, but the method with its formulas is a product of defense contracting. The through-line is a measure that kept leaving its home. It moved from the Air Force to the Pentagon, from the Pentagon to industry in 1998, and from there to professional bodies and other countries.

Wayne Abba, who spent 17 years as a senior program analyst in the Pentagon's acquisition office, later wrote that this kind of "spend plan" reporting had no objective relationship to the work accomplished. This article follows the fix for that problem, and keeps three things apart: the factory habits that came before, the criteria that defined the method, and the standards that spread it. For the concept itself, see earned value management. For the wider field, see the history of project management.

Timeline at a Glance

Dates here separate the day a policy was issued from the day it was adopted.

Factory Standards (1900s-1950s)

Industrial engineers compare planned standards with earned ones

Start on a factory floor. Industrial engineers have set a standard time or cost for a task, and at the end of the shift someone counts the pieces finished and prices them at the standard. That price is what the shift "earned", and the comparison to what the shift actually cost is the whole idea. In a 1993 interview, retired Air Force Lieutenant General Hans Driessnack said the concept came "right off the factory floor" from industrial engineers, who compared their planned standards with earned standards and actual costs. The PMI article that records his remark places these engineers among the followers of Frederick Taylor, Frank and Lillian Gilbreth and Henry Gantt. Gantt's own charts did hold promises up against performance, a story told in the history of the Gantt chart and in the history of scientific management.

That makes the factory a precursor, not the concept. Nobody in those shops was running a program with a work breakdown structure, a network schedule and a formal system audited by the customer. Project historian Patrick Weaver says the foundations were in place by 1960: construction and engineering cost controls by the 1920s, critical path scheduling and PERT by 1957, and work breakdown structures as part of PERT. He cites a 1909 engineering text on cost keeping, by Halbert Gillette and Richard Dana, as one source of the cost-control tradition, and notes that such controls were required on US government works from the 1930s. They worked well where the design was known and quantities were measurable, such as excavating rock.

They failed on a new kind of contract. Where a contractor was inventing a missile guidance system, spending told you little about progress. Weaver names this failure of cost-plus development work as the catalyst for the method. The network side of the story is told in the history of the critical path method.

What this means for teams today: a plan-versus-actual cost chart tells you how fast money leaves, not how much was built. If your status report has only those two lines, you are still in the 1950s.

The PERT/Cost Experiment (1960-1964)

The Navy and NASA try to attach money to the network

By the early 1960s the Pentagon had a problem and a political push to solve it. Weaver credits the McNamara reforms, which began when Robert McNamara became Defense Secretary in 1961, for the demand that cost be tied to weapon systems and tasks. The Navy had already linked resources to its PERT network on the Polaris program in 1960, and Weaver dates a joint Stanford and Navy effort to expand PERT to include resources to 1960 through 1962. The result was PERT/Cost. On June 1, 1962, McNamara and NASA's Robert C. Seamans Jr. adopted it as the standard supervisory format for major weapons and space programs.

PERT/Cost introduced the vocabulary that survives in EVM. The OSD PERT Coordinating Group set out six concepts: a work breakdown, work packages with charge numbers, networks, a link between time and cost at the work package level, cyclic updating of estimates, and continuous evaluation of actual against planned. Weaver notes that its report formats, such as the Cost of Work report, are the basis for most EVM reports in use today. If you want the structure it was built on, read about the work breakdown structure and the PERT chart.

It also had a flaw that gave earned value its reason to exist. PERT/Cost judged progress from supervisors' estimates to complete, which Weaver calls the weakness of the system. By 1964 more than ten variations existed, each with its own how-to-manage requirements, and industry, in Abba's words, viewed the proliferating systems with alarm. Weaver adds a common misreading: many people thought PERT/Cost meant pricing each activity of the network, which was not the intention. The Air Force commissioned a review of the system from the Mitre Corporation in June 1964, and the Defense Department kept developing it afterward. Industry complaints were aired at an Air Force Systems Command conference in Monterey, California, in May 1962, and Weaver says they triggered the next step.

What this means for teams today: a system that depends on frequent re-estimating rewards the optimistic estimator. Earned value replaced the estimate with a measure fixed in advance.

The Minuteman Criteria (1963-1972)

The Air Force defines a good system instead of dictating one

Two people carried the next step. The first was A. Ernest Fitzgerald, a contractor who later became an Air Force executive. In 1963, building on the PERT/Cost work, the Air Force applied a criteria-based approach on the Minuteman missile program; the criteria were brief statements of attributes a contractor's system had to meet, drawn from industry best practice. A contractor could use any scheduling system, provided it showed the sequence of work and its key interdependencies. Fitzgerald formed a consulting firm, Performance Technology Corporation, and it delivered the Earned Value Summary Guide to the Air Force's Ballistic Systems Division in draft on February 25, 1965 and in final on April 30, 1965. Its introduction defined the idea in a sentence that is still a good one: an estimated value can be placed on all work to be performed, and that value is "earned" when the work is done.

On March 21, 1965, the first criteria went to the division: 11 specifications and a checklist of 57 items, added to the contracts of the eight Minuteman associate contractors. The second person was Hans "Whitey" Driessnack, then an Air Force officer, who, reacting to the lack of flexibility in the PERT/Cost requirements, drafted ten criteria describing the control systems an effective contractor would need. The two lines merged when Fitzgerald was appointed Deputy Assistant Secretary for Management Systems in 1965. The Cost/Schedule Planning and Control Specification, known as C/SPEC, was published in June 1966 as Annex 4 of Air Force Systems Command Manual 70-5. It had 26 specifications, including the work breakdown structure, work packages and integration with the schedule, and new concepts such as cost accounts and management reserve. Weaver says it was revised in June 1967 and restated as 35 criteria.

Then it went Defense-wide. Robert N. Anthony, the Assistant Secretary of Defense (Comptroller), decided the approach deserved a DoD-wide requirement and a joint-service team was appointed. The result was Department of Defense Instruction 7000.2, "Performance Measurement for Selected Acquisitions", issued on December 22, 1967. That date needs care. Weaver says the first version required C/SCSC but did not describe the criteria, and it promised a separate guide. A coordination draft followed on June 28, 1968, joint implementation procedures on September 10, 1970, and finally a proper C/SCSC Joint Implementation Guide signed on January 27, 1972. DoDI 7000.2 was reissued in 1977 with the 35 criteria. Abba, writing in 1997, simply says C/SCSC was "issued in 1967 as a DoD Instruction" and that the 35 criteria were organized in five parts: organization, planning and budgeting, accounting, analysis and revisions.

Two vocabulary notes help when reading old documents. The Air Force specification called its measures PVWS (Planned Value of Work Scheduled) and PVWA (Planned Value of Work Accomplished), according to Weaver, and the four-letter BCWS, BCWP and ACWP became the standard terms later in the line.

What this means for teams today: write down what a good control system must do, not the forms it must use. The criteria idea was sound; the next era shows how it decayed.

The Compliance Years (1972-1991)

Reviews grow, paperwork follows, and the A-12 shows the gaps

By the 1980s many contractor program offices had specialists whose job was preparing monthly cost and schedule reports for government review teams. Abba, who watched this from the Pentagon, described how the guide grew. The first guide in 1972 ran 76 pages with 12 on the discussion of criteria; by 1987 it had 102 pages and 20 pages of discussion, and the discussion, meant to clarify, became de facto requirements. His example is the six-month rolling wave: guidance said detailed planning about six months out should suffice, depending on the work, and in practice contractors who used six months passed review, reviewers came to expect it, and consultants taught it.

The result was a specialist subculture. Abba wrote that earned value was perceived by many as a mere financial reporting requirement and was over-implemented by specialists, while technically oriented managers were put off by the jargon, and that some contractors did what they had to do to pass the review while the monthly reports went ignored by project managers. A 1974 instruction (DoDI 7000.10) set the Cost/Schedule Status Report as a standard way to report summarized cost and schedule performance. A 1984 study sponsored by the Office of the Secretary of Defense found industry strongly supported the criteria-based approach, and in 1989 the C/SCSC office moved from the Comptroller to Acquisition, which Abba describes as the start of the shift away from financial management.

Then came a failure that the system did not prevent. Abba's account of the A-12 cost overrun describes a Navy stealth bomber that was revealed to be in serious cost and schedule difficulty; because the program was highly classified, his office was denied its routine oversight of contractor cost and schedule data. The Defense Department's Inspector General reported that Under Secretary of Defense John Betti had erred in managing the overrun, and the Secretary of Defense accepted Betti's resignation on December 12, 1990, effective at year end. The Secretary of Defense canceled the program on January 7, 1991, according to the Government Accountability Office. Abba also points out that EVM cannot prevent overruns on its own, and managers must use the data. What followed was a reaffirmation, not a retreat: Abba says the earned value requirement was reaffirmed in acquisition regulations in 1991, after a joint DoD and industry quality survey in 1989 to 1991 that produced 18 recommendations.

What this means for teams today: a control system that only produces reports for an auditor will be ignored by the people who could act on it. Measure for the person who has to decide.

The Industry Standard (1993-2003)

The Pentagon hands earned value to the contractors

The pivot came with reform. In 1993 DoD formed an acquisition reform office at the Deputy Under Secretary level. In January 1994 a policy memorandum introduced Integrated Baseline Reviews, led by program managers rather than auditors. A December 1994 study by Coopers & Lybrand and TASC put the value-added cost to industry of doing business with DoD at 18 percent, of which 0.9 percent was attributed to C/SCSC, and most of that came from practices C/SCSC did not require. In 1995 the Performance Measurement Joint Executive Group that governed C/SCSC was abolished, and DoD signed a trilateral memorandum of understanding with Australia and Canada pledging to reduce differences between government and commercial management practices.

In 1996 the criteria changed. According to Weaver, DoD regulation 5000.2-R, dated March 15, 1996, reduced the criteria from 35 to 32 and applied them to flexibly priced development contracts of $70 million or more and procurement contracts of $300 million or more in fiscal 1996 dollars. The same year, OMB Circular A-11, Part 3, issued on July 16, 1996, required earned value as an integral part of fixed-asset planning for all proposed and ongoing acquisitions across federal agencies; NASA, NOAA, the FAA, the Coast Guard, the IRS and the FBI had previously adopted DoD requirements for their large contracts.

The decisive move was to let industry write it. Weaver says Gary Christle and Wayne Abba turned the work breakdown structure military standard into a guide and invited the National Defense Industrial Association and other industry groups to write an earned value standard that could replace the DoD regulation. The ANSI/EIA-748 standard, approved in May 1998 (the document itself is dated June 1998), says its guidelines were prepared by an industry team of the NDIA Management Systems Subcommittee, chaired by Bob Surrency of Lockheed Martin, and describes them as purposely high level and goal oriented. Weaver puts the ANSI adoption in July 1998 and DoD's adoption in 1999. Two things shifted, in his words: EVM came to be seen as a project management technique rather than a financial one, and ownership passed from the Defense Department to private industry.

The method also crossed to a wider profession. Weaver notes EVM appeared in the 1987 PMBOK only as a glossary term, as "earned value analysis" in the 1996 edition, and that the 2000 edition replaced the four-letter terms with PV, EV and AC, a change he says seems to have been instigated by PMI. The Performance Management Association, formed in 1985, merged into PMI in 1999 as the PMI College of Performance Management, which Weaver says had a major influence on EVM's place in PMI documents. See the PMBOK Guide for what the guide covers.

What this means for teams today: a practice owned by the people who use it survives longer than one mandated from above. Writing your own criteria beats waiting for an auditor to write them.

The Global Standard (2003-present)

Earned schedule, ISO and the audit guides carry EVM beyond defense

By 2003 one weakness was well known. Traditional EVM expresses schedule performance in cost units, so at the end of a project all the work is done and the schedule performance index returns to 1.0 whether the project finished early or very late. Walt Lipke addressed this in "Schedule is Different", published in The Measurable News in 2003, which introduced earned schedule. It uses the same data as traditional EVM but moves the calculation from the cost axis to the time axis, so it can predict a completion date. Weaver reports that university studies found the duration predictions as accurate as cost predictions from traditional EVM. The Earned Schedule site hosts the method's documentation.

The standards multiplied. Weaver lists AS 4817:2003 in Australia, which replaced criteria with 11 steps and 54 requirements, the PMI Practice Standard for Earned Value Management in 2005 with a second edition in 2011, and the 2019 ANSI/PMI standard that treats earned schedule as a core component. ISO 21508:2018 followed, and the US standard continued through revisions B (2007), C (2013) and D, approved on January 8, 2019, still with 32 guidelines. Other countries adopted it on their own timelines. Weaver notes Sweden used it on the Gripen fighter contract signed on June 30, 1982, and that the UK Ministry of Defence began mandating it for a range of projects on January 1, 2006.

Today's reference for non-defense work is audit-oriented. GAO's Cost Estimating and Assessment Guide, issued on March 12, 2020 as an update of the 2009 original, includes best practices for the use of EVM. Weaver's summary of the method's identity is still useful: EVM is a performance management tool and not a cost accounting function, and the data it reports is only as good as the baseline behind it. Weaver adds that the 2019 PMI standard considers the application of EVM to agile projects. The baseline schedule it measures against comes from methods such as the critical path method.

What this means for teams today: use the formulas for what they can do, forecast cost and time from a baseline, and do not treat the index as a verdict. A project with a clean index and a stale baseline is still in trouble.

Key People

Key Facts

• PERT/Cost was adopted on June 1, 1962 by Defense Secretary McNamara and NASA's Robert Seamans as the standard format for major weapons and space programs.
• DoD Instruction 7000.2 was issued on December 22, 1967, but the criteria themselves were detailed in a guide that followed in 1972.
• A 1994 study attributed 0.9 percent of an 18 percent extra cost of doing business with DoD to C/SCSC.
• OMB Circular A-11, Part 3, issued July 16, 1996, required earned value for fixed-asset acquisitions in all federal agencies.
• The ANSI/EIA-748 standard was drafted by an industry team, and its 32 guidelines are still in force in the 2019 revision D.
• The 2000 PMBOK Guide replaced BCWS, BCWP and ACWP with PV, EV and AC.

The Pattern Behind the History

This is our synthesis, not published research. We call it the Mandate Loop, and its five points repeat through this history:

• A cost problem appears. Money spent no longer tracks work done, first in factories and then in cost-plus development.
• A measure replaces an estimate. Supervisors' guesses at completion give way to a baseline fixed in advance.
• A mandate follows. Criteria become reviews, reviews become checklists, and compliance replaces judgment.
• Ownership moves outward. The Air Force, then the Pentagon, then industry, then PMI and ISO take the method over.
• A missing dimension gets patched. Schedule in time arrives with earned schedule, long after the cost formulas.

What It Teaches Teams Today

• Measure work done, not money spent. Plan the value of each work package before you start, and credit it only when the work meets its stated measure.
• Separate the baseline from the estimate. Keep a fixed plan and update the forecast, so a new estimate cannot quietly rewrite the plan.
• Write criteria for outcomes. The 35 criteria went wrong when discussion text became rules. Say what the system must show.
• Watch schedule in time. An index based on cost units can read 1.0 on a late project, so add a date forecast.
• Know where your tool came from. Who invented project management and the project management timeline show how methods drift once they spread.