4squareviews

This post covers the outputs of the process 9.2 Estimate Activity Resources.

9.2.3.1 Resource Requirements

This document identifies the types and quantities of resource required for each work package or activity.    It is distinguished from these two other documents that have the word “resource:

1. Resource breakdown structure (see paragraph 9.2.3.3 below)–this is a preliminary document that is an output of 9.1 Plan Resource Management which just lists the types of resources required for work on the project in general.   The process 9.2 Estimate Activity Resources takes this further in two ways:   it lists not only the types of resources, but also the quantity needed.
2. Resource calendar–This is a calendar that identifies the working days when each specific resource is available.    This can be done at the level of the project in general, or it can be updated as a result of the process 9.2 Estimate Activity Resources to the level of the work package or activity.

So the resource breakdown structure answers the question of “what” when it comes to resources required for the project, the resource requirements adds the answer to the question “how much”, and the resource calendar adds the answer to the question “when”.

9.2.3.2. Basis of Estimates

Just like for the other two estimating processes, 6.4 Estimate Activity Durations and 7.2 Estimate Costs, it is important to keep track of how the estimation came about so that it is clear how the resource estimate was derived.   That can include items like:

• Methods used to develop the estimate (bottom-up estimating, analogous estimating, parametric estimating, etc.)
• Resources used to develop the estimate, particularly information from previous similar projects
• Assumptions associated with the estimate (these will go in the project document called the Assumption Log–see paragraph 9.2.3.4)
• Known constraints (from other knowledge areas, such as schedule, budget, scope, risk, etc.)
• Range of estimates (usually expressed in terms of a plus or minus percentage)
• Confidence level of estimates (for example, a 90% probability of being able to obtain the resources within a given cost estimate)
• Documentation of identified risks influencing the estimate (these will go in the risk register)

9.2.3.3 Resource Breakdown Structure

This is a preliminary document that is an output of 9.1 Plan Resource Management which just lists the types of resources required for work on the project in general.   The process 9.2 Estimate Activity Resources takes this further in two ways:   it lists not only the types of resources, but also the quantity needed.   These two documents will be used to acquire and monitor resources in the upcoming processes, starting with 9.3 Acquire Resources.

9.2.3.4 Project Documents Updates

• Activity attributes–the activity attributes, a description that gives information about each activity, are updated with the resource requirements.
• Assumption log–updated with assumptions regarding the types and quantities of resources required
• Lessons learned register–as with a lot of planning processes, the lessons learned register is updated with techniques that were found to be efficient and effective in developing resource estimates

Filed under: Uncategorized |