Project Management

Please login or join to subscribe to this thread

How are you guys dealing with agile practices and earned value?

linkedin twitter facebook   Agile   Earned Value Management  
avatar
Ricardo Cantu Team leader, Risk and Benefits realization management| MTESS Quebec, Quebec, Canada
Hello PM friends!
As you know, Agile practices accepts, even welcomes, changes in scope. This could be done at the beginning of every iteration, typically of 2-3 weeks. Some argue that earned value is outdated and is against Agile principles.

Have you stopped using earned value?
Have you adapted the basic earned value methodology to measure project performance?
Sort By:
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
First of all, agile is not software or IT, but I will assume that in your question. Second, agile is not a method or methodology. Thrid, welcomes changes but changes are managed and controled and people can not make changes when they want. You can use (I am doing that) earned value with any agile software development method you use or the same method applied to any other type of solution. There is a lot into the internet about agile and earned value convined so I think the best way is to search for that. Most of the papers were written by the agile software development methods authors.
avatar
Denise Canty Agile Coach, Life Coach, Author, Senior Project-Program Manager| Cenden Company Washington, Dc, United States
I think that EVM works pretty well with Agile. One has to use story points, but the results are good. The downside is that "value" can be measured with EVM.
avatar
Ricardo Cantu Team leader, Risk and Benefits realization management| MTESS Quebec, Quebec, Canada
Thank you for your kind responses. Very good Sergio, you are right : Agile is not a software, nor a methodology.

We have Agile projects, not only in software development, and we use earned value when reporting performance too (during monitoring and controlling processes).
After reviewing performance in projects for some time, we decided to stop using SPI (schedule performance index) for single components. We have SPI for the whole project only and we are looking into how much it is making sense to people.
Our typical projects are multi-team having more than one backlog.
Do you still use component SPI? Did you base your performance on velocity measures only?

How about you Denise?
Do you measure value in “value” points or in actual benefits realization?

Please login or join to reply

Content ID:
ADVERTISEMENTS
ADVERTISEMENT

Sponsors