-
Purpose
- A project team generates estimates and a work breakdown structure
-
Summary
- A repeatable process for estimation. Using it, a project team can generate
a consensus on estimates for the completion of the project
-
Work Products
-
Input
- Vision and scope document, or other documentation that
defines the scope of the work product being estimated
-
Output
- Work Breakdown Structure
- Effort estimates for each of the tasks in the WBS
-
Entry criteria
- The vision and scope document has been agreed to
by the stakeholders, users, managers and engineering team
- The kickoff meeting and estimation session have been scheduled,
with at least two hours allowed for each
- The project manager and the moderator agree on the goal of the
estimation session by identifying the scope of the work to be estimated
-
Basic Courses of Events
-
Choose the team
- The project manager selects the estimation team and a moderator
- Should consist of 3 to 7 team members
- Should include representatives from every engineering group that will be involved
-
Kickoff meeting
-
The moderator prepares the team and leads a discussion to
- brainstorm assumptions
- generate a WBS
- decide on the units of estimation
-
Individual preparation
- generates the initial estimates for each task in the WBS
- documenting any changes to the WBS and missing assumptions
-
Estimation session
- The moderator leads the team through a series of iterative steps to gain consensus on the estimates
- At the start of the iteration, the moderator charts the estimates on the
whiteboard so the estimators can see the range of estimates
- The team resolves issues and revises estimates without revealing specific numbers
-
The cycle repeats until
- no estimator wants to change his or her estimate
- the estimators agree that the range is acceptable
- two hours have elapsed
- or
-
Assemble tasks
-
The project manager works with the team to
- collect the estimates from the team members at the end of the meeting
- and compiles the final task list, estimates and assumptions
-
Review results
- The project manager reviews the final task list with the estimation team
-
Alternate paths
- During step 1, if the team determines that there is not enough information known
about the project to perform an estimate, the script ends.
Before the script can be started again, the project manager must document
the missing information by creating or modifying the vision and scope document
- During either step 1 or 3, if the team determines that there are outstanding issues
that must be resolved before the estimate can be made,
they agree upon a plan to resolve the issues and the script ends