Factor affecting project plans: scope creep

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. Which statement best describes scope creep?

A The team finishes all planned features ahead of schedule

B Features keep being added beyond the original scope without control

2. A client asks for a new login screen, a chat tool and a dark mode after development has started. None of these were in the original plan. What is this an example of?

A Beta testing of the solution

B Scope creep from added features

3. What is a likely effect of scope creep on a project plan?

A Extra time and cost are needed

B The project becomes cheaper and quicker

4. Which approach helps control scope creep?

A Record changes and get them approved before adding them

B Add every new request straight away to keep the client happy

5. A student's app plan lists 3 features. Halfway through, the student adds 5 more without changing the plan or deadline. What is the likely result?

A The project falls behind schedule

B The Gantt chart updates itself and stays accurate

Match the Pairs

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

Left column		Right column
1scope creep		AA record used to control scope by formally approving or rejecting each new feature before work starts
2change request form		BThe feature is added without assessing its impact or updating the scope, time frame and budget, which is scope creep.
3Adding a feature that was not in the original scope increases the time and cost of the project		CThe uncontrolled growth of a project's features beyond the original scope
4Controlling scope means checking each new feature request against the original scope before accepting it		DExtra features were added without extending the deadline or budget, so the plan is unrealistic and the project will run late.
5Client asks for a new feature mid-project. Developer says 'Sure!' and adds it without updating the plan.		ETask: Add dark mode (not in scope) \| Planned: 10 days \| Actual: 14 days \| Extra cost: $1,200
6Project plan: scope fixed, no change process. 5 extra features added over 6 weeks. Deadline unchanged.		Fif request not in original_scope: log_change_request(request)

Definitions

scope creep

Fill in the Blanks

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

features = ["login", "search"] features.______("chat") print(features)

planned = 40 extra = 3 * 8 total = planned _ extra

budget = 5000 newcost = 5000 + 1200 over = newcost _ budget

approved = False if ________: print("Add chat feature")

features = ["login", "search", "chat"] added = ___(features) - 2 print(added)

Spot the Error

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

Question 1

A orig = 5

B added = 3

C total = orig + added

D extra_days = orig * 2

E print(total, extra_days)

Question 2

A def add(scope, new)

B scope.append(new)

C return scope

D features = ['login']

E print(add(features, 'chat'))

Question 3

A request = 'dark mode

B approved = False

C if approved:

D print('Add', request)

E else:

F print('Rejected')

Question 4

A features = ['login', 'chat']

B added = 0

C for f in feature:

D added += 1

E print(added)

Question 5

A budget = 8000

B cost = 9500

C if cost = budget:

D print('Over budget')

E else:

F print('On budget')

Answer Key

Factor affecting project plans: scope creep

Section A: Quick Questions

B — Features keep being added beyond the original scope without control

B — Scope creep from added features

A — Extra time and cost are needed

A — Record changes and get them approved before adding them

A — The project falls behind schedule

Section B: Match the Pairs

scope creep → The uncontrolled growth of a project's features beyond the original scope

change request form → A record used to control scope by formally approving or rejecting each new feature before work starts

Adding a feature that was not in the original scope increases the time and cost of the project → Task: Add dark mode (not in scope) | Planned: 10 days | Actual: 14 days | Extra cost: $1,200

Controlling scope means checking each new feature request against the original scope before accepting it → if request not in original_scope: log_change_request(request)

Client asks for a new feature mid-project. Developer says 'Sure!' and adds it without updating the plan. → The feature is added without assessing its impact or updating the scope, time frame and budget, which is scope creep.

Project plan: scope fixed, no change process. 5 extra features added over 6 weeks. Deadline unchanged. → Extra features were added without extending the deadline or budget, so the plan is unrealistic and the project will run late.

Section C: Definitions

scope creep — The uncontrolled growth of a project's features beyond the original scope, which adds extra time and cost unless changes are controlled.

Section D: Fill in the Blanks

features = ["login", "search"]
features.append("chat")
print(features)

planned = 40
extra = 3 * 8
total = planned + extra

budget = 5000
newcost = 5000 + 1200
over = newcost > budget

approved = False
if approved:
    print("Add chat feature")

features = ["login", "search", "chat"]
added = len(features) - 2
print(added)

Section E: Spot the Error

D — Scope creep adds extra time because of the added features. The extra days must be calculated from added, not from the original features. It should be extra_days = added * 2.

A — A function definition must end with a colon. Without it Python raises a SyntaxError. It should be def add(scope, new):

A — The string is missing its closing quote, which causes a SyntaxError. It should be request = 'dark mode'

C — The list is called features, not feature, so Python raises a NameError. The loop should be for f in features:

C — A single = assigns a value and is not allowed in an if condition. To compare the cost with the budget, use a comparison operator: if cost > budget: