Applying Earned Value Management to Software Intensive Programs 1

Applying Earned Value Management to Software Intensive Programs

Many statistics generation projects had been declared too costly, too late. And often do not paintings proper. Applying appropriate technical and management strategies can significantly improve the cutting-edge scenario. The foremost reasons for growth in those huge-scale programs may be traced to numerous causes related to overzealous advocacy, immature generation, lack of corporate technology roadmaps, requirements instability, ineffective acquisition strategy, unrealistic software baselines, insufficient structures engineering, and work-force issues. This article affords a quick precis of 4 strategies to clear up these problems.


Establishing a Process for Requirements Definition and Developing the Technical, Cost, and Schedule Baselines

We all realize the significance of having a prompted, nice painting pressure, but even our finest humans can’t carry out at their pleasure. At the same time, the manner is not understood or no longer working at its exceptional. A nicely described procedure is important in defining the necessities and completing the initial value and timetable estimate. The proper use of Performance-Based Earned Value® (PBEV) affords for the integration of undertaking technical scope, schedule, and fee goals; and the status quo of a baseline plan for performance size. Additionally, using an analytic application to assign probable price and agenda based on real performance affords practical projections of future overall performance. The success of the mission may be aided by defining the first-rate targets, using making plans resources and costs that are directly related to one’s objectives, measuring accomplishments objectively in opposition to the plan, using identifying overall performance developments and troubles as early as possible, and through taking well-timed corrective movements.

That maximum large software applications get into a problem is a proven phenomenon. Therefore choosing the precise set of software metrics for the song is important to application success. Practical Software Measurement (McGarry, Card, Jones; Addison-Wesley, 2002) identifies seven information categories and expands these records classes into measurable concepts and potential metrics.

For Earned Value purposes, the most effective software program metrics relate to product size, schedule, nice, and development. For software program intensive applications, measures of the amount (e.G. Number of traces of code completed) do not accurately reflect the best aspects of the work carried out on neither this system nor the real progress on account that gadgets which include lines of code finished doing not seize objects inclusive of integration, testing, etc.

Size is often measured as Source Lines of Code (SLOC) or Function Points and used as a sizing measure for budgets and earned cost using a percentage crowning glory approach. There are critical issues with this method. First, there has traditionally been a considerable mistake in estimating SLOC. And, the wide variety of traces of code completed does not always mirror the quality or total progress in the direction of a performance purpose. Therefore, any development metric primarily based solely on SLOC is quite volatile. Whether SLOC, function factors, Use Cases, or some different size artifact is selected, a careful manner must be utilized to establish a credible length metric. It is suggested that in addition to tracking progress towards a goal, a size boom should also be tracked.


Schedule metrics and processes usually relate to entirety milestones also are commonplace monitoring metrics. Sometimes these milestone definitions and of entirety criteria lack quantifiable objectives. An incremental construct is often launched that doesn’t contain all of the deliberate useful necessities, or a developer claims victory after simply trying out the nominal instances.

Progress metrics can be complicated for big software program programs. It is usually agreed that no software is brought defect free. Software engineers have hoped that new languages and new processes might greatly reduce the variety of delivered defects. However, this has now not been the case. Software remains added with an extensive quantity of defects. The bodily and sensible software barriers trying out (the best way to determine if an application will paintings is to write the code and run it) ensure that huge programs can be launched with undetected errors. Therefore, defects discovery and elimination is a key metric for assessing application fine.

Applying Performance-Based Earned Value (PBEV)

Performance-Based Earned Value® (PBEV) is an enhancement to the Earned Value Management Systems (EVMS) preferred. PBEV overcomes the same old’s shortcomings about measuring technical overall performance and exceptional (satisfactory gap). PBEV is based on requirements and models for structures engineering, software engineering, and project control that emphasize quality. The distinguishing characteristic of PBEV is its consciousness of the consumer requirements. PBEV gives standards and steerage for fee effective procedures that specify the only measures of price, agenda, and product first-rate performance.

Because of the pleasant gap inside the EVMS preferred, there may be no assurance that the reported earned fee (EV) is based totally on product metrics and the evolving product first-rate. First, the EVMS standard states that EV is a measurement of the quantity of labor achieved and that different processes control the great and technical content of labor accomplished. A software program manager should ensure that EV is likewise a measurement of the product exceptional and technical maturity of the evolving work products instead of simply the amount of labor completed. Second, the EVMS concepts cope with best the task work scope. EVMS ignores the product scope and product necessities. Third, the EVMS trendy does now not require precise, quantifiable measures of development. It states that goal EV strategies are desired, but it additionally states that management evaluation (subjective) can be used. In the evaluation, other requirements specify objective measurement. Fourth, EVM is looked at as if it would be a chance management device. However, EVMS changed into now not designed to control danger and provides no steerage on the subject.

PBEV is a hard and fast concept and hints that designate the best measures of value, timetable, and product excellent overall performance. It has numerous traits that distinguish it from traditional EVMS by augmenting EVMS with four additional ideas and sixteen additional recommendations.


PBEV dietary supplements conventional EVMS with the quality practices. Its standards and suggestions enable real integration of mission cost, agenda, and technical overall performance. The distinguishing characteristic of PBEV is its recognition of consumer necessities. Measures of product scope and product pleasant are included in the mission plan. Progress is measured towards a plan to satisfy all purchaser requirements. Measuring the wrong things does no longer dilute management interest. Consequently, management can take speedy corrective actions on deviations that threaten patron pleasure and business organization goals.