Estimating cannot guarantee accuracy but when applied provides a view about the overall cost as time required to complete the plan.
Estimates will inevitably change as more is discovered about the project.
Estimating follows identification of the activities in sub-process PL3 and precedes scheduling in sub-process PL5.
This is an iterative sub-process.
The objective is to identify the resources and time required to complete each activity.
This will include not only people but also all other resources that will be required.
Since the type of estimating will vary according to the type of project and level of plan, the guidance is of a general nature.
A Project Plan will normally require top-down estimating (that is, an estimate for the total project, broken down across the normal stages for a project of this type), whereas a Stage Plan or Team Plan would use bottom-up methods (an estimate for each product, built up into a figure for the whole plan).
The two major steps in a typical estimating process are:
Specific skills may be required depending on the type and complexity of the project.
Requirements may include non-human resources, such as equipment, travel or money
It is important to agree a definition of resource types.
For staff this should include:
At this point the estimates will be approximate and therefore provisional.
The reliability of estimates depends on:
From this information we can estimate the elapsed time (duration) for each activity for use in Scheduling (PL5) (See the example list of activities for the organisation of a conference and their duration, in file ‘conference tabular list.doc’ in the product package).
The assumptions that underpin the estimate, the margin of error and the degree of confidence in the estimate should be recorded in the plan.
This information will enable the Project Board to set appropriate tolerances. Tolerances are full described in the section on Controls.
If current understanding is insufficient, the earlier planning sub-processes may have to be reworked.
The Project Manager is responsible for estimation on Project and Stage Plans.
Team Manager will be responsible for Team Plan estimates.
It is a difficult job and, wherever possible, extra help should be sought.
It requires previous experience in the subject matter of the plan as well as training in the job of estimation.
This is where expertise from Project Support can help greatly.
|All planning information so far||Input||Products and activities that require estimation.|
|Activity estimates (effort and duration)||Output||Estimated activities are passed to Scheduling (PL5).|
These are given in tabular form in the file ‘PL4 estimating.doc’ in the product package.
There may be a computerised estimating tool, written text, tables, graphs or formulae available for the type of work identified in the plan.
These tools are normally based on information of actual time taken by identical or similar activities to the ones required in the plan.
The figures can generally be tailored to some extent to reflect more closely the environment for which the plan in question applies.
Where possible, estimating should include discussion with the people who will be responsible for doing the work.
In a large project or difficult areas of work, it is prudent to estimate at least twice, either by using two distinct approaches or by allowing two different sets of people to estimate independently.
When resources have been estimated, it may become clear that resource constraints cannot be met.
If this should happen, the matter should be referred to the Project Board.
More uncertainty should be expected in Project Plan than in a Stage Plan.
A Stage Plan is for a shorter time frame, in the near future and planned in much greater detail.
Refer to the Lessons Learned Reports fro earlier similar projects.
Understanding past estimation successes and failures by reading the Lessons Learned Reports of other projects can assist with estimating.
Any assumptions made during the estimation process should be documented under the heading of ‘Assumptions’ in the plan text.
If the assumption refers to a risk, should be documented in the Risk Log.