Using Earned Value on Agile Projects
By Mike Griffiths
Q: Does Earned Value work for software projects?
A: Absolutely, Earned Value Analysis (EVA) is a statically valid reporting approach that can be applied to any endeavour. It compares actual progress and spend against projected progress and spend.
Q: Can you use Earned Value on Agile projects?
A: You can, but I would not recommend it. There are fundamental problems using EVA on agile projects relating to baseline plan quality. Also there are better alternatives available for agile projects.
Earned Value analysis and reporting measures conformance and performance to a baselined plan. So, given that on agile projects we know that our initial plans are likely to change, why track progress against a weak plan?
An excellent reference to Earned Value reporting is “Earned Value Project Management, Second Edition” by Quentin Fleming, Joel M. Koppelman. In it the authors list 3 critical success factors for Earned Value reporting.
- Quality of the project’s baseline plan. Earned Value is compared against the baseline plan, whether the plan is accurate or not. Therefore, cost ‘overruns’ will occur if the project costs are under-budgeted, and scope creep will occur if the initial project scope hasn’t been adequately defined.
- Actual Performance against the Approved Baseline Plan. i.e. whether the actual performance tracks to the baseline plan.
- Management’s Determination to Influence the final results. Final results for a project based on earned value projections can be modified based on management’s commitment to take action as soon as deviations from the plan are observed.
Agile projects fail to meet the first two critical success factors. First, the quality of the original baselined plan is very low from a completeness and scheduling perspective. We could try to use EVA against our continuously evolving plans, but the figures become meaningless if you keep changing the baselined plan. Each time you do so the performance indexes and variances change making tracking and forecasting extremely problematic. Secondly, since our initial baselined plan may be little more than “today’s best guestimate“ critical success factor number 2 “whether the actual performance tracks to the baseline plan” would be more a matter of luck than anything else.
Given these challenges, what should replace EVA on Agile Projects? Are there agile equivalents of Cost Performance Index (CPI), Schedule Performance Index (SPI), Cost and Schedule variances (CV and SV), and Estimate at Completion (EAC)? The good news is that all of these metrics can still be obtained and even better, if you are using Cumulative Flow Diagrams, you are half way there already.
Mike Griffiths is an independent consultant specializing in effective project management. Mike was involved in the creation of DSDM in 1994 and has been using agile methods (Scrum, FDD, XP, DSDM) for the last 13 years. He serves on the board of the Agile Alliance and the Agile Project Leadership Network (APLN). He maintains a leadership and agile project management blog at http://www.LeadingAnswers.com