Learn the IT-English vocabulary for handling dependencies and risk in estimates: blockers, assumptions, buffers and contingency.
0 / 14 completed
1 / 14
An engineer says: 'This estimate assumes the auth API is ready.' What is this an example of?
Surfacing assumptions makes clear what conditions the estimate relies on, so risks are visible.
2 / 14
A task is 'blocked' by another team. How should that affect the estimate?
External dependencies/blockers add risk and should be called out rather than buried in the estimate.
3 / 14
The plan adds a 'buffer'. What is a buffer?
A buffer (or contingency) is padding to cover the uncertainty inherent in estimates.
4 / 14
Which sentence correctly uses 'critical path'?
The critical path is the chain of dependent tasks that determines the minimum project duration.
5 / 14
How should a high-risk estimate best be 'communicated'?
Expressing risky estimates as a range with stated drivers sets honest expectations.
6 / 14
PR Description: 'Adding new feature X. Estimated time: 3 days.'
During a code review, your colleague comments: 'This estimate feels optimistic. We haven't factored in the potential for integration issues with the legacy payment gateway, and that's historically been a significant source of delays.' Which of the following best captures the core concern raised by your colleague?
The colleague's comment highlights the importance of considering external dependencies and their potential impact on timelines. While all options touch upon aspects of estimation, the core issue is the lack of awareness regarding risks stemming from integrating with established systems – specifically, the legacy payment gateway. The other options focus on more general issues like detail or timeframe without directly addressing the risk element that's driving the concern about the estimate's validity.
7 / 14
PR Description: 'Adding new feature X. Estimated time: 3 days.'
During a code review, your colleague comments: 'This estimate feels optimistic. We haven't factored in the potential for integration issues with the legacy payment gateway, and that's historically been a significant source of delays.' Which of the following best captures the core concern raised by your colleague?
The colleague's comment highlights the importance of considering external dependencies and their potential impact on timelines. While all options touch upon aspects of estimation, the core issue is the lack of awareness regarding risks stemming from integrating with established systems – specifically, the legacy payment gateway. The other options focus on more general issues like detail or timeframe without directly addressing the risk element that's driving the concern about the estimate's validity.
8 / 14
PR Description: 'Adding new feature X. Estimated time: 3 days.'
During a code review, your colleague comments: 'This estimate feels optimistic. We haven't factored in the potential for integration issues with the legacy payment gateway, and that's historically been a significant source of delays.' Which of the following best captures the core concern raised by your colleague?
The colleague's comment highlights the importance of considering external dependencies and their potential impact on timelines. While all options touch upon aspects of estimation, the core issue is the lack of awareness regarding risks stemming from integrating with established systems – specifically, the legacy payment gateway. The other options focus on more general issues like detail or timeframe without directly addressing the risk element that's driving the concern about the estimate's validity.
9 / 14
PR Description: 'Adding new feature X. Estimated time: 3 days.'
During a code review, your colleague comments: 'This estimate feels optimistic. We haven't factored in the potential for integration issues with the legacy payment gateway, and that's historically been a significant source of delays.' Which of the following best captures the core concern raised by your colleague?
The colleague's comment highlights the importance of considering external dependencies and their potential impact on timelines. While all options touch upon aspects of estimation, the core issue is the lack of awareness regarding risks stemming from integrating with established systems – specifically, the legacy payment gateway. The other options focus on more general issues like detail or timeframe without directly addressing the risk element that's driving the concern about the estimate's validity.
10 / 14
Sarah (Product Owner) sends this Slack message: 'Hey team, we're estimating 5 days for the new user onboarding flow. It's pretty straightforward, right?' Which of the following best captures Sarah's potential underestimation regarding dependencies and risk?
Sarah's statement is overly simplistic. A straightforward feature can quickly become complex when dependencies exist – for example, reliance on another team's API or the availability of third-party services. The key here is to identify potential bottlenecks and external factors that could significantly increase development time. This highlights a failure to account for risk.
11 / 14
During a standup update, David says: 'I'm working on the data migration script. I've allocated 2 days.' The team lead responds with: 'David, are you aware that this script needs to interface with the legacy database which is known for intermittent downtime?' How should David adjust his estimate?
David's initial estimate was insufficiently conservative given the known instability of the legacy database. Recognizing potential downtime is crucial for accurate risk assessment. A proactive approach – seeking more information and adjusting the estimate accordingly – demonstrates responsible planning. Simply increasing the time based on a guess isn't sufficient.
12 / 14
You're writing a PR description for adding a new authentication endpoint. The estimated effort is 4 days. Which of the following best describes how to communicate this estimate effectively, considering potential risks?
The most effective PR description acknowledges potential risks and provides context. Simply stating the estimated time doesn't convey the level of uncertainty or the factors influencing it. Including a mention of the identity provider API (a common source of instability) demonstrates awareness and justifies the estimate better.
13 / 14
A project manager is explaining the concept of a 'critical path' to a junior developer. Which of the following best describes this term in the context of estimating?
The critical path represents the sequence of dependent activities that directly impacts the project's deadline. Any delay on a task within this path will inevitably push back the entire project completion date. Understanding the critical path is fundamental to identifying and mitigating potential risks and ensuring timely delivery.
14 / 14
You've estimated 7 days for a complex UI component. During a code review, a senior developer points out: 'This estimate seems high. We need to account for potential accessibility issues and thorough testing.' What is the *most* important thing to communicate about this revised estimate?
The senior developer's comment highlights the importance of incorporating identified risks into the estimate. Transparently documenting these risks and their potential impact (e.g., increased testing time, accessibility remediation) demonstrates a robust approach to estimation and allows for more accurate forecasting.
What does the "Dependencies & Risk in Estimates" exercise cover?
Learn the IT-English vocabulary for handling dependencies and risk in estimates: blockers, assumptions, buffers and contingency.
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 "Dependencies & Risk in Estimates"?
This exercise has 14 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.