Estimation Report

Definition

An estimation report is the metrics work product that reports estimates relating to future projects or phases.

Objectives

The typical objectives of an estimation report are to formally document estimations of the:

• Size of a future project or phase (e.g., in terms of use cases, components, or lines of code).
• Effort required to complete the project or phase (e.g., in terms of staff time by team size and composition).
• Schedule required to complete the project or phase (e.g., in terms of calendar time).
• Cost of a future project or phase (e.g., in terms of staffing, facilities, and equipment costs).

Benefits

The typical benefits of an estimation report include:

• Providing input to endeavor budgets and master schedules.
• Providing a foundation on which to perform staffing including creating the endeavor organization chart.

Contents

An estimation report typically has the following contents:

• Size Estimates
• Effort Estimates
• Schedule Estimates
• Cost Estimates
• Appendices:
  • Major Issues
  • TBDs
  • Assumptions

Stakeholders

An estimation report typically has the following stakeholders:

• Producer:
  • Metrics Team
  • Technical Leader
• Evaluators:
  • Program Manager or Project Manager
  • Technical Leader
• Approvers:
  • Program Manager or Project Manager
  • Technical Leader
  • Customer Representative
• Maintainers:
  • Metrics Team
• Users:
  • Program Management Team or Project Management Team
  • Customer Organization

Phases

An estimation report is typically produced and maintained during the following phases:

• Business Strategy: Completed
• Business Optimization: Completed
• Initiation: Completed
• Construction: Completed
• Delivery: Completed
• Usage: Maintained
• Retirement: Archived

Preconditions

An estimation report can typically be started if the following preconditions hold:

• The project has started.
• The metrics team is properly staffed and trained in estimating the size, schedule, and cost of endeavors.

Inputs

An estimation report typically has the following inputs:

• Work products:
  • Application Vision Statement
  • System Requirements Specification
  • System Architecture Document
  • Project Environments Description Document
• Stakeholders:
  • Program Management Team or Project Management Team
  • Requirements Team
  • Architecture Team
  • Environments Team

Guidelines

• Project estimations should be based on solid metrics rather than marketing's or management's wishful thinking.
• Use the procedure in the associated work flow to produce this work product.
• If you tailor this work product, then tailor its associated standard, template, and inspection checklist.

Conventions

Estimation reports are typically constrained by the following conventions:

• Work Flow
• Content and Format Standard
• MS Word Template
• XML Template
• Inspection Checklist

Examples

• Example Estimation Report