Tracking Project Progress with Earned Value Management Metrics - A Real Case

Maria Teresa Baldassarre, Nicola Boffoli, Danilo Caivano, Giuseppe Visaggio


According to the Project Management Institute (PMI) project management consists of planning, organizing, motivating and controlling resources such as time and cost in order to produce products with acceptable quality levels. As so, project managers must monitor and control project execution, i.e. verify actual progress and performance of a project with respect to the project plan and timely identify where changes must be made on both process and product. Earned Value Management (EVM) is a valuable technique for determining and monitoring the progress of a project as it indicates performance variances based on measures related to work progress, schedule and cost information. This technique requires that a set of metrics be systematically collected throughout the entire project. A consequence is that, for large and long projects, managers may encounter difficulties in interpreting all the information collected and using it for decision-making. To assist managers in this tedious task, in this paper we classify the EVM metrics distinguishing them into five conceptual classes and present an interpretation model that managers can adopt as checklist for monitoring EVM values and tracking the project’s progress. At this point of our research the decision model has been applied during an industrial project to monitor project progress and guide project manager decisions.


  1. Pyster A.B., Thayer R.H., 2005, “Software engineering project management 20 years later”, IEEE Software, 22(5), pp.18-21.
  2. PMI, 2013, A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Fifth Edition, PMI.
  3. PMI, 2005, Practice Standard for Earned Value Management.
  4. NASA, 2010, Earned Value Management Web Site -
  5. DoD 2002, 5000.2-R, “Mandatory Procedures for MDAPS and MAIS Acquisition Programs”, April 2002.
  6. EVM, 2000, “The Earned Value Management Maturity Model”, Version 0.0, Initial Public Draft, Management Technologies”,
  7. DoD, 1998, The Program Manager's Guide to Software Acquisition Best Practices, Version 2.1.
  8. Marshall R.A., 2006, “The contribution of earned value management to project success on contracted efforts: a quantitative statistics approach within the population of experienced practitioners”, PMI 2006.
  9. Jaafari A., 1996, “Time and priority allocation scheduling technique for projects”, IJPM 14(5), pp.289-299.
  10. Wells E, Duffey M., 2003, “A model for effective implementation of earned value management methodology”. IJPM, 21(5),
  11. Raby M., 2000, “Project management via earned value”, Work study 49(1), pp6-10.
  12. Donzelli P., 2006, “A decision support system for software pm”, IEEE Sw, 23(4), pp.65-75.
  13. Garcia M.N., Quintales L.A, Penalvo F.J., Martin M.J., 2004,“Building knowledge discovery-driven models for decision support in pm” DSS, 38(2).
  14. Nkasu M.M., Leung K.H., 1997, “A resources scheduling decision support system for concurrent pm”, J. production research, 35(11), pp.3107-3132.
  15. Plaza M., Turetken O., 2009, “A model based DSS for integrating the impact of learning in project control”, Decision Support Systems, 47(2009), pp.488-488.
  16. Basili V.R., McGarry F.E., Pajerski R., Zelkowitz MV., 2002, “Lessons learned from 25 years of process improvement: the rise and fall of the NASA software engineering laboratory”, 24th ICSE 2002, pp.69-79.
  17. Tague N.R., 2004, The Quality Toolbox, Second Edition, ASQ Quality Press, 2004, pp. 390-392.
  18. Matthews C.R., 2006, “Linking the supply chain to TQM”, Quality Progress, November 2006.
  19. Christensen D.S., 2006, “Project advocacy and the estimate at completion problem”, J. Cost Analysis.
  20. Christensen M.J, Thayer H.R., 2001, The project managers guide to software engineering best practices, IEEE Computer Soc,
  21. Pressman R., 2002, Software engineering: a practical guide, Standish Group. 2010, “Chaos summary 2010”, the Standish Group International, Inc. TR, 2010.
  22. Australia, 2006. AS 4817-2006 Australian Standard 4817- 2006: Project performance measurement using EV.
  23. Fleming Q.W, Koppelman J.M, 1998, “Earned Value project management: a powerful tool for software projects”, CrossTalk, The J.of Defense Software Engieering, 4, 19-23.
  24. Sulaiman T, Barton B, Blackburn T., 2006, “AgileEVM - Earmed Value Management in Sccrum Projects”, Proc.of AGILE 2006 Conference IEEE CS.
  25. Boehm B., 2000, Software Cost Estimation with COCOMO II. Prentice Hall, New Jersey.
  26. IFPUG, 2004, Counting practices manual v4.2.
  27. Smith J., 2000, “The estimation of effort based on use cases”.
  28. Efe P., Demirors O., 2013, “Applying EVM in a software company: benefits and difficulties”, 39th Euromicro Conference series on software engineering and advanced applications, pp.333-340.

Paper Citation

in Harvard Style

Teresa Baldassarre M., Boffoli N., Caivano D. and Visaggio G. (2015). Tracking Project Progress with Earned Value Management Metrics - A Real Case . In Proceedings of the 17th International Conference on Enterprise Information Systems - Volume 2: ICEIS, ISBN 978-989-758-097-0, pages 502-508. DOI: 10.5220/0005470305020508

in Bibtex Style

author={Maria Teresa Baldassarre and Nicola Boffoli and Danilo Caivano and Giuseppe Visaggio},
title={Tracking Project Progress with Earned Value Management Metrics - A Real Case},
booktitle={Proceedings of the 17th International Conference on Enterprise Information Systems - Volume 2: ICEIS,},

in EndNote Style

JO - Proceedings of the 17th International Conference on Enterprise Information Systems - Volume 2: ICEIS,
TI - Tracking Project Progress with Earned Value Management Metrics - A Real Case
SN - 978-989-758-097-0
AU - Teresa Baldassarre M.
AU - Boffoli N.
AU - Caivano D.
AU - Visaggio G.
PY - 2015
SP - 502
EP - 508
DO - 10.5220/0005470305020508