Is it a good idea to use PERT analysis when planning a software project?

Question

A friend recently suggested I use PERT analysis when estimating the time it will take me to complete projects. Put simply, PERT analysis is a technique that depends on your optimistic estimate, your pessimistic time estimate, and your normal time estimate. You then use a formula to calculate the expected time estimate.
Here's an example:

Activity: Develop module B	
Predecessor: Learn to use the necessary APIs
Optimistic time estimate (O):3 hours
Normal time estimate (M):5 hours
Pessimistic time estimate (P):9 hours
Expected time: (O +4M + P) ÷6 = (3 +5*4 +9) /6 =5.333 hours

You do that for each task in the project, and then draw a gantt chart with the expected durations. It's supposedly accurate for giving an estimate for large projects. I was wondering, have any of you used it while planning software projects and  would you recommend it?

Tamim Salem · Answer

Yes, I use this method frequently in my task estimates, and I found that it provides more trust worthy estimates.
Of course, you're initial input to this formula should be as accurate and realistic as possible for the overall cost to be reasonable.
Its also worth mentioning that the factors (4*M) in the formula might change depending on your industry and historical data.
I found Steve McConnel's Book "Software Estimation: Demystifying the Black Art" a good reference on this topic.

Asher Ahsan · Answer

Don't have much idea on this application

abdenacer garidi · Answer

yes it is  a good idea to use PERT analysis when planning a software project of course

Senad Naser · Answer

i think it is the most realistic, it focuses on the |Most likely, and consider O and P

Products By Bayt.com

Use Our Mobile App

Start networking and exchanging professional insights

Is it a good idea to use PERT analysis when planning a software project?

Popular Searches

More Questions Like This