Master the IT-English vocabulary of three-point estimation: optimistic, pessimistic, most likely, PERT and weighted averages.
0 / 23 completed
1 / 23
Three-point estimation uses three values. What are they?
Three-point estimation combines optimistic (best case), most likely, and pessimistic (worst case) figures.
2 / 23
What does the 'optimistic' estimate represent?
The optimistic estimate is the shortest plausible duration assuming no problems arise.
3 / 23
The 'pessimistic' estimate accounts for what?
The pessimistic estimate captures the time if significant problems occur.
4 / 23
PERT weights the most likely value more heavily. The common formula is?
The PERT expected value is (Optimistic + 4×Most likely + Pessimistic) / 6, weighting the most likely case.
5 / 23
Which sentence correctly uses 'weighted average' here?
The technique blends the three points into a weighted average that better reflects risk than a single guess.
6 / 23
Sarah: "Hey team, I'm estimating 5 days to complete the user authentication feature. It's pretty straightforward – just standard OAuth integration."
Sarah's estimate of 5 days is likely too low because it doesn't account for risks. A three-point estimation would involve assigning an optimistic, most likely (or 'realistic'), and pessimistic value to the task. The 'conservative' approach, considering rate limiting and edge cases, is the most appropriate response in this scenario – acknowledging potential problems is crucial when using a robust estimation technique.
7 / 23
PR Description
During a code review of a new API endpoint, Alex writes in the PR description: 'I'm estimating this will take 3 days. Optimistic is 1 day, pessimistic is 7 days, and most likely is 3.' His team lead, Ben, asks for feedback on his estimation. Which response best reflects understanding of three-point estimation principles?
PR Description
Three-point estimation uses optimistic, pessimistic, and most likely estimates to account for uncertainty. The 'optimistic' value represents the best-case scenario, assuming everything goes perfectly smoothly – a situation unlikely to persist. The 'pessimistic' estimate reflects the worst-case scenario, accounting for potential roadblocks or unforeseen complexities, while the 'most likely' value provides a central projection based on experience and judgment. Ben is correct in acknowledging this approach as it demonstrates an awareness of potential risks.
8 / 23
Sarah: "Hey team, I'm estimating 5 days to complete the user authentication feature. It's pretty straightforward – just standard OAuth integration."
Sarah's estimate of 5 days is likely too low because it doesn't account for risks. A three-point estimation would involve assigning an optimistic, most likely (or 'realistic'), and pessimistic value to the task. The 'conservative' approach, considering rate limiting and edge cases, is the most appropriate response in this scenario – acknowledging potential problems is crucial when using a robust estimation technique.
9 / 23
PR Description
During a code review of a new API endpoint, Alex writes in the PR description: 'I'm estimating this will take 3 days. Optimistic is 1 day, pessimistic is 7 days, and most likely is 3.' His team lead, Ben, asks for feedback on his estimation. Which response best reflects understanding of three-point estimation principles?
PR Description
Three-point estimation uses optimistic, pessimistic, and most likely estimates to account for uncertainty. The 'optimistic' value represents the best-case scenario, assuming everything goes perfectly smoothly – a situation unlikely to persist. The 'pessimistic' estimate reflects the worst-case scenario, accounting for potential roadblocks or unforeseen complexities, while the 'most likely' value provides a central projection based on experience and judgment. Ben is correct in acknowledging this approach as it demonstrates an awareness of potential risks.
10 / 23
Sarah: "Hey team, I'm estimating 5 days to complete the user authentication feature. It's pretty straightforward – just standard OAuth integration."
Sarah's estimate of 5 days is likely too low because it doesn't account for risks. A three-point estimation would involve assigning an optimistic, most likely (or 'realistic'), and pessimistic value to the task. The 'conservative' approach, considering rate limiting and edge cases, is the most appropriate response in this scenario – acknowledging potential problems is crucial when using a robust estimation technique.
11 / 23
PR Description
During a code review of a new API endpoint, Alex writes in the PR description: 'I'm estimating this will take 3 days. Optimistic is 1 day, pessimistic is 7 days, and most likely is 3.' His team lead, Ben, asks for feedback on his estimation. Which response best reflects understanding of three-point estimation principles?
PR Description
Three-point estimation uses optimistic, pessimistic, and most likely estimates to account for uncertainty. The 'optimistic' value represents the best-case scenario, assuming everything goes perfectly smoothly – a situation unlikely to persist. The 'pessimistic' estimate reflects the worst-case scenario, accounting for potential roadblocks or unforeseen complexities, while the 'most likely' value provides a central projection based on experience and judgment. Ben is correct in acknowledging this approach as it demonstrates an awareness of potential risks.
12 / 23
Sarah: "Hey team, I'm estimating 5 days to complete the user authentication feature. It's pretty straightforward – just standard OAuth integration."
Sarah's estimate of 5 days is likely too low because it doesn't account for risks. A three-point estimation would involve assigning an optimistic, most likely (or 'realistic'), and pessimistic value to the task. The 'conservative' approach, considering rate limiting and edge cases, is the most appropriate response in this scenario – acknowledging potential problems is crucial when using a robust estimation technique.
13 / 23
PR Description
During a code review of a new API endpoint, Alex writes in the PR description: 'I'm estimating this will take 3 days. Optimistic is 1 day, pessimistic is 7 days, and most likely is 3.' His team lead, Ben, asks for feedback on his estimation. Which response best reflects understanding of three-point estimation principles?
PR Description
Three-point estimation uses optimistic, pessimistic, and most likely estimates to account for uncertainty. The 'optimistic' value represents the best-case scenario, assuming everything goes perfectly smoothly – a situation unlikely to persist. The 'pessimistic' estimate reflects the worst-case scenario, accounting for potential roadblocks or unforeseen complexities, while the 'most likely' value provides a central projection based on experience and judgment. Ben is correct in acknowledging this approach as it demonstrates an awareness of potential risks.
14 / 23
Reviewer: 'I'm estimating this will take 4 days. Optimistic is 2 days, pessimistic is 8 days, and most likely is 4.' What does the 'pessimistic' estimate primarily represent in a three-point estimation scenario?
The 'pessimistic' estimate is crucial for acknowledging potential problems. It's not about being negative; it's about proactively accounting for delays caused by bugs, dependencies, or unexpected challenges. This provides a buffer against overruns and helps manage expectations.
15 / 23
Dev (Liam): 'I'm estimating 7 days for this database migration. Optimistic is 3, most likely is 5, and pessimistic is 10.' Liam's use of the 'pessimistic' estimate suggests he anticipates what?
The 'pessimistic' estimate is used to account for potential problems that could significantly delay the project. It acknowledges risks such as database incompatibilities, performance issues, or unforeseen data transformations – factors that could realistically extend the timeline beyond a more optimistic projection.
16 / 23
Team Lead: 'I'm estimating this bug fix will take 2 days. Optimistic is 1 day, pessimistic is 4 days, and most likely is 2.' Which of the following best describes how the 'weighted average' is calculated in this scenario?
The weighted average method accounts for the varying degrees of certainty in each estimate. Multiplying the three values (1 * 7 + 5 * 3 + 8 * 1) / 15 is a common way to approach this calculation, but more simply, the formula used here is (optimistic + pessimistic + most likely)/3. This method provides a more robust estimate than a simple average, particularly when there's a significant difference between the optimistic and pessimistic values.
17 / 23
Maria provides a three-point estimate for refactoring a legacy module: Optimistic = 2 days, Most Likely = 5 days, Pessimistic = 10 days. What is the primary purpose of using a 'pessimistic' estimate in this scenario?
The 'pessimistic' estimate acts as a safety net. It's deliberately high to account for potential problems – technical debt, unforeseen bugs, or dependencies. Using this value ensures that the team has realistic buffer time and doesn't get caught off guard by delays; Option C is incorrect because it suggests ignoring risks.
18 / 23
Sarah, a developer, is explaining her estimates to her team: 'I'm estimating this new API endpoint will take 3 days. Optimistic is 1 day, most likely is 2 days, and pessimistic is 4 days.' What's the primary benefit of using these three points instead of just one estimate?
The core benefit of three-point estimation is improved risk assessment. By considering optimistic, most likely, and pessimistic outcomes, you gain a more comprehensive understanding of potential delays. This allows for better resource allocation, buffer time, and proactive problem-solving – Option C is incorrect because it suggests simplification.
19 / 23
You're reviewing a PR from Ben who includes these estimates for a microservice update: Optimistic = 1 day, Most Likely = 3 days, Pessimistic = 7 days. What is the *primary* reason Ben provides a pessimistic estimate?
The pessimistic estimate isn't about being difficult; it's a risk management technique. Ben is building in a contingency – a buffer – to account for potential problems that could delay the project. While options A and D are possible, option C best describes the *reason* behind using a pessimistic estimate as a standard practice.
20 / 23
You've received an API response detailing an estimated processing time: Optimistic = 0.5 seconds, Most Likely = 2 seconds, Pessimistic = 10 seconds. What is the primary value of incorporating a 'pessimistic' estimate in this case?
The pessimistic estimate is crucial for understanding the *worst-case* performance. It helps identify potential bottlenecks or issues where the API might experience delays due to high traffic, complex data, or other factors. This allows developers to proactively address these concerns and ensure a stable and reliable service.
21 / 23
During a standup meeting, David says, 'I'm estimating 6 hours to implement this new feature. Optimistic is 3 hours, most likely is 5 hours, and pessimistic is 8 hours.' What does David's 'pessimistic' estimate *primarily* represent in the context of project planning?
The 'pessimistic' estimate is designed to account for potential risks and challenges that could significantly increase the effort. It's not about being overly cautious but recognizing that things often take longer than initially anticipated; option B accurately describes this purpose.
22 / 23
Alex is writing a PR description for a complex data transformation task: 'I'm estimating 4 days. Optimistic is 2 days, most likely is 3 days, and pessimistic is 7 days.' What does the 'optimistic' estimate *primarily* serve to communicate?
The 'optimistic' estimate represents a best-case scenario – the shortest time Alex believes he *could* complete the task if everything went smoothly. It provides a benchmark and a positive expectation while acknowledging potential efficiency.
23 / 23
Sarah provides these three-point estimates for a new service integration: Optimistic = 1 day, Most Likely = 3 days, Pessimistic = 7 days. Which of the following best describes how Sarah would use the 'pessimistic' estimate in her planning?
The 'pessimistic' estimate is often used as a critical upper bound for risk assessment and capacity planning. If the task consistently exceeds this timeframe, it signals a potential problem that needs attention—option B highlights this key use case.
What does the "Three-Point Estimation" exercise cover?
Master the IT-English vocabulary of three-point estimation: optimistic, pessimistic, most likely, PERT and weighted averages.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
How many questions are in "Three-Point Estimation"?
This exercise has 23 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more Estimation Language exercises?
Browse the full Estimation Language hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.