This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
September/October 2010 (vol. 27 no. 5)
pp. 2-7
Hakan Erdogmus, Kalemun Research
This article explains the concept of earned value for tracking progress in software projects. It discusses the benefits and limitations of earned value. The earned value approach deserves more attention from the software development community in contexts where planning and estimation is part of the culture. The presence of a point of reference against which to compare progress introduces additional metrics that better known techniques do not incorporate. Although these additional metrics are not applicable when plans and estimates are absent, earned value can still be used with proper adaptations.
Index Terms:
software engineering, project management, performance measurement, earned value, earned value management, burndown charts, schedule variance, cost variance
Citation:
Hakan Erdogmus, "Tracking Progress through Earned Value," IEEE Software, vol. 27, no. 5, pp. 2-7, Sept.-Oct. 2010, doi:10.1109/MS.2010.130
Usage of this product signifies your acceptance of the Terms of Use.