There's always someone talking about how Earned Value can be used for Agile, or how Agile is the same as Earned Value. Most of these discussions are fundamentally flawed, because they start with the Agile paradigm and try to wedge in the Earned Value concepts.
Some of the discussions are just flat out wrong, using wrong terms, using wrong principles. Then there are one or two that follow Wolfgang Pauli's quote:
This isn't right. This isn't even wrong. - Wolfgang Pauli (1900-1958) commenting on a journal paper submitted by a colleague.
But here's a paper that gets it right.
"Earned Value for Agile Development," John Rusk, Software Tech News.
Just remember successfully connecting two disparate concepts - EV and Agile - requires care in choosing where to start. Here's a couple of starting points that have served me well in the past
- "Making Agile Development Work in a Government Contracting Environment," Agile Development, June 25-28, 2003, Salt Lake City, UT.
- "Agile Project Management Methods for ERP: How to Apply Agile Processes to Complex COTS Projects and Live to Tell About It," Extreme Programming and Agile Methods: XP/Agile Universe 2002, pp. 70–88, Springer Verlag, LNCS 2418, Editors, Don Wells and Laurie Williams.
These are getting a bit long in the tooth, but the work was successful in the early days of orthogonal paradigms come together in the single program.
