Practice vocabulary for managing scope in freelance projects including change orders, feature creep, SOW references, and re-estimation conversations.
0 / 14 completed
1 / 14
When a client requests work not covered in the original agreement, a professional freelancer responds by saying _____.
Referring to scope and raising a change order is the professional response — it protects the freelancer's time while keeping communication transparent and the relationship intact.
2 / 14
A 'change order' in a freelance context is a formal document that _____.
A change order formally documents the new or modified work, its cost, and timeline — it becomes an amendment to the original contract and must be agreed before work begins.
3 / 14
'Feature creep' describes a situation where _____.
Feature creep is the gradual, uncontrolled expansion of scope through small additions — each request seems minor, but collectively they can add many unplanned hours to a project.
4 / 14
When a project has expanded significantly beyond original estimates, a freelancer should say they need to _____.
Pausing to re-estimate is the professional approach — it surfaces the scope change formally, gives the client a choice, and prevents the freelancer from absorbing unplanned work unpaid.
5 / 14
The SOW (Statement of Work) in a freelance contract defines _____.
The Statement of Work is the contractual reference document that defines exactly what will be delivered — it is the baseline against which scope changes are measured.
6 / 14
Reviewer: "I'm seeing this function called from multiple places within the `UserAuthentication` module. While it's not *wrong*, it feels like a potential scope issue. We might want to consider moving some of these calls into a dedicated authentication service."
The reviewer isn't just pointing out a technical problem; they're raising a concern about long-term maintainability. The key vocabulary here is 'scope management,' referring to how code dependencies are organized and the potential for future issues when functionality is spread across multiple modules. Options A and D miss this point, while B suggests immediate action without understanding the underlying reason, and C invites a productive discussion to understand the scope issue fully.
7 / 14
Reviewer: "I'm seeing this function called from multiple places within the `UserAuthentication` module. While it's not *wrong*, it feels like a potential scope issue. We might want to consider moving some of these calls into a dedicated authentication service."
The reviewer isn't just pointing out a technical problem; they're raising a concern about long-term maintainability. The key vocabulary here is 'scope management,' referring to how code dependencies are organized and the potential for future issues when functionality is spread across multiple modules. Options A and D miss this point, while B suggests immediate action without understanding the underlying reason, and C invites a productive discussion to understand the scope issue fully.
8 / 14
Reviewer: "I'm seeing this function called from multiple places within the `UserAuthentication` module. While it's not *wrong*, it feels like a potential scope issue. We might want to consider moving some of these calls into a dedicated authentication service."
The reviewer isn't just pointing out a technical problem; they're raising a concern about long-term maintainability. The key vocabulary here is 'scope management,' referring to how code dependencies are organized and the potential for future issues when functionality is spread across multiple modules. Options A and D miss this point, while B suggests immediate action without understanding the underlying reason, and C invites a productive discussion to understand the scope issue fully.
9 / 14
Reviewer: "I'm seeing this function called from multiple places within the `UserAuthentication` module. While it's not *wrong*, it feels like a potential scope issue. We might want to consider moving some of these calls into a dedicated authentication service."
The reviewer isn't just pointing out a technical problem; they're raising a concern about long-term maintainability. The key vocabulary here is 'scope management,' referring to how code dependencies are organized and the potential for future issues when functionality is spread across multiple modules. Options A and D miss this point, while B suggests immediate action without understanding the underlying reason, and C invites a productive discussion to understand the scope issue fully.
10 / 14
Alice (Lead Developer) sends this Slack message to the team after discovering a new feature request during sprint planning:
"Okay, so we've agreed on core user authentication, but now Mark wants to add two-factor auth? That's outside the original scope. We need to discuss if that impacts our timeline and budget."
This scenario tests understanding of scope boundaries in a collaborative setting. Alice's response is key because it directly addresses the deviation from the agreed-upon scope. It's important to clearly state what *is* included and what isn't, avoiding vague statements that could lead to confusion or scope creep. Option A is too aggressive, option C is unhelpful, and option D misses the core point.
11 / 14
During a code review, you notice a function `calculateTax()` is used in several unrelated modules. The reviewer comments: 'This seems like it's starting to broaden the scope of this component significantly.' What does this comment primarily refer to?
A. A potential performance bottleneck.
B. An unnecessary dependency on external libraries.
C. Scope pollution – the function's use is expanding beyond its intended purpose, potentially leading to maintenance issues and increased complexity.
D. The need for unit tests covering all possible scenarios.
This question directly tests the understanding of 'scope pollution.' The reviewer identifies that the function's use is growing beyond its original intended purpose. This expansion can lead to maintenance headaches and increased complexity if not managed carefully. Options A, C, and D represent other potential code review concerns but don't capture the specific meaning of scope pollution.
12 / 14
A project manager is explaining a change order to a developer after the initial SOW. The change order outlines adding a new reporting dashboard. What does an 'SOW' (Statement of Work) primarily define?
A. The total budget allocated for the entire project.
B. The specific technical tasks and deliverables agreed upon between the client and the developer, including scope, timelines, and payment terms.
C. A formal legal document outlining liabilities and warranties.
D. The daily stand-up meeting agenda.
The SOW (Statement of Work) is fundamental to managing scope. It's a crucial document that clearly outlines the agreed-upon deliverables and terms of engagement. Without a well-defined SOW, misunderstandings and disagreements about what needs to be done are far more likely. Options A, C, and D have different meanings.
13 / 14
During a sprint retrospective, the team discusses a project that went significantly over budget and timeline. A developer says: 'We should have recognized early on when adding this new API integration was becoming a major scope shift and proactively discussed it with the client.' What is this statement primarily highlighting?
A. The importance of aggressive deadlines.
B. The need for frequent code commits.
C. Effective scope management – recognizing and addressing changes to the project's boundaries promptly to prevent uncontrolled expansion.
D. The value of using automated testing frameworks.
This question focuses on the proactive aspect of scope management. The developer's statement emphasizes the importance of recognizing and addressing changes in scope *before* they escalate into major issues. This highlights a crucial skill for developers – anticipating potential problems and engaging with stakeholders to manage expectations effectively. Options A, B, and D are irrelevant.
14 / 14
A developer is writing a PR description for a change that refactors a complex module. They want to clearly communicate the scope of the changes. What's the most effective way to phrase this?
A. 'Refactored some code.'
B. 'Fixed bugs and improved performance.'
C. 'This PR addresses the original requirements for User Authentication, focusing on modularity and reducing dependencies within that module – any changes outside of this scope are not part of this release.'
D. 'Cleaned up some messy code'
The PR description should explicitly define the boundaries of the change. Option C clearly states the scope – focusing on modularity and reducing dependencies within the `User Authentication` module. This prevents ambiguity and manages expectations about what's included in this release. Options A, B, and D are too vague.
What does the "Scope Management Vocabulary" exercise cover?
Practice vocabulary for managing scope in freelance projects including change orders, feature creep, SOW references, and re-estimation conversations.
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 Management 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.