# Estimates: Precision vs. Accuracy

Jim, a new project manager, struggled to define the projects parameters: schedule estimate, people estimate, requirements outline, and necessary capital equipment. Jim proudly walked into his managers office, and proceeded to walk through his project plan discussing these numbers:

64.1 calendar weeks

12.125 people

ROI (return on investment) of 7.5 months

Jims manager, Dave, stopped him, smiling, and said, So, Jim, wheres this .125 person coming from? And whats .1 of a week? Jim was a little stumped, and said, Oh, I guess well borrow someone else. I thought youd want to see a project plan with the fewest number of people. One-tenth of a week is part of a day. Jims manager said, Well, we only have whole people, so I need a plan with either 12 or 13 or whatever you think the right number of people is for this project. And, while youre at it, although I would love to plan a release for a Monday at 9:37am, we both know thats not going to happen. Please work up an estimate thats more accurate, but not as precise. And, while youre at it, show me our optionshow many people for how many weeks, giving me ideas for how we would staff a shorter project with more people and a longer project with fewer people.

Precision is the exactness of the measurement, the number of decimal places. Accuracy is how close you are to the estimate. When I worked with robots, precision meant how close to a specific place in space we could move the robot arm once. Accuracy meant how many times we could make the robot arm move to that precise place. Jims estimate was certainly precise, but estimates are more useful when they are accurate, close to the mark. Projects are composed of numerous predicted estimates, so we cant expect accurate estimates, except to an order of magnitude. Over time, you can learn how to estimate so that your estimates (predictions) are close to your actual schedule.

When you talk about estimates, youre in much better shape if you choose accuracy (how close you are to the prediction) over precision (exactness). As you move closer to accomplishing milestones, you can re-estimate with greater precision.

One way to discuss a schedule estimate is to deal with a range. Jim could have said, Ill need 13 people for about 64 weeks. Or, I can do this project with more difficulty if I have 20 people for about 50 weeks. Or, if we take out this specific performance requirement, well need 18 people for about 48 weeks.

Each of the abouts in the previous sentence exists for accuracy. Schedule estimates are just that, an estimate. In my experience, putting an about in front of a schedule estimate is more helpful than a range (62-65 weeks). Ive met too many senior managers who dont hear the second number, just the first. When I use an about, I can choose a number that makes sense to me to use to senior management.

However, some of you work for managers who prefer a range of estimates, with a confidence for each point in the range. This is particularly helpful if you use a graph to explain your confidence. (see Figure 1.)

Figure 1: Estimates: Precision vs. Accuracy

The graph is a vehicle for starting the discussion about why you have how much confidence when. You can explain why you only have 50% confidence that you will meet the 3/1 requested release date, and you can explain why your confidence improves over time. With this graph, youll especially want to explain the difference in confidence between 6/1 and 7/1. The project manager who generated this graph was concerned about the amount of rework (problem finding and fixing) at the end of the project, and wasnt absolutely sure the project team could finish the rework for 6/1. When he explained how the last three releases had used more than the planned four weeks, his management understood why his confidence level was less than 100% for the 6/1 date.