Stalin Jesudoss

 Profile Answers by Stalin Jesudoss 

• Oct 22nd, 2008

 

Effort Variance (%) Project effort estimates will be done in terms of
man-hours. The Effort Variance would be calculated as below 

Effort Variance = (Actual Effort – Planned Effort) / (Planned Effort) * 100

srinivasulub1981

 Profile Answers by srinivasulub1981 Questions by srinivasulub1981

• Nov 29th, 2008

 

It's just calculating the extra time spend on testing, in our project my client asked the estimates for all types of requirements, then we started our testing , if QA time is exceeded then we should give a explanation as why it takes the extra time, if it's a valid reason there will be no problem other wise problem for entire QA team.

Srinivas

G.D.S.Prasad

 Profile Answers by G.D.S.Prasad Questions by G.D.S.Prasad

• Mar 12th, 2009

 

Effort Variance = (Actual Efforts - Planned Effort)/Planned Efforts
In general the Effort Variance Should be in between +/- 5%

mathan_vel

 Profile Answers by mathan_vel Questions by mathan_vel

• Aug 12th, 2009

 

This metric gives the variation of actual effort vs. the estimated effort. This is calculated for each project Stage wise

Formula

EV = [(Actual person hours – Estimated person hours) / Estimated person hours] * 100

Calculated at

Stage completion as identified in SPP

Calculated from

Estimation sheets for estimated values in person hours, for each activity within a given stage and Actual Worked Hours values in person hours.

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 16th, 2009

 

Effort variance (EV) calculates variance of actual effort versus planned effort.  The formula for effort variance is:

Effort variance = [(Actual effort - Planned Effort)/Planned effort] * 100

The effort variance may be greater than expected.  For example, we estimated 100 hours but actual work took 110 hours.  In this case, there would be a +10% effort variance.  Some of the causes why this positive variance might have occurred are:

- Estimation parameters were wrong.

- Test scope was not understood in totality.

- Underestimated the test group's inefficient process.

- The estimate was changed without changing scope just to make the numbers match the preferred schedule.

- Added functionalities that were not in the customer requirements.

The effort variance may be less than expected.  For example, we estimated that the test project will take 100 hours to complete but it actually took 90 hours.  This results in a -10% effort variance.  Some of the causes why this negative variance might have occurred are:

- Estimation parameters were wrong.

- There was an improvement in the process

- Team performed much better than expected

- Testing was not finished and one or more of the requirements was missed.