PK0-005 Project Life Cycle Practice Question
A project manager is estimating the cost of a new software development project. She uses the actual cost of a similar past project and adjusts for differences in size and complexity. Which estimation technique is she using?
⚠ Common exam trap
PK0-005 often tests the confusion between analogous and parametric estimation — candidates see 'historical data' and jump to parametric, but parametric requires a measurable unit rate applied to a variable, whereas analogous uses whole-project comparison.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Analogous estimation
Analogous estimation uses historical data from a similar past project as the basis for estimating the current project, adjusting for known differences in size, complexity, or scope. The scenario explicitly describes using actual cost of a similar past project with adjustments, which is the textbook definition of analogous (top-down) estimating. It is fast and inexpensive but less accurate than bottom-up or parametric methods.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Three-point estimation
Why it's wrong here
Three-point estimation uses optimistic, pessimistic, and most likely cost values to calculate a weighted average, but the scenario describes a single historical baseline adjusted for size and complexity—this is analogous (parametric or analogous estimation), not a probabilistic range. It is tempting because three-point estimation is a common technique for refining cost accuracy, and it would be correct if the project manager had gathered three separate estimates from subject-matter experts to account for uncertainty rather than relying on one past project.
- ✗
Parametric estimation
Why it's wrong here
Parametric estimation applies a statistical rate per unit, such as cost per function point, to a project variable. It is tempting because it also uses historical data, but it would be correct when a measurable unit rate exists and can be multiplied by the project's size.
- ✗
Bottom-up estimation
Why it's wrong here
Bottom-up estimation sums individual work-package or task estimates to reach a total. It is tempting because it is highly accurate, but it would be correct when detailed task-level data is available, not when scaling a single analogous project's actual cost.
- ✓
Analogous estimation
Why this is correct
Analogous estimation derives duration or cost from the actual figures of a comparable historical project, then scales them for size and complexity differences. Here the manager uses a similar past project's real cost, adjusted for scope variance, satisfying the stem's requirement for a top-down, experience-based estimate rather than bottom-up or parametric calculation.
Go deeper
Related to this question
About these practice questions
This PK0-005 question is part of Courseiva's 954-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
This PK0-005 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PK0-005 exam.