 The load factor was how
a project was tracked before project velocity became more popular. The load factor
equals actual calendar days to complete a task divided by the developer's estimated "ideal" days to do
it. That is, think of a task that would take you one day if you could focus completely on it. Now picture yourself
trying to get it done in the real world. The number of days it actually takes is the load factor.
Load factors from 2 to 5
are normal. If you need to guess at a load factor to get started you should consider people's experience and the
technology being used. A 2 is optimistic, a 3 is typical, while a 4 and 5 are for projects using unfamiliar technology.
Ron Jeffries recommends just simply using a 3 as an initial guess for new projects. |
After making an initial
guess you must then measure and track either the load factor, or better yet, the project velocity throughout the
project.
The load factor can not
be used to compare two projects. Each project and team is unique and will have different load factors for different
reasons.
Use a release planning meeting
to re-estimate and re-negotiate the release plan if the load factor changes dramatically. Expect the load factor
to change again when the system is put into production due to maintenance tasks. 
  |
