Learn vocabulary for managing and communicating scope creep: change requests, professional pushback, and additional work language.
0 / 14 completed
1 / 14
What is 'scope creep' in freelance project vocabulary?
Scope creep is one of the most common freelance challenges: 'Can you just also add a blog section?', 'The client wants us to support mobile now too', 'We need three more revision rounds.' Each addition seems small but collectively they can double the work without increasing compensation. Clear scope definition and a change request process prevent it.
2 / 14
How do you professionally communicate a change request?
Change request communication: never say no to the work (say no to the scope). 'That sounds like a great addition! It's beyond our current scope, so I'd handle it as a change order. I estimate it's about [X hours / $Y]. I can send a formal change request for your approval if you'd like to proceed.' This keeps the relationship positive while protecting your time and compensation.
3 / 14
What is a 'change order' or 'change request' in freelance vocabulary?
A change order formalises scope additions: it describes the new work in detail, the additional fee, any timeline extension, and requires client signature (or written approval) before work begins. This protects you legally and ensures the client explicitly agrees to the additional cost before you do the work.
4 / 14
What is 'revision limit' language in a freelance contract or proposal?
Revision limit language: 'This proposal includes two rounds of design revisions. Additional revision rounds are billed at $[X]/hour.' This prevents endless revision cycles. A revision 'round' should be defined (one consolidated set of changes per round, not multiple separate revision requests that count as one round).
5 / 14
What is 'out of scope' and how do you use it professionally?
Out of scope is a neutral, professional phrase: 'That would fall outside our current scope — I can absolutely do it, but as a change request rather than under our existing agreement. Happy to put together a quick quote if you'd like to proceed.' It redirects, not refuses. The phrase signals a commercial, not personal, distinction.
6 / 14
Reviewer: 'Okay, the new authentication flow is solid. But can we also add support for two-factor authentication? It's just a small change and will significantly improve security.'
Which of the following responses best addresses this request in a professional code review context, acknowledging potential scope creep?
The correct answer highlights the need for clarification regarding the scope implications. Simply approving or rejecting without understanding the potential consequences is a mistake. The question prompts further discussion about complexity, user flow impacts, and time estimations – vital considerations when evaluating whether a change fits within the current project's boundaries. Option A is too permissive; B ignores the core issue of scope; C is overly dismissive without investigation.
7 / 14
Reviewer: 'Okay, the new authentication flow is solid. But can we also add support for two-factor authentication? It's just a small change and will significantly improve security.'
Which of the following responses best addresses this request in a professional code review context, acknowledging potential scope creep?
The correct answer highlights the need for clarification regarding the scope implications. Simply approving or rejecting without understanding the potential consequences is a mistake. The question prompts further discussion about complexity, user flow impacts, and time estimations – vital considerations when evaluating whether a change fits within the current project's boundaries. Option A is too permissive; B ignores the core issue of scope; C is overly dismissive without investigation.
8 / 14
Reviewer: 'Okay, the new authentication flow is solid. But can we also add support for two-factor authentication? It's just a small change and will significantly improve security.'
Which of the following responses best addresses this request in a professional code review context, acknowledging potential scope creep?
The correct answer highlights the need for clarification regarding the scope implications. Simply approving or rejecting without understanding the potential consequences is a mistake. The question prompts further discussion about complexity, user flow impacts, and time estimations – vital considerations when evaluating whether a change fits within the current project's boundaries. Option A is too permissive; B ignores the core issue of scope; C is overly dismissive without investigation.
9 / 14
Reviewer: 'Okay, the new authentication flow is solid. But can we also add support for two-factor authentication? It's just a small change and will significantly improve security.'
Which of the following responses best addresses this request in a professional code review context, acknowledging potential scope creep?
The correct answer highlights the need for clarification regarding the scope implications. Simply approving or rejecting without understanding the potential consequences is a mistake. The question prompts further discussion about complexity, user flow impacts, and time estimations – vital considerations when evaluating whether a change fits within the current project's boundaries. Option A is too permissive; B ignores the core issue of scope; C is overly dismissive without investigation.
10 / 14
You're reviewing a pull request for a new user authentication module. The reviewer comments: 'Excellent work! However, to enhance security, could we integrate two-factor authentication (2FA) as well? It's a relatively small addition.' Which response best addresses the reviewer's suggestion?
This scenario tests understanding of scope creep. Option A politely declines the change request while maintaining boundaries. Options B & D are overly enthusiastic and potentially disruptive. Option C acknowledges the suggestion but highlights potential consequences – a key communication skill.
11 / 14
Sarah, a senior developer, sends a Slack message to her team: 'Just finished implementing the API endpoint for user profiles. It's fully tested and ready for integration.' Later, another developer suggests adding rate limiting. What is the *most* appropriate response from Sarah?
This assesses communication skills when a new requirement arises. Option A shuts down discussion. Option B invites collaboration and further discussion - demonstrating openness to change while staying within the original scope. Options C & D are dismissive or overly prescriptive.
12 / 14
You've written a PR description for a bug fix that added logging to a critical service. The description reads: 'Fixed a bug where the service was crashing under heavy load. Added detailed logging for debugging.' A reviewer comments: 'Could we also include metrics on error rates?' How should you respond?
This focuses on managing expectations and scope. Option A prioritizes the original goal. Option B shows willingness to consider further improvements – a key aspect of proactive communication. Options C & D are either overly restrictive or dismissive.
13 / 14
"The project is currently delivering features A, B and C. Adding feature D would require a significant refactoring of the existing codebase and could introduce new risks." Which of the following best captures this statement in developer vocabulary?
This tests the ability to understand and articulate a limitation. Option A suggests adding features regardless of impact. Option B is too blunt. Option C accurately reflects the need for careful consideration before proceeding – demonstrating an understanding of potential risks.
14 / 14
During a standup meeting, Mark says: 'I've finished implementing user authentication. It's working but needs some basic error handling.' David replies: 'Great! Can we also add support for password reset flows? It will improve usability.' What is David doing?
This explores how suggestions are framed within a project context. Option A is correct – suggesting an incremental improvement aligned with the existing feature. Options B & C misinterpret David's comment. Option D is unnecessarily negative.
What does the "Scope Creep — Communication and Vocabulary" exercise cover?
Learn vocabulary for managing and communicating scope creep: change requests, professional pushback, and additional work language.
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 "Scope Creep — Communication and Vocabulary"?
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 Freelance Client exercises?
Browse the full Freelance Client 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.