Solution Constraints and Scope

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. Is a limited budget an example of a project constraint?

A False

B True

2. Does scope define what is included and excluded from a solution?

A True

B False

3. Is scope creep generally helpful or harmful to a project?

A Helpful

B Harmful

4. Should constraints and scope be considered during planning?

A Yes

B No

5. Can limited team skills act as a project constraint?

A Yes

B No

Match the Pairs

Draw a line connecting each item on the left to its match on the right.

Left column		Right column
1A tight project deadline that limits development time		AConstraints like budget must be respected throughout a project
2A written statement listing included and excluded features		BScope
3A restriction such as limited budget or available technology		CConstraint
4The boundary defining what a solution will and won't include		DConstraint
5The team added extra features nobody had agreed on partway through		EScope
6The project ignored its budget constraint and kept spending freely		FThis is scope creep, which can push a project over time and budget

Definitions

Constraints and scope

Fill in the Blanks

Complete each line of code by filling in the missing parts.

1. ____ 2. Budget 3. Technology

1. Time 2. ______ 3. Technology

1. Time 2. Budget 3. __________

Scope defines what is included and ________

A project's ___________ limit what it can achieve

Spot the Error

Shade in the letter of the line that contains an error.

Question 1

A A constraint is a limit or restriction on a project.

B Time and budget are common constraints.

C Constraints can never affect what a solution looks like.

D Technology available is also a common constraint.

Question 2

A Scope defines what a solution will include.

B Scope must be agreed on before development begins.

C It also defines what a solution will exclude.

D Scope has no connection to project constraints.

Question 3

A Constraints are always ignored once a project starts.

B A tight deadline is an example of a time constraint.

C A limited budget is an example of a cost constraint.

D Constraints must be considered throughout the project.

Question 4

A Scope creep happens when extra features are added unplanned.

B Scope creep is always beneficial for a project.

C It can cause a project to go over budget or time.

D Managing scope helps keep a project on track.

Question 5

A Defining scope early helps avoid confusion later.

B Scope should be defined only after the project ends.

C It clarifies what features will and won't be built.

D A clear scope reduces the risk of miscommunication.

E Team members should agree on scope from the start.

Answer Key

Solution Constraints and Scope

Section A: Quick Questions

B — True

A — True

B — Harmful

A — Yes

Section B: Match the Pairs

A tight project deadline that limits development time → Constraint

A written statement listing included and excluded features → Scope

A restriction such as limited budget or available technology → Constraint

The boundary defining what a solution will and won't include → Scope

The team added extra features nobody had agreed on partway through → This is scope creep, which can push a project over time and budget

The project ignored its budget constraint and kept spending freely → Constraints like budget must be respected throughout a project

Section C: Definitions

Constraints and scope — The limits on a project (constraints, like time or budget) and the boundaries of what the solution will and won't include (scope)

Section D: Fill in the Blanks

1. Time
2. Budget
3. Technology

1. Time
2. Budget
3. Technology

1. Time
2. Budget
3. Technology

Scope defines what is included and excluded

A project's constraints
 limit what it can achieve

Section E: Spot the Error

C — Constraints, such as budget or technology, often directly affect what a solution can look like or include.

D — Scope is closely connected to constraints, since limits like time and budget often shape what fits within scope.

A — Constraints are considered throughout the project, not ignored once it starts.

B — Scope creep is usually harmful, not beneficial, as it can push a project over budget or past its deadline.

B — Scope should be defined before or early in a project, not only after it ends.