Establish Estimates (Feature)

Purpose:

<?>

Objective:

Estimates of project planning parameters are established and maintained.

Description:

Project planning parameters include all information needed by the project to perform necessary planning, organizing, staffing, directing, coordinating, reporting, and budgeting.

The acquirer develops estimates for project work based on the acquisition strategy, including high-level estimates for the work to be done by suppliers. Initial estimates can be revised based on supplier estimates in response to the solicitation package.

Estimates of planning parameters should have a sound basis to instill confidence that plans based on these estimates can support project objectives.

Factors to consider when estimating these parameters include the following:

• • The acquisition strategy
  • Project requirements, including product requirements, requirements imposed by the organization, requirements imposed by the customer, and other requirements that affect the project
  • The scope of the project
  • Identified tasks and work products
  • The technical approach
  • The selected project lifecycle model (e.g., waterfall, incremental, spiral)
  • Attributes of work products and tasks (e.g., size, complexity)
  • The schedule
  • Models or historical data used for converting attributes of work products and tasks into labor hours and costs
  • The methodology (e.g., models, data, algorithms) used to determine needed material, skills, labor hours, and cost.

The acquisition strategy is a key factor when estimating the project. Documentation of the estimating rationale and supporting data is needed for stakeholder review and commitment to the plan and maintenance of the program as the project progresses.

Inputs:

<?>

Outputs:

<?>

Controls:

• Detail Project Schedule
• <?>

Task Instructions:

Establish the Acquisition Strategy (User Story)

1. 1. Using the <?>, [the ?] with support from <?> is responsible for identifying the capabilities and objectives the acquisition is intended to satisfy or provide.
   2. Using the <?>, [the ?] with support from <?> is responsible for identifying the acquisition approach.
   3. Using the <?>, [the ?] with support from documenting the business considerations.
   4. Using the <?>, [the ?] with support from <?> is responsible for identifying significant risks and which risks will be addressed jointly with the supplier.
   5. Using the <?>, [the ?] with support from <?> is responsible for identifying the preferred type of supplier.
   6. Using the <?>, [the ?] with support from <?> is responsible for identifying the product support strategy.
   7. Using the <?>, [the ?] with support from <?> is responsible for reviewing and obtaining agreement with senior management on the acquisition strategy.

Estimate the Scope of the Project (User Story)

1. 1. Using the <?>, [the ?] with support from <?> is responsible for developing a Work Breakdown Structure based on the product architecture.
   2. Using the <?>, [the ?] with support from <?> is responsible for defining the work packages in sufficient detail so that estimates of the project tasks, responsibilities, and schedule can be specified
   3. Using the <?>, [the ?] with support from <?> is responsible for identifying products and product components to be externally acquired.
   4. Using the <?>, [the ?] with support from <?> is responsible for identifying work products to be reused.

Establish Estimates of Work Product and Task Attributes (User Story)

1. 1. Using the <?>, [the ?] with support from <?> is responsible for determine the technical approach for the project
   2. Using the <?>, [the ?] with support from <?> is responsible for using appropriate methods to determine the attributes of the work products and tasks to be used to estimate resource requirements.
   3. Using the <?>, [the ?] with support from <?> is responsible for estimating the attributes or work products and tasks.

Define Project Lifecycle Phases (User Story)

1. 1. Using the <?>, [the ?] with support from <?> is responsible for defining the project lifecycle for the project.

Estimate Effort and Cost (User Story)

1. 1. Using the <?>, [the ?] with support from <?> is responsible for collecting models or historical data to be used to transform the attributes of work products and tasks into estimates of labor hours and costs.
   2. Using the <?>, [the ?] with support from <?> is responsible for including supporting infrastructure needs when estimating effort and cost.
   3. Using the <?>, [the ?] with support from <?> is responsible for estimating effort and cost using models, historical data, or a combination of both.