Dennis DavisConsultant| Davis ConsultingAntioch, Ca, United States
I'm looking for more tips/techniques on how to use earned value for software development projects; small, med & large in size? I've read the articles on gantthead but am still trying to gain a better understanding of how to use the technique for software projects that don't have obviously measurable tasks like a construction or other project would. Thoughts? Saving Changes...
I would submit that there really is no difference between a software project versus construction when it comes to applying EVM - it just seems that construction is easier because you have something you can see (brick, concrete, etc) versus software which seems intangiable. It's really not though - you can estimate by how many lines of code or measure by module or by project requirement. You just have to really think about how you are structuring your schedule and the project overall really. However, where I think most people have difficulty with when trying to apply evm is that evm requires a solid schedule to begin with. So, when scheduling a software project, it helps to have sme's that really think about the breakdown of what it takes to meet your project requirements. That is, they have to understand what workpackages need to be created and the tasks within those workpackages. Then they have to be good at estimating the time involved with creating those workpackages. In my experience, unless you are working in a very mature IT department, it will take you some time and repetition working with your developers, network engineers, requirements analysts, etc... before they give you solid workpackages and time estimates. However, also from experience, I know this can be done. With each project, the sme's got better at estimating and identifying workpackages. On top of reviewing the EVM articles here, I would strongly suggest reviewing the WBS articles - what it is, how to create, etc. - Not necessarily for you as you already know about creating a WBS but for reviewing with the team so they understand what you are trying to accomplish and why. Hope this helps a bit. Saving Changes...
