Practise the IT-English phrasing for re-estimating work: flagging slippage early, explaining changes and resetting expectations.
0 / 18 completed
1 / 18
You realise a task will overrun. When should you communicate it?
Flagging slippage early lets stakeholders re-plan; surprises at the deadline erode trust.
2 / 18
Which phrasing best 'explains' a revised estimate?
Giving the concrete reason for the change makes the new estimate credible and informative.
3 / 18
What does 'scope creep' refer to in re-estimation?
Scope creep is the gradual growth of requirements that inflates effort and justifies re-estimation.
4 / 18
Which is the best way to 'reset expectations' with a stakeholder?
Resetting expectations transparently, with trade-offs and re-confirmed priorities, keeps trust intact.
5 / 18
Which sentence correctly uses 'slippage'?
Slippage is falling behind the planned schedule; naming it clearly prompts timely re-planning.
6 / 18
Sarah: 'Okay team, I've been digging into the performance of this new API endpoint. Initial tests show it's significantly slower than anticipated, and we're seeing a high rate of timeouts. We need to refactor some of the data retrieval logic.'
Which Slack message best reflects Sarah's communication regarding this issue?
The correct answer, 'Okay team, I've identified a performance bottleneck. Let's schedule a meeting to discuss,' demonstrates proactive communication and immediately proposes a solution – a meeting – to address the problem. The other options either downplay the issue (insufficient), offer vague solutions without urgency (schedule a meeting), or incorrectly state that everything is fine, failing to acknowledge the reported problems. Effective re-estimation communication often involves highlighting potential roadblocks and proposing immediate action.
7 / 18
Team Lead: 'Hey everyone, we've just received feedback on the new user onboarding flow. Stakeholders are requesting a dark mode option and integration with our CRM – things that weren't in the original scope. I need to update the timeline. What's the most effective way to communicate this change to the team and stakeholders?
This scenario highlights the importance of proactively managing scope changes. Option A is reactive and doesn't acknowledge the impact. Option B simply states a delay without explaining *why*, which can frustrate stakeholders. Option D minimizes the issue, failing to address the fundamental shift in requirements. Option 2 demonstrates a clear, transparent approach – acknowledging the change, proposing a discussion, and outlining next steps for reassessment, which is crucial for effective re-estimation communication.
8 / 18
Sarah: 'Okay team, I've been digging into the performance of this new API endpoint. Initial tests show it's significantly slower than anticipated, and we're seeing a high rate of timeouts. We need to refactor some of the data retrieval logic.'
Which Slack message best reflects Sarah's communication regarding this issue?
The correct answer, 'Okay team, I've identified a performance bottleneck. Let's schedule a meeting to discuss,' demonstrates proactive communication and immediately proposes a solution – a meeting – to address the problem. The other options either downplay the issue (insufficient), offer vague solutions without urgency (schedule a meeting), or incorrectly state that everything is fine, failing to acknowledge the reported problems. Effective re-estimation communication often involves highlighting potential roadblocks and proposing immediate action.
9 / 18
Team Lead: 'Hey everyone, we've just received feedback on the new user onboarding flow. Stakeholders are requesting a dark mode option and integration with our CRM – things that weren't in the original scope. I need to update the timeline. What's the most effective way to communicate this change to the team and stakeholders?
This scenario highlights the importance of proactively managing scope changes. Option A is reactive and doesn't acknowledge the impact. Option B simply states a delay without explaining *why*, which can frustrate stakeholders. Option D minimizes the issue, failing to address the fundamental shift in requirements. Option 2 demonstrates a clear, transparent approach – acknowledging the change, proposing a discussion, and outlining next steps for reassessment, which is crucial for effective re-estimation communication.
10 / 18
Sarah: 'Okay team, I've been digging into the performance of this new API endpoint. Initial tests show it's significantly slower than anticipated, and we're seeing a high rate of timeouts. We need to refactor some of the data retrieval logic.'
Which Slack message best reflects Sarah's communication regarding this issue?
The correct answer, 'Okay team, I've identified a performance bottleneck. Let's schedule a meeting to discuss,' demonstrates proactive communication and immediately proposes a solution – a meeting – to address the problem. The other options either downplay the issue (insufficient), offer vague solutions without urgency (schedule a meeting), or incorrectly state that everything is fine, failing to acknowledge the reported problems. Effective re-estimation communication often involves highlighting potential roadblocks and proposing immediate action.
11 / 18
Team Lead: 'Hey everyone, we've just received feedback on the new user onboarding flow. Stakeholders are requesting a dark mode option and integration with our CRM – things that weren't in the original scope. I need to update the timeline. What's the most effective way to communicate this change to the team and stakeholders?
This scenario highlights the importance of proactively managing scope changes. Option A is reactive and doesn't acknowledge the impact. Option B simply states a delay without explaining *why*, which can frustrate stakeholders. Option D minimizes the issue, failing to address the fundamental shift in requirements. Option 2 demonstrates a clear, transparent approach – acknowledging the change, proposing a discussion, and outlining next steps for reassessment, which is crucial for effective re-estimation communication.
12 / 18
Sarah: 'Okay team, I've been digging into the performance of this new API endpoint. Initial tests show it's significantly slower than anticipated, and we're seeing a high rate of timeouts. We need to refactor some of the data retrieval logic.'
Which Slack message best reflects Sarah's communication regarding this issue?
The correct answer, 'Okay team, I've identified a performance bottleneck. Let's schedule a meeting to discuss,' demonstrates proactive communication and immediately proposes a solution – a meeting – to address the problem. The other options either downplay the issue (insufficient), offer vague solutions without urgency (schedule a meeting), or incorrectly state that everything is fine, failing to acknowledge the reported problems. Effective re-estimation communication often involves highlighting potential roadblocks and proposing immediate action.
13 / 18
Team Lead: 'Hey everyone, we've just received feedback on the new user onboarding flow. Stakeholders are requesting a dark mode option and integration with our CRM – things that weren't in the original scope. I need to update the timeline. What's the most effective way to communicate this change to the team and stakeholders?
This scenario highlights the importance of proactively managing scope changes. Option A is reactive and doesn't acknowledge the impact. Option B simply states a delay without explaining *why*, which can frustrate stakeholders. Option D minimizes the issue, failing to address the fundamental shift in requirements. Option 2 demonstrates a clear, transparent approach – acknowledging the change, proposing a discussion, and outlining next steps for reassessment, which is crucial for effective re-estimation communication.
14 / 18
// Original code review comment: 'This function is too complex. Refactor it!'
During a code review, which of the following responses best addresses the reviewer's concern while communicating potential implications?
The best response acknowledges the reviewer's concern and proactively suggests a plan. Option A clearly communicates the trade-off between refactoring and potential risks. Options B and D dismiss the feedback, while option C initiates a constructive discussion about mitigation strategies. This demonstrates proactive communication and collaboration.
15 / 18
You're part of a team working on an API integration. The lead developer sends this Slack message: 'Okay, the initial performance tests are… not great. We're seeing high latency. Need to investigate.' What is the MOST effective follow-up message to send?
The initial message is vague. Option 1 directly requests more information – a crucial step in re-estimation communication. Options B and C demonstrate a proactive approach to understanding the problem. Option D is dismissive and doesn't address the urgency of the situation.
16 / 18
You've been asked to write the PR description for a change that significantly increases the complexity of a core module. Which statement is MOST appropriate to include?
Option 3 directly addresses the increased complexity, highlighting the need for careful consideration. It's vital to flag changes that could have unintended consequences. Options A and B are misleading, while option D downplays the significance of the change.
17 / 18
During your daily stand-up, you realize a task will take longer than initially estimated. What's the BEST way to communicate this to the team?
Option 2 is direct and transparent. It clearly states the revised estimate and provides context. This allows the team to adjust plans accordingly. Option A avoids responsibility, while option B is vague and doesn't offer a solution. Option D shifts blame.
18 / 18
A stakeholder says: 'We need to add support for iOS devices!' This wasn't in the original requirements document. How do you best respond?
Option 2 acknowledges the stakeholder's request but immediately raises concerns about its impact. This initiates a discussion about scope and priorities. Options A is overly enthusiastic without considering consequences, while option B avoids addressing the problem and option C is unhelpful.
What does the "Re-estimation Communication" exercise cover?
Practise the IT-English phrasing for re-estimating work: flagging slippage early, explaining changes and resetting expectations.
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 "Re-estimation Communication"?
This exercise has 18 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.