Advanced
Estimation Language
#bias
#planning-fallacy
Estimation Bias Language
6 exercises — name and mitigate common estimation biases (anchoring, planning fallacy, overconfidence, scope creep) in professional English.
0 / 38 completed
1 / 38
A project manager suggests "3 days" as a starting point before you've looked at the code, and your final estimate ends up being 4 days even though the work genuinely warranted 8. What bias should you name in the retro, and how?
Anchoring bias occurs when an initial number (even an arbitrary one, like someone else's guess) unduly influences a subsequent independent estimate — the estimator adjusts insufficiently away from the anchor. Naming it explicitly in a retro helps the team recognise the pattern and mitigate it (e.g. asking estimators to size stories before hearing any suggested number).
Mitigation phrase: "Let's size this independently before anyone shares a number, to avoid anchoring each other." This is a well-documented cognitive bias (Tversky & Kahneman) directly applicable to estimation meetings.
Mitigation phrase: "Let's size this independently before anyone shares a number, to avoid anchoring each other." This is a well-documented cognitive bias (Tversky & Kahneman) directly applicable to estimation meetings.
2 / 38
You consistently estimate tasks assuming everything will go smoothly — no interruptions, no unexpected bugs, no code review delays. What is the correct name for this bias, and how do you describe a fix?
The planning fallacy (a form of over-optimism bias) describes the tendency to estimate based on the best-case scenario while ignoring the base rate of how similar tasks have actually gone historically — interruptions, code review cycles, unexpected complexity, etc.
Mitigation phrase: "Let's use reference-class forecasting — look at how long our last 5 similar tickets actually took, not how this one 'should' go in a perfect world." Naming both the bias and a concrete counter-technique (reference-class forecasting) is the professional way to raise this in a retro.
Mitigation phrase: "Let's use reference-class forecasting — look at how long our last 5 similar tickets actually took, not how this one 'should' go in a perfect world." Naming both the bias and a concrete counter-technique (reference-class forecasting) is the professional way to raise this in a retro.
3 / 38
What is the correct way to explain Hofstadter's Law to a stakeholder who is frustrated that a project is taking longer than the original estimate?
Hofstadter's Law is a well-known, semi-humorous but empirically supported observation about the persistent underestimation of software work, even by experienced estimators who try to correct for past underestimation. Explaining it to stakeholders should pair the observation with a practical response — buffers and iterative re-estimation — rather than presenting it as a fatalistic excuse.
Useful phrase: "This is a well-documented pattern, not an excuse — the response is to build in explicit buffer and re-estimate as we uncover more information, not to pretend the original number was exact."
Useful phrase: "This is a well-documented pattern, not an excuse — the response is to build in explicit buffer and re-estimate as we uncover more information, not to pretend the original number was exact."
4 / 38
A senior engineer gives a very confident, precise estimate ("exactly 11.5 days") for a task with significant unknowns. What bias might this reflect, and what is the correct way to raise the concern?
Overconfidence bias in estimation shows up as false precision — a single exact number that implies more certainty than the underlying knowledge supports. The correct response is not to dismiss the estimate but to gently suggest expressing it as a range that reflects genuine uncertainty.
Useful phrase: "Given the unknowns, could we express this as a range instead of a single number, to reflect the actual uncertainty?" Ranges are a standard technique (e.g. 3-point estimation: optimistic/likely/pessimistic) precisely to counter overconfidence bias.
Useful phrase: "Given the unknowns, could we express this as a range instead of a single number, to reflect the actual uncertainty?" Ranges are a standard technique (e.g. 3-point estimation: optimistic/likely/pessimistic) precisely to counter overconfidence bias.
5 / 38
A team member says "the last time we estimated a migration project it took 3x longer, so let's just triple every estimate going forward." Why is this an oversimplified response to estimation bias, and how would you phrase a better approach?
This describes the difference between an ad-hoc overcorrection and genuine estimation calibration — using a systematic, ongoing measurement of actual-vs-estimated ratios (ideally segmented by task type) rather than a single anecdote generalised into a blanket rule.
Useful phrase: "Let's track our estimate-to-actual ratio over time, per category of work, so we calibrate based on evidence rather than a single past incident." Calibration is a repeated, data-driven practice — not a one-time multiplier applied forever.
Useful phrase: "Let's track our estimate-to-actual ratio over time, per category of work, so we calibrate based on evidence rather than a single past incident." Calibration is a repeated, data-driven practice — not a one-time multiplier applied forever.
6 / 38
How do you correctly explain "scope creep" as a source of estimation inaccuracy, distinct from the estimate itself being wrong?
It's important to distinguish estimation error (the estimate itself was inaccurate for the defined scope) from scope creep (the delivered scope grew after the estimate was made, without revisiting the estimate). Conflating these leads teams to blame poor estimation for what is actually uncontrolled scope change.
Useful phrase: "The original estimate covered X — this new requirement (Y) wasn't included, so let's re-estimate rather than treating this as the original estimate being wrong." Explicitly re-estimating when scope changes is the correct professional response, rather than silently absorbing the extra work into the same timeline.
Useful phrase: "The original estimate covered X — this new requirement (Y) wasn't included, so let's re-estimate rather than treating this as the original estimate being wrong." Explicitly re-estimating when scope changes is the correct professional response, rather than silently absorbing the extra work into the same timeline.
7 / 38
Sarah's error stems from overconfidence bias. This occurs when individuals overestimate their ability to predict the difficulty of a task, often because they lack complete understanding or haven't considered potential complexities. The initial estimate served as an 'anchor,' influencing subsequent judgments and preventing her from adequately assessing the true effort required, despite encountering unexpected challenges. It's important to recognize that even seemingly simple tasks can introduce unforeseen complications.
8 / 38
PR Description: "Implementing the user authentication service will take approximately 3 days. I've built similar services before and this one seems straightforward." After a week of intense debugging and discovering several undocumented dependencies, the task takes 12 days to complete.
Which of the following best describes the primary source of error in this estimate?The correct answer is Availability Heuristic. This bias describes our tendency to rely heavily on easily recalled memories or examples when making judgments about future events. Sarah's overconfidence stemmed from readily available, albeit potentially misleading, recollections of similar projects – failing to adequately account for the uncertainties inherent in a new microservice and its interactions with other systems. The other options represent different biases but don't capture the core issue of relying on easily accessible, potentially skewed information.
9 / 38
During a sprint planning meeting, David states, "I can finish the database schema design in one day – it's just about mapping out the tables and relationships. I've done similar projects before." Three days later, after wrestling with data migration complexities, performance considerations, and unexpected constraints imposed by existing systems, he delivers a partially complete schema that requires another two days to finalize. Which of the following best reflects David's primary error in estimation?
The correct answer is 'Overconfidence' because David's statement suggests an inflated belief in his past experience without adequately considering the specific context of this new project. While scope creep and confirmation bias could play a role, they aren't the *primary* source of error here; the core issue is that he underestimated the complexities inherent in integrating with existing systems – a common pitfall when assuming prior experiences translate directly across projects. Insufficient planning wasn't his primary mistake, it was a lack of realistic assessment regarding integration challenges.
10 / 38
Sarah's error stems from overconfidence bias. This occurs when individuals overestimate their ability to predict the difficulty of a task, often because they lack complete understanding or haven't considered potential complexities. The initial estimate served as an 'anchor,' influencing subsequent judgments and preventing her from adequately assessing the true effort required, despite encountering unexpected challenges. It's important to recognize that even seemingly simple tasks can introduce unforeseen complications.
11 / 38
PR Description: "Implementing the user authentication service will take approximately 3 days. I've built similar services before and this one seems straightforward." After a week of intense debugging and discovering several undocumented dependencies, the task takes 12 days to complete.
Which of the following best describes the primary source of error in this estimate?The correct answer is Availability Heuristic. This bias describes our tendency to rely heavily on easily recalled memories or examples when making judgments about future events. Sarah's overconfidence stemmed from readily available, albeit potentially misleading, recollections of similar projects – failing to adequately account for the uncertainties inherent in a new microservice and its interactions with other systems. The other options represent different biases but don't capture the core issue of relying on easily accessible, potentially skewed information.
12 / 38
During a sprint planning meeting, David states, "I can finish the database schema design in one day – it's just about mapping out the tables and relationships. I've done similar projects before." Three days later, after wrestling with data migration complexities, performance considerations, and unexpected constraints imposed by existing systems, he delivers a partially complete schema that requires another two days to finalize. Which of the following best reflects David's primary error in estimation?
The correct answer is 'Overconfidence' because David's statement suggests an inflated belief in his past experience without adequately considering the specific context of this new project. While scope creep and confirmation bias could play a role, they aren't the *primary* source of error here; the core issue is that he underestimated the complexities inherent in integrating with existing systems – a common pitfall when assuming prior experiences translate directly across projects. Insufficient planning wasn't his primary mistake, it was a lack of realistic assessment regarding integration challenges.
13 / 38
Sarah's error stems from overconfidence bias. This occurs when individuals overestimate their ability to predict the difficulty of a task, often because they lack complete understanding or haven't considered potential complexities. The initial estimate served as an 'anchor,' influencing subsequent judgments and preventing her from adequately assessing the true effort required, despite encountering unexpected challenges. It's important to recognize that even seemingly simple tasks can introduce unforeseen complications.
14 / 38
PR Description: "Implementing the user authentication service will take approximately 3 days. I've built similar services before and this one seems straightforward." After a week of intense debugging and discovering several undocumented dependencies, the task takes 12 days to complete.
Which of the following best describes the primary source of error in this estimate?The correct answer is Availability Heuristic. This bias describes our tendency to rely heavily on easily recalled memories or examples when making judgments about future events. Sarah's overconfidence stemmed from readily available, albeit potentially misleading, recollections of similar projects – failing to adequately account for the uncertainties inherent in a new microservice and its interactions with other systems. The other options represent different biases but don't capture the core issue of relying on easily accessible, potentially skewed information.
15 / 38
During a sprint planning meeting, David states, "I can finish the database schema design in one day – it's just about mapping out the tables and relationships. I've done similar projects before." Three days later, after wrestling with data migration complexities, performance considerations, and unexpected constraints imposed by existing systems, he delivers a partially complete schema that requires another two days to finalize. Which of the following best reflects David's primary error in estimation?
The correct answer is 'Overconfidence' because David's statement suggests an inflated belief in his past experience without adequately considering the specific context of this new project. While scope creep and confirmation bias could play a role, they aren't the *primary* source of error here; the core issue is that he underestimated the complexities inherent in integrating with existing systems – a common pitfall when assuming prior experiences translate directly across projects. Insufficient planning wasn't his primary mistake, it was a lack of realistic assessment regarding integration challenges.
16 / 38
Sarah's error stems from overconfidence bias. This occurs when individuals overestimate their ability to predict the difficulty of a task, often because they lack complete understanding or haven't considered potential complexities. The initial estimate served as an 'anchor,' influencing subsequent judgments and preventing her from adequately assessing the true effort required, despite encountering unexpected challenges. It's important to recognize that even seemingly simple tasks can introduce unforeseen complications.
17 / 38
PR Description: "Implementing the user authentication service will take approximately 3 days. I've built similar services before and this one seems straightforward." After a week of intense debugging and discovering several undocumented dependencies, the task takes 12 days to complete.
Which of the following best describes the primary source of error in this estimate?The correct answer is Availability Heuristic. This bias describes our tendency to rely heavily on easily recalled memories or examples when making judgments about future events. Sarah's overconfidence stemmed from readily available, albeit potentially misleading, recollections of similar projects – failing to adequately account for the uncertainties inherent in a new microservice and its interactions with other systems. The other options represent different biases but don't capture the core issue of relying on easily accessible, potentially skewed information.
18 / 38
During a sprint planning meeting, David states, "I can finish the database schema design in one day – it's just about mapping out the tables and relationships. I've done similar projects before." Three days later, after wrestling with data migration complexities, performance considerations, and unexpected constraints imposed by existing systems, he delivers a partially complete schema that requires another two days to finalize. Which of the following best reflects David's primary error in estimation?
The correct answer is 'Overconfidence' because David's statement suggests an inflated belief in his past experience without adequately considering the specific context of this new project. While scope creep and confirmation bias could play a role, they aren't the *primary* source of error here; the core issue is that he underestimated the complexities inherent in integrating with existing systems – a common pitfall when assuming prior experiences translate directly across projects. Insufficient planning wasn't his primary mistake, it was a lack of realistic assessment regarding integration challenges.
19 / 38
During a code review of a new API endpoint, Mark says, "Based on the API spec, this function should take no more than 30 minutes to develop. I've built similar endpoints before."
Which of the following best describes the potential estimation bias at play here?
Mark's reliance on past experience represents *Anchoring Bias*. This bias occurs when individuals fixate on an initial piece of information (his previous projects) and struggle to adjust their estimates even when new data suggests otherwise. Confirmation bias is a related but distinct issue—he's not just anchoring, he's also seeking out information to support his existing view. Optimism bias describes an overly positive outlook generally, while the availability heuristic involves using easily recalled memories, which isn't quite as central here.
20 / 38
In a Slack channel discussing a new feature, Alex writes: "We're estimating this will take 5 days. It's pretty straightforward – just need to integrate with the existing payment gateway. I've done this before."
The team lead, Sarah, responds: "That sounds ambitious. Can you break down the key unknowns and potential risks?"
Sarah's response is crucial. She's acknowledging Alex's initial estimate but immediately prompting for a deeper dive into potential unknowns and risks – this addresses the core issue of estimation bias by forcing him to consider factors he might have initially overlooked. Simply criticizing his confidence isn't helpful; it doesn't tackle the root cause.
21 / 38
A developer submits a PR with the following description: "Implementing the new user profile API will take approximately 7 days. I've built similar REST APIs before, and this one seems relatively simple."
Which of the following statements best explains why this PR description is potentially problematic regarding estimation bias?
The core problem is the assumption that 'similar' always equates to 'same'. Past experience doesn't guarantee identical complexity. This describes *Anchoring Bias* - the estimate is anchored on past projects without sufficient consideration for potential differences in scope, technology, or requirements. Focusing solely on technical details can also mask the risk of scope creep.
22 / 38
During a daily stand-up meeting, Liam states: "I'm working on refactoring the legacy authentication module – I think it'll take me about 2 days. It's mostly just updating some old code and adding a few new tests."
What is the most significant potential issue with Liam's statement, considering estimation bias?
The danger lies in Liam's overly simplistic view of 'updating old code'. Legacy systems often have hidden complexities – technical debt, undocumented dependencies, or unexpected interactions – that can significantly increase development time. This is a classic example of *Anchoring Bias* - he's anchoring his estimate on the superficial task description without considering the underlying challenges.
23 / 38
Sarah, during a code review, says: "I've reviewed the design for the new data processing pipeline. It looks like it will take approximately 4 days to implement fully – including testing and documentation."
Which of the following best explains why Sarah's statement might be problematic from an estimation bias perspective?
Sarah's estimate lacks crucial context. The statement doesn't consider potential integration complexities or the need for robust testing—these are common pitfalls that often inflate development time. This reflects a failure to account for unknowns, highlighting a key aspect of estimation bias: underestimating risk and complexity.
24 / 38
During a code review of a new API endpoint, Mark says, "Based on the API spec, this function should take no more than 30 minutes to develop. I've built similar endpoints before."
Which of the following best describes the potential estimation bias at play here?
Mark's reliance on past experience represents *Anchoring Bias*. This bias occurs when individuals fixate on an initial piece of information (his previous projects) and struggle to adjust their estimates even when new data suggests otherwise. Confirmation bias is a related but distinct issue—he's not just anchoring, he's also seeking out information to support his existing view. Optimism bias describes an overly positive outlook generally, while the availability heuristic involves using easily recalled memories, which isn't quite as central here.
25 / 38
In a Slack channel discussing a new feature, Alex writes: "We're estimating this will take 5 days. It's pretty straightforward – just need to integrate with the existing payment gateway. I've done this before."
The team lead, Sarah, responds: "That sounds ambitious. Can you break down the key unknowns and potential risks?"
Sarah's response is crucial. She's acknowledging Alex's initial estimate but immediately prompting for a deeper dive into potential unknowns and risks – this addresses the core issue of estimation bias by forcing him to consider factors he might have initially overlooked. Simply criticizing his confidence isn't helpful; it doesn't tackle the root cause.
26 / 38
A developer submits a PR with the following description: "Implementing the new user profile API will take approximately 7 days. I've built similar REST APIs before, and this one seems relatively simple."
Which of the following statements best explains why this PR description is potentially problematic regarding estimation bias?
The core problem is the assumption that 'similar' always equates to 'same'. Past experience doesn't guarantee identical complexity. This describes *Anchoring Bias* - the estimate is anchored on past projects without sufficient consideration for potential differences in scope, technology, or requirements. Focusing solely on technical details can also mask the risk of scope creep.
27 / 38
During a daily stand-up meeting, Liam states: "I'm working on refactoring the legacy authentication module – I think it'll take me about 2 days. It's mostly just updating some old code and adding a few new tests."
What is the most significant potential issue with Liam's statement, considering estimation bias?
The danger lies in Liam's overly simplistic view of 'updating old code'. Legacy systems often have hidden complexities – technical debt, undocumented dependencies, or unexpected interactions – that can significantly increase development time. This is a classic example of *Anchoring Bias* - he's anchoring his estimate on the superficial task description without considering the underlying challenges.
28 / 38
Sarah, during a code review, says: "I've reviewed the design for the new data processing pipeline. It looks like it will take approximately 4 days to implement fully – including testing and documentation."
Which of the following best explains why Sarah's statement might be problematic from an estimation bias perspective?
Sarah's estimate lacks crucial context. The statement doesn't consider potential integration complexities or the need for robust testing—these are common pitfalls that often inflate development time. This reflects a failure to account for unknowns, highlighting a key aspect of estimation bias: underestimating risk and complexity.
29 / 38
During a code review of a new API endpoint, Mark says, "Based on the API spec, this function should take no more than 30 minutes to develop. I've built similar endpoints before."
Which of the following best describes the potential estimation bias at play here?
Mark's reliance on past experience represents *Anchoring Bias*. This bias occurs when individuals fixate on an initial piece of information (his previous projects) and struggle to adjust their estimates even when new data suggests otherwise. Confirmation bias is a related but distinct issue—he's not just anchoring, he's also seeking out information to support his existing view. Optimism bias describes an overly positive outlook generally, while the availability heuristic involves using easily recalled memories, which isn't quite as central here.
30 / 38
In a Slack channel discussing a new feature, Alex writes: "We're estimating this will take 5 days. It's pretty straightforward – just need to integrate with the existing payment gateway. I've done this before."
The team lead, Sarah, responds: "That sounds ambitious. Can you break down the key unknowns and potential risks?"
Sarah's response is crucial. She's acknowledging Alex's initial estimate but immediately prompting for a deeper dive into potential unknowns and risks – this addresses the core issue of estimation bias by forcing him to consider factors he might have initially overlooked. Simply criticizing his confidence isn't helpful; it doesn't tackle the root cause.
31 / 38
A developer submits a PR with the following description: "Implementing the new user profile API will take approximately 7 days. I've built similar REST APIs before, and this one seems relatively simple."
Which of the following statements best explains why this PR description is potentially problematic regarding estimation bias?
The core problem is the assumption that 'similar' always equates to 'same'. Past experience doesn't guarantee identical complexity. This describes *Anchoring Bias* - the estimate is anchored on past projects without sufficient consideration for potential differences in scope, technology, or requirements. Focusing solely on technical details can also mask the risk of scope creep.
32 / 38
During a daily stand-up meeting, Liam states: "I'm working on refactoring the legacy authentication module – I think it'll take me about 2 days. It's mostly just updating some old code and adding a few new tests."
What is the most significant potential issue with Liam's statement, considering estimation bias?
The danger lies in Liam's overly simplistic view of 'updating old code'. Legacy systems often have hidden complexities – technical debt, undocumented dependencies, or unexpected interactions – that can significantly increase development time. This is a classic example of *Anchoring Bias* - he's anchoring his estimate on the superficial task description without considering the underlying challenges.
33 / 38
Sarah, during a code review, says: "I've reviewed the design for the new data processing pipeline. It looks like it will take approximately 4 days to implement fully – including testing and documentation."
Which of the following best explains why Sarah's statement might be problematic from an estimation bias perspective?
Sarah's estimate lacks crucial context. The statement doesn't consider potential integration complexities or the need for robust testing—these are common pitfalls that often inflate development time. This reflects a failure to account for unknowns, highlighting a key aspect of estimation bias: underestimating risk and complexity.
34 / 38
During a code review of a new API endpoint, Mark says, "Based on the API spec, this function should take no more than 30 minutes to develop. I've built similar endpoints before."
Which of the following best describes the potential estimation bias at play here?
Mark's reliance on past experience represents *Anchoring Bias*. This bias occurs when individuals fixate on an initial piece of information (his previous projects) and struggle to adjust their estimates even when new data suggests otherwise. Confirmation bias is a related but distinct issue—he's not just anchoring, he's also seeking out information to support his existing view. Optimism bias describes an overly positive outlook generally, while the availability heuristic involves using easily recalled memories, which isn't quite as central here.
35 / 38
In a Slack channel discussing a new feature, Alex writes: "We're estimating this will take 5 days. It's pretty straightforward – just need to integrate with the existing payment gateway. I've done this before."
The team lead, Sarah, responds: "That sounds ambitious. Can you break down the key unknowns and potential risks?"
Sarah's response is crucial. She's acknowledging Alex's initial estimate but immediately prompting for a deeper dive into potential unknowns and risks – this addresses the core issue of estimation bias by forcing him to consider factors he might have initially overlooked. Simply criticizing his confidence isn't helpful; it doesn't tackle the root cause.
36 / 38
A developer submits a PR with the following description: "Implementing the new user profile API will take approximately 7 days. I've built similar REST APIs before, and this one seems relatively simple."
Which of the following statements best explains why this PR description is potentially problematic regarding estimation bias?
The core problem is the assumption that 'similar' always equates to 'same'. Past experience doesn't guarantee identical complexity. This describes *Anchoring Bias* - the estimate is anchored on past projects without sufficient consideration for potential differences in scope, technology, or requirements. Focusing solely on technical details can also mask the risk of scope creep.
37 / 38
During a daily stand-up meeting, Liam states: "I'm working on refactoring the legacy authentication module – I think it'll take me about 2 days. It's mostly just updating some old code and adding a few new tests."
What is the most significant potential issue with Liam's statement, considering estimation bias?
The danger lies in Liam's overly simplistic view of 'updating old code'. Legacy systems often have hidden complexities – technical debt, undocumented dependencies, or unexpected interactions – that can significantly increase development time. This is a classic example of *Anchoring Bias* - he's anchoring his estimate on the superficial task description without considering the underlying challenges.
38 / 38
Sarah, during a code review, says: "I've reviewed the design for the new data processing pipeline. It looks like it will take approximately 4 days to implement fully – including testing and documentation."
Which of the following best explains why Sarah's statement might be problematic from an estimation bias perspective?
Sarah's estimate lacks crucial context. The statement doesn't consider potential integration complexities or the need for robust testing—these are common pitfalls that often inflate development time. This reflects a failure to account for unknowns, highlighting a key aspect of estimation bias: underestimating risk and complexity.
Frequently Asked Questions
What does the "Estimation Bias Language — Estimation Language Exercise" exercise cover?
Practise naming and mitigating estimation biases in English: anchoring, over-optimism, Hofstadter's Law, overconfidence, and scope creep. 6 exercises.
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 "Estimation Bias Language — Estimation Language Exercise"?
This exercise has 38 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.