Establish Estimates (Epic)

Purpose:

Establish and maintain accurate estimates for project planning parameters to ensure precise and up-to-date project timelines, resource allocation, and budget management. This will help enhance project predictability and successful delivery.

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
• Guidelines for Selection of Project Lifecycle Models

Task, User Stories, Acceptance Criteria, and Task Instructions:

Establish the Acquisition Strategy

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

As a project manager, I want to develop a Work Breakdown Structure (WBS) So that all project tasks are clearly defined, organized, and manageable, ensuring efficient project execution and monitoring.

Acceptance Criteria:
Given a new project initiation, When defining the project scope and objectives Then, create the top-level components of the WBS, including major deliverables.

Task Instructions:

1. 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

As a project manager, I want to establish and maintain estimates of work product and task attributes So that I can ensure effective project planning, resource allocation, and monitoring for successful project execution.

Acceptance Criteria:
Given the project scope and requirements When defining work products and tasks, Then create initial estimates for effort, duration, and resources required for each work product and task.

Task Instruction:

1. 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

As a project manager, I want to define the project lifecycle phases So that I can effectively scope the planning effort and ensure successful project completion.

Acceptance Criteria:

• • • Given a project initiation, When defining the project lifecycle phases Then the initiation phase should include project goals, objectives, stakeholders, and high-level scope.

• • • Given a need to scope the planning effort, When defining the project lifecycle phases Then the planning phase should detail the project plan, including timelines, resources, risk management, and communication plan.

• • • Given the start of project execution, When defining the project lifecycle phases Then, the executing phase should encompass task execution, team management, and quality assurance activities.

• • • Given ongoing project activities When defining the project lifecycle phases Then, the monitoring and controlling phase should include tracking project performance, managing changes, and ensuring the project stays on track.

• • • Given project completion, When defining the project lifecycle phases Then the closing phase should cover project finalization, stakeholder approval, and documentation of lessons learned.

Task Instructions:

1. 1. 1. Using the Guidelines for the Selection of Project Lifecycle Models, [the Project Manager], with support from the PMO, is responsible for defining the project’s lifecycle.

Estimate Effort and Cost

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.