CMMI v.2 0 Model Excerpt Estimating Practice Area Models
CMMI v.2 0 Model Excerpt Estimating Practice Area Models
V2.0
Model
Excerpt
Estimating
Practice Area
C MM I®
V2.0
An Integrated
Product Suite
MODEL
• Clear pathway to performance improvement
• Simplified for accelerated adoption
APPRAISAL METHOD
• New appraisal method to increase reliability and reduce cost
ADOPTION GUIDANCE
• Guidance for new adopters to get started with CMMI
• Guidance for transition from CMMI V1.3 to CMMI V2.0
What is the
CMMI V2.0 Model?
The Capability Maturity Model Integration (CMMI)® is a proven set
of global best practices that drives business performance through
building and benchmarking key capabilities.
CMMI V2.0 is one model with multiple customized views that apply
to different business environments, enabling organizations to
create a view of the model that meets their specific performance
improvement needs.
CMMI V2.0
Model Excerpt
This Model Excerpt booklet includes the complete content from the
CMMI model’s Estimating (EST) Practice Area (PA).
Continuity
Optimize schedules to
reduce time-to-market
Planning
This Model Excerpt booklet contains content from model version 2.1, including the Development, Services, and
Supplier Management views. Refer to the release notes, available from the Model Viewer, for more details.
Table of Contents
ESTIMATING...............................6
Required PA Information
Intent
Estimate the size, effort, duration, and cost of the work and resources
needed to develop, acquire, or deliver the solution.
Value
Estimation provides a basis for making commitments, planning, and
reducing uncertainty, which allows for early corrective actions and
increases the likelihood of meeting objectives.
Additional Required PA Information
This section left blank for future content.
Explanatory PA Information
Practice Summary
Level 1
EST 1.1 Develop high-level estimates to perform the work.
Level 2
EST 2.1 Develop, keep updated, and use the scope of what is
being estimated.
EST 2.2 Develop and keep updated estimates for the size of
the solution.
EST 2.3 Based on size estimates, develop and record effort,
duration, and cost estimates and their rationale for the
solution.
Level 3
EST 3.1 Develop and keep updated a recorded estimation
method.
EST 3.2 Use the organizational measurement repository and
process assets for estimating work.
• P
roviding an initial commitment with an understanding that the
initial commitment may be changed if the scope changes
• D
efining milestones to refine an initial commitment range to
produce a final commitment after more investigation
• C
ommitting to the known parts of the project, and committing
to the remainder of the work after further investigation and
definition
Estimate and track several aspects of the work to realize value. For
example, based on Table EST-1, how complete is the work?
Size 10%
Effort 60%
Duration 50%
Cost 75%
Context Specific
Agile
with Scrum Guidance
Release Planning
Estimating
Backlog Grooming
Sprint Planning
Sprint Execution
Sprint Review/Demo
Retrospective
Requirement 1 40
Requirement 2 30
User Story 1 20
Practice(s) 1.1
Requirement 1 40
Requirement 2 20
EST 1.1
A high-level estimate addresses work size, cost, and schedule
uncertainties to avoid pursuing work that may result in schedule or
budget overruns.
Additional Required Information
This section left blank for future content.
Example Activities
Example Activities Further Explanation
EST 2.1
estimated.
Value
Ensures the entire solution is addressed which increases the
likelihood of meeting objectives and avoiding rework.
Additional Required Information
This section left blank for future content.
Explanatory Practice Information
Additional Explanatory Information
The scope:
• Includes the work effort
• D
efines the solution to be developed, delivered, or
acquired
• R
esults in the information needed to estimate the size,
effort, cost, and duration
• A
ddresses any resources that must be acquired or will be
consumed during the project
• E
stablishes the work constraints, e.g., what is included
and what is not included
EST 2.1
Example Work Products Further Explanation
List of tasks and activities To more accurately estimate costs,
or Work Breakdown include identified resources for tasks
Structure (WBS) and durations.
List of needed resources Includes not just staff, but also other
resources needed to accomplish
the work, e.g., facilities, acquired
solutions, tools.
Context Specific
Supplier Management
EST 2.2
Additional Required Information
This section left blank for future content.
Explanatory Practice Information
Additional Explanatory Information
Size is the primary input to many estimation models. Estimation is not
a one-time activity that is only performed before or at the start of the
project. It is a recurring activity where the estimate is adjusted as new
information becomes available throughout the lifecycle of a solution,
operations and maintenance, or for services produced and delivered.
Estimating size provides a consistent basis for estimating effort,
duration, and cost. A relative level of difficulty or complexity may be
associated with size estimates and is used in the transformation to
effort, duration, cost, and quality. For example:
• F
or services, size could be the type or number of service requests,
number of calls received in an hour, or the number of customers
desiring a service delivery, etc.
• F
or software development, size could be the number of objects,
the number of components, the number of features, standard or
customized function points, the number of requirements, or the
number of lines of code, etc.
• F
or hardware development, size could be the number of connections
or connection points, the number of welds, the number of boards,
the number of components, or the number of hardware and software
integration points, etc.
• F
or supplier management, size could be the number of requirements,
the number of features, the number of items to be acquired, or the
number and types of bidders, etc.
EST 2.2
tasks.
The project estimation methods and
their use may change over time as
the understanding of the relationship
of solution characteristics to size
improves.
Complexity is typically used in the
transformation from size to effort,
duration, and cost. Complexity may
also include qualitative aspects of the
solution, such as new vs. legacy.
EST 2.2
• N
umber of service levels
• V
olume of service requests
Examples of tasks to develop size estimates for include:
• S
ervice system development and delivery
• S
ervice system monitoring
• P
reventative maintenance or repair
• T
raining
• Incident management and resolution
• U
pdating equipment and supplies
• L
ogistical support
• F
acilities maintenance
• T
ransition activities
• M
onitoring for and addressing obsolescence
• S
ystem disposal
Supplier Management
Context Tag: CMMI-SPM
EST 2.2
EST 2.3
estimates, leading to better decision making.
Additional Required Information
This section left blank for future content.
Explanatory Practice Information
Additional Explanatory Information
Transform the size estimate into estimates of effort, duration, and
cost. Use estimation models, historical data, expert judgment, or
a combination of all three. Understanding the size of the solution
provides a more accurate basis for determining the effort, duration,
and cost for the solution. While performing the work, compare the
rationale to actual conditions to identify missing or unnecessary
aspects in the original estimate. Identifying missing or unnecessary
aspects supports re-planning the current work or estimating future
work.
Managers and leads typically perform top down estimation. Bottom up
estimation is typically performed by team members.
Develop and calibrate estimation models using available historical
data. To increase confidence, update estimation models as additional
data becomes available.
Sometimes, historical data is not available, such as when efforts are
unprecedented. Unprecedented efforts are riskier and require more
research to develop a basis of estimate. Record rationale for what
made the work unique to aid understanding of any assumptions made
in the initial planning phases.
EST 2.3
transform size and • Size, cost, effort, and schedule
complexity into effort, (duration) data from previous
duration, and cost completed projects
estimates. • Appropriate scaling data to account
for differing sizes and complexity
• In addition, information on factors
that influenced the performance
and other contextual information will
help determine if past data can be
included, excluded, or adjusted
Historical data can also be used with
analogies, e.g., if a current project is 10%
smaller than a similar historical project,
use the historical project’s results reduced
by 10%. There may be instances where
historical data is not available or does not
apply. In the absence of historical data (for
example, no prior history of work similar to
current work) external sources like industry
data may be used.
EST 2.3
suppliers
• Amount of risk
• How agreeable or difficult
the customer is
• Direct labor rates and overhead
• Penalties for warranty work
• Regulatory requirements or environment
• Level of security required for tasks,
work products, hardware, software,
personnel, and work environment
EST 2.3
• Context for the effort estimate
Duration estimate Typically includes:
• Duration
• Unit of measure (typically hours or days)
• Rationale for the duration estimate
Service estimates should consider the effort and cost associated with
delivering the service. Individual services can have associated workflows
EST 2.3
or detailed steps that involve points of communication, evaluation, and
decision. Consider these lifecycles when estimating the requirements to
support the delivery of individual services.
EST 2.3
service)
Supplier Management
Context: U
se processes to identify, select, and manage
suppliers and their agreements.
Additionally, the acquirer needs to estimate the cost and effort for
the acquired solutions. Estimates should address effort and cost
for supplier management and reporting requirements. The acquirer
should review its supplier effort and cost estimates with external
individuals to ensure reasonable estimates.
EST 3.1
Value
Maximizes consistency and efficiency for developing
accurate estimates and increases the likelihood of
meeting objectives.
Additional Required Information
This section left blank for future content.
EST 3.1
re-estimates. This is repeated until the
estimates converge. The facilitator then
records the final estimate.
EST 3.1
for similar activities, projects, domains,
etc. Involve subject matter experts in
developing and approving the method.
EST 3.2
better decision making, a higher likelihood of meeting objectives, and
reduced risk.
Additional Required Information
This section left blank for future content.
Explanatory Practice Information
Additional Explanatory Information
Using organizational assets as a basis for estimating leverages the
data and experience from previous projects to improve the reliability
of estimates for similar work. Select the most appropriate estimation
method and use it to produce the estimates.
When using organizational assets consider:
• H
istorical and validated data from this work or similar work and
its context
• S
imilarities and differences between the current work and work
from which historical data will be used
• R
ationale used to select the historical data
• Type of work
• Tailoring performed
• G
eographic-specific information
• Domain and technology
EST 3.2
Example Activities
Example Activities Further Explanation
Use estimation
methods.
Contribute results
Include actual results, contextual
and measures to the
information, and identified
organization in order to
improvements.
improve the estimation
methods and update
organizational assets.
EST 3.2
• Templates
• Best practice examples
• Approved methods for use
• Guidelines
Updates to the organizational
measurement repository may
include:
• Historical estimation data,
e.g., actual effort expended,
number of function points
• Rationale for the estimate,
e.g., team skill levels, amount
of code reused
• Contextual information,
e.g., domain, type of work,
customer
• Updated estimation results
Context Specific
Supplier
Management
Context Tag: CMMI-SPM
Context: Use
processes to identify, select, and manage
suppliers and their agreements.
EST 3.2
CMMI Model
The model provides an integrated approach to building, improving, and
sustaining organizational performance, with built-in domain-specific views for
Development, Services, and Supplier Management.
Purchase a CMMI model license at
https://cmmiinstitute.com/model-viewer
CMMI Appraisals
CMMI Appraisals help businesses identify the strengths and weaknesses of
existing organizational performance and processes. The results provide a clear
path to adopt model best practices for improving performance.