Estimation Techniques

Why Estimation Techniques Are Important

Estimation techniques are critical in business analysis because they form the foundation of project planning, resource allocation, and stakeholder management. Accurate estimations allow organizations to:

• Set realistic timelines and budgets for projects
• Allocate resources effectively
• Manage stakeholder expectations
• Identify risks and potential project challenges early
• Track progress and performance against baselines
• Make informed business decisions

For the CBAP exam, understanding estimation techniques demonstrates your ability to support project success and deliver business value.

What Are Estimation Techniques?

Estimation techniques are structured methods used to forecast the effort, cost, duration, and complexity of project work based on available information. They help business analysts predict how many resources, how much time, and what level of effort will be required to complete specific activities or deliverables.

Key Definition: Estimation is the process of determining the probable quantitative result of an activity, based on information available at a particular time, using historical data, expert judgment, and analytical techniques.

Estimations can apply to:

• Time and schedule estimates
• Cost and budget estimates
• Effort and resource estimates
• Quality and risk estimates
• Scope and complexity estimates

How Estimation Techniques Work

1. Analogous Estimation (Top-Down)

How it works: This technique uses historical data from similar past projects to estimate current project parameters. The estimator looks at comparable projects and adjusts for differences in scope, complexity, and other factors.

When to use: Early in project planning when detailed information is limited

Advantages: Quick, cost-effective, uses real historical data

Disadvantages: Less accurate, requires relevant historical projects, may overlook unique aspects of current project

Example: If a previous website redesign took 6 months with a team of 5, a similar redesign might be estimated at 5-7 months depending on scope differences.

2. Parametric Estimation

How it works: This technique establishes a statistical relationship between historical data and other variables. It uses mathematical models and formulas based on measurable project characteristics (parameters).

When to use: When you have a large amount of historical data and clear relationships between project parameters

Advantages: Objective, scalable, improves with more data, provides basis for benchmarking

Disadvantages: Requires quality historical data, may be costly to set up, assumes past patterns continue

Example: If development historically costs $100 per line of code, and a new module requires 5,000 lines, the estimate is $500,000.

3. Three-Point Estimation (PERT)

How it works: This technique uses three estimates for each activity: optimistic (best case), pessimistic (worst case), and most likely. A weighted average is calculated using the formula:

Expected Estimate = (Optimistic + 4×Most Likely + Pessimistic) ÷ 6

When to use: When there is significant uncertainty and risk in estimating

Advantages: Accounts for uncertainty, provides range of estimates, encourages critical thinking about risks

Disadvantages: More time-consuming, requires three estimates per activity, weighting may vary by organization

Example: A task estimated at: optimistic 2 weeks, most likely 4 weeks, pessimistic 8 weeks = (2 + 4×4 + 8) ÷ 6 = 4.33 weeks

4. Bottom-Up Estimation

How it works: Detailed estimates are created for individual work items, components, or tasks, then rolled up or aggregated to create estimates for larger deliverables and the overall project.

When to use: When detailed scope is known, later in planning when tasks are well-defined

Advantages: High accuracy, builds team buy-in, identifies specific work items, supports detailed planning

Disadvantages: Time-consuming, requires detailed scope definition, may miss integration or system-level efforts

Example: Estimating each screen in a software application (2 days), each database table (3 days), integration testing (5 days), then summing for total effort.

5. Expert Judgment

How it works: Individuals with significant experience and expertise provide estimates based on their knowledge, experience, and understanding of similar work.

When to use: Always, as a supplement to other techniques; essential when historical data is unavailable

Advantages: Incorporates tacit knowledge, flexible, quick, considers organizational context

Disadvantages: Subjective, may be biased, varies by expert, lacks documented rationale

Example: A senior architect estimating that a complex integration will take 3 months based on similar past work and current team capabilities.

6. Planning Poker (Fibonacci)

How it works: Team members independently estimate work using a set of cards (often with Fibonacci numbers: 1, 2, 3, 5, 8, 13, etc.). Estimates are revealed simultaneously, discussed if there's disagreement, and the process repeats until consensus is reached.

When to use: Agile environments, sprint planning, relative sizing of user stories

Advantages: Encourages team participation, surfaces assumptions and risks, quick, prevents anchoring bias

Disadvantages: Requires team availability, works better for relative estimation than absolute time, Fibonacci numbers can be confusing initially

Example: Team members estimate a user story as 5, 8, 8, and 13 story points. Discussion reveals missing requirements; they re-estimate at 8.

Estimation Process Steps

Step 1: Gather Information - Collect requirements, scope, constraints, and historical data relevant to the estimate

Step 2: Select Appropriate Technique(s) - Choose estimation method(s) based on project phase, available data, and organizational standards

Step 3: Document Assumptions - Clearly state all assumptions underlying the estimate (resource availability, technology, team skills, etc.)

Step 4: Perform the Estimation - Apply the chosen technique(s) to generate estimates

Step 5: Validate the Estimate - Review estimates with stakeholders and subject matter experts for reasonableness

Step 6: Document and Communicate - Record estimates, basis, assumptions, confidence level, and constraints; communicate to stakeholders

Step 7: Monitor and Refine - Track actual performance against estimates and refine estimation approaches for future projects

How to Answer Questions Regarding Estimation Techniques on the CBAP Exam

Question Type 1: Identifying the Appropriate Technique

Approach:

• Look for keywords indicating project phase: "early planning" suggests analogous; "detailed scope known" suggests bottom-up
• Identify available resources: "historical data available" suggests parametric; "no similar projects" suggests expert judgment
• Consider uncertainty level: "high uncertainty" suggests three-point estimation
• Check for team collaboration: "team input needed" suggests planning poker

Example Question: "Your organization is in the early phases of planning a new product development project. You have limited detailed requirements and no similar past projects. Which estimation approach would be most appropriate?"

Answer Strategy: Look for the combination of "early phase" and "no similar projects." This points to expert judgment or analogous estimation. Analogous would require similar historical projects, so expert judgment is the best choice. Watch for analogous as a distractor.

Question Type 2: Understanding Estimation Formulas

Approach:

• Recognize the PERT/three-point formula: (O + 4M + P) ÷ 6
• Remember that "most likely" is weighted 4 times
• Be able to calculate expected value given three estimates
• Understand the concept of standard deviation: (P - O) ÷ 6

Example Question: "A task has an optimistic estimate of 5 days, a most likely estimate of 10 days, and a pessimistic estimate of 20 days. Using three-point estimation, what is the expected duration?"

Answer Strategy: Apply the formula: (5 + 4×10 + 20) ÷ 6 = (5 + 40 + 20) ÷ 6 = 65 ÷ 6 = 10.83 days

Question Type 3: Analyzing Estimation Accuracy and Confidence

Approach:

• Understand that bottom-up estimates are generally more accurate than analogous estimates
• Recognize that parametric estimates improve with more historical data
• Know that three-point estimation accounts for risk and uncertainty
• Understand confidence levels based on available information

Example Question: "Which estimation technique would provide the highest confidence in accuracy when detailed requirements have been defined and decomposed?"

Answer Strategy: "Detailed requirements have been defined and decomposed" indicates bottom-up estimation is appropriate. Bottom-up provides the highest accuracy when detailed scope is known. Select bottom-up estimation.

Question Type 4: Identifying Assumptions and Constraints

Approach:

• Recognize that all estimates are based on assumptions
• Look for factors that could impact accuracy (resource skills, technology, availability)
• Identify what must be true for the estimate to be valid
• Consider what could change or go wrong

Example Question: "An analyst estimates a project at 6 months using analogous estimation from a similar past project. Which assumption is implied in this estimate?"

Answer Strategy: When using analogous estimation, implicit assumptions include: the past project is truly similar, team skills are comparable, technology and tools are similar, organizational context hasn't changed significantly. Look for answer options that reflect these assumptions.

Question Type 5: Estimation in Different Contexts

Approach:

• Understand how estimation applies to different project domains (IT, construction, marketing, etc.)
• Recognize that Agile projects often use relative estimation (story points) rather than time
• Know that estimates may be expressed in different units (hours, days, effort, cost, complexity)
• Distinguish between estimation for requirements analysis vs. implementation

Example Question: "An Agile development team uses Planning Poker to estimate user stories. What is the primary advantage of this approach over asking a single expert to provide time estimates in hours?"

Answer Strategy: Planning Poker advantages include: team collaboration, relative sizing (story points vs. absolute time), identifying assumptions and risks through discussion, preventing individual bias, building team understanding. Look for answers emphasizing collaboration and risk discussion.

Exam Tips: Answering Questions on Estimation Techniques

Tip 1: Memorize the PERT Formula and Variations

Know the three-point formula cold: (Optimistic + 4×Most Likely + Pessimistic) ÷ 6

Also know the standard deviation formula: (Pessimistic - Optimistic) ÷ 6

Be able to identify when to use which. Practice calculating scenarios before the exam so you can do it quickly under time pressure.

Tip 2: Understand When Each Technique Is Appropriate

Create a mental matrix:

• Early phase, limited data: Analogous or Expert Judgment
• Lots of historical data: Parametric
• High uncertainty: Three-Point
• Detailed scope defined: Bottom-Up
• Team-based, Agile: Planning Poker

When you see a scenario, quickly match it to this matrix.

Tip 3: Watch for Keywords That Signal the Answer

Analogous signals: "similar past projects," "historical data," "early planning phase," "quick estimate"

Parametric signals: "statistical relationship," "large database," "benchmarking," "formula," "per unit cost"

Three-Point signals: "uncertainty," "best case/worst case," "risk account," "pessimistic/optimistic"

Bottom-Up signals: "detailed requirements," "decomposed," "component level," "high accuracy needed"

Planning Poker signals: "Agile," "team consensus," "story points," "relative sizing," "discussion"

Expert Judgment signals: "no historical data," "unique project," "subject matter expert," "experience-based"

Tip 4: Understand Accuracy vs. Precision vs. Confidence

The exam may distinguish between:

• Accuracy: How close the estimate is to actual reality. Bottom-up is typically more accurate than analogous.
• Precision: The level of detail in the estimate. "5.33 days" is more precise than "about a week."
• Confidence: How certain you are about the estimate. More detailed information increases confidence.

Higher accuracy doesn't always mean higher precision or confidence.

Tip 5: Recognize Estimation vs. Planning

Estimation provides the basis for planning, but they are not the same. Estimation forecasts effort/duration/cost. Planning determines how work will be sequenced, resourced, and managed. Don't confuse estimation techniques with project planning or scheduling techniques.

Tip 6: Pay Attention to Organizational Context

The "best" estimation technique depends on organizational maturity, available historical data, project type, and culture. A question might ask which technique is most appropriate "for an organization that..."

• Mature organizations with good metrics: Parametric or sophisticated bottom-up
• Agile organizations: Planning Poker, relative estimation
• Organizations with diverse projects: Expert judgment, three-point estimation
• Project-based organizations: Analogous, parametric

Tip 7: Remember That Estimation Is Ongoing

Estimates are refined as more information becomes available. Early "order of magnitude" estimates may be ±50%. Later estimates (during detailed planning) should be ±10%. This concept of progressive elaboration may be tested.

Tip 8: Understand the Role of Assumptions

Every estimate rests on assumptions. Good answers will reference documentation of assumptions. Poor estimates often fail because underlying assumptions changed or were not identified. If a question asks about estimation failure, check whether assumptions were documented and monitored.

Tip 9: Be Familiar with Common Estimation Biases

Recognize these biases that can skew estimates:

• Anchoring: Being influenced by the first number mentioned. Planning Poker avoids this through simultaneous estimates.
• Optimism bias: Underestimating effort because "this time will be different." Three-point estimation and pessimistic scenario planning address this.
• Recency bias: Relying too heavily on recent projects, ignoring longer-term trends.
• Status quo bias: Assuming current conditions will continue when they likely won't.

The exam may ask which technique helps mitigate specific biases.

Tip 10: Apply Critical Thinking

Estimation questions often test your reasoning, not just memorization. When answering:

• Consider why a technique would or wouldn't work
• Think about what information would be needed for accuracy
• Evaluate trade-offs between different approaches
• Consider project constraints that affect estimation choices

If torn between two answers, choose the one that demonstrates deeper understanding of the technique and its application.

Tip 11: Distinguish Between Estimation and Contingency

The estimate itself is the "most likely" or expected value. Contingency reserves are added to account for identified risks. Don't confuse a pessimistic estimate in three-point estimation with a contingency reserve. The pessimistic value is one data point in the formula, not the final plan.

Tip 12: Practice with Real Scenarios

Before the exam, practice answering questions about:

• Estimating a project you've worked on
• Choosing a technique for a described project
• Calculating three-point estimates
• Identifying assumptions in estimates
• Explaining why an estimate failed

Working through scenarios will help you apply concepts quickly on exam day.

Summary

Estimation techniques are fundamental to business analysis and project success. The CBAP exam tests your understanding of when to use each technique, how they work, their advantages and limitations, and how to apply them in various contexts. By mastering the six major estimation techniques—analogous, parametric, three-point, bottom-up, expert judgment, and planning poker—and understanding the factors that influence their selection and accuracy, you'll be well-prepared to answer estimation questions with confidence. Remember that estimation is both a science (formulas, data, methods) and an art (judgment, assumptions, communication), and successful business analysts blend both elements.