Scope Negotiation: Phrases for Managing Expectations
5 exercises on scope negotiation phrases. Choose the most natural and professional option.
0 / 10 completed
1 / 10
A stakeholder wants to add a feature mid-sprint. You need to say it is out of scope without being dismissive. Which phrase works best?
Option B is the professional way to decline scope additions. 'That's out of scope for this sprint' is a factual boundary, not a personal refusal. 'Could we add it to the backlog and revisit in planning?' immediately offers a constructive path forward rather than a dead end. 'We can't do that' (A) sounds like a capability problem rather than a prioritisation decision. 'That's not happening this sprint' (C) is blunter and gives no next step. 'We don't have time for that' (D) sounds dismissive. Always pair a scope boundary with a path forward — 'not now, but here's when and how' keeps the relationship intact.
2 / 10
A full feature will take three weeks but you want to propose a faster, slimmer version. Which phrase is most effective?
Option D is the complete MVP proposal. It labels the approach ('lightweight version'), specifies what is and isn't included ('core read path without the filtering UI'), and states the benefit ('ship value faster'). 'We could do a simpler version' (A) is too vague — what is included and excluded? 'Let's not do the full thing' (B) proposes reduction without defining what remains. 'A basic version might work' (C) is non-committal and doesn't name the scope. Effective MVP proposals are specific about what is in scope, what is deferred, and what value is delivered by the lean version.
3 / 10
You want to understand what the minimum viable version of a feature needs to be. Which question is most useful?
Option A is the best question because it defines 'minimum' in terms of user value ('for this to be useful') rather than just technical simplicity. This grounds the conversation in outcomes. 'What's the simplest version?' (B) focuses on technical complexity rather than user value — you might build the simplest thing that is still useless. 'Can we cut some stuff?' (C) sounds like cost-cutting rather than principled scoping. 'What's the MVP here?' (D) is the right concept but too jargon-laden — stakeholders may have different mental models of MVP. Framing around usefulness keeps everyone aligned on purpose.
4 / 10
A stakeholder wants to add an export feature, which would require dropping the notification redesign. How do you explain this trade-off?
Option C is precise and respectful. It names both specific items (export feature, notification redesign), states the constraint clearly (need to drop), and explains why (both are substantial pieces of work). This gives the stakeholder the information needed to make a real prioritisation decision. 'If we add that, something else will suffer' (A) is vague — what else? What kind of suffering? 'Adding things means removing things' (B) is a principle, not a decision-point. 'We can't add more without removing something' (D) says the same thing more firmly but still doesn't name the specific trade-off. Name both items when presenting a trade-off.
5 / 10
A useful feature came up late in the sprint and should be given proper attention. Which phrase defers it most professionally?
Option B is the professional deferral. It proposes a specific next touchpoint ('next sprint's planning'), and explains why deferring is actually better for the feature ('give it proper time rather than rushing it in'). This reframes deferral as a quality decision, not a rejection. 'Let's talk about this later' (A) is vague about when and gives no reason. 'Not this sprint, maybe next' (C) is honest but curt, with no reasoning. 'We should defer this item' (D) is procedural language without a commitment to when it will resurface. Good deferrals name the next opportunity and explain what deferring protects.
6 / 10
Sarah (Product Owner) just emailed the team: 'Can we integrate with Stripe for payments? It would be amazing!' You're a senior developer. Which phrase best sets expectations regarding this request without immediately saying no?
The key here is to acknowledge the request's value while gently introducing the complexities. Option 2 buys you time and sets the stage for a more detailed discussion about scope. Options A & B are too direct in their refusal, and option C over-complicates things unnecessarily at this early stage.
7 / 10
You're reviewing a pull request from Mark (Junior Dev). He's implemented a new API endpoint for user profile updates. His PR description says: 'Added user profile functionality.' Which phrase would you use to subtly suggest he refine his description to better align with the actual work?
Mark's description is too high-level. Option 1 prompts him for crucial details about the implementation – data fields, validations, etc., which are vital for code review and understanding the scope of the change. Options A & C are technically correct but don't address the core problem of a vague description, while option B suggests a technical workaround rather than clarifying the *scope*.
8 / 10
During a standup meeting, David (Team Lead) asks: 'What's blocking you on Task X?' You respond with: 'I'm waiting for clarification on the acceptance criteria.' Which phrase best communicates that the team needs to negotiate those criteria to proceed?
This situation highlights the importance of proactively addressing ambiguity. Option 2 directly states the need for negotiation regarding the acceptance criteria – the core of scope management. Options A & B are passive responses, and option C misrepresents the situation.
9 / 10
You're responding to a Slack message from Emily (Stakeholder) regarding a new feature request: 'We need to add a dark mode toggle to the app!' You know this would require a major UI overhaul. Which phrase best manages her expectations while exploring the possibility?
Option 2 acknowledges Emily's suggestion but immediately flags the substantial effort involved. This is a crucial step in scope negotiation. Options A & C are overly enthusiastic or dismissive, while option B ignores the inherent complexity of the request.
10 / 10
You've been assigned a new task: 'Implement user authentication.' The product manager asks if you can also include two-factor authentication (2FA) during the current sprint. You realize this is a significant addition. Which phrase best communicates that 2FA needs to be considered as a separate, subsequent effort?
Clearly stating that 2FA is 'a substantial expansion' highlights the impact on time and resources. This avoids simply saying no but focuses on the increased effort required, prompting a more informed discussion about priorities and scope. Options A & B are too eager, while option C implies immediate action without considering the implications.
What will I practise in "Scope Negotiation: Phrases for Managing Expectations"?
This module focuses on Phrasebook — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Phrasebook exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around phrasebook — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Phrasebook exercises?
See the Phrasebook hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.