Scope Terms
Tools & Techniques
Processes
Scope Documents
Common Pitfalls
100

What is project scope?

A. A list of team members
B. The boundaries of the budget
C. All work required to deliver the project
D. Only the deliverables  

Answer: C

C. All work required to deliver the project

100

What is the method to gather detailed stakeholder input

A. Delphi technique
B. Interviews
C. Monte Carlo simulation
D. Fishbone diagram

100

Which is the first process in Scope Management?

A. Collect Requirements
B. Define Scope
C. Plan Scope Management
D. Create WBS  

Answer: C 

C. Plan Scope Management

100

Which plan outlines how project scope will be defined and controlled? 

A. Quality Management Plan
B. Scope Management Plan
C. Stakeholder Engagement Plan
D. Communications Plan

Answer: B 

Scope Management Plan

100

Failing to involve stakeholders early can result in: 

A. Scope freeze
B. Missed requirements
C. More funding
D. Fast approvals

Answer: B 

Missed requirements

200

Adding features not included in the scope is called:
A. Scope creep
B. Risk mitigation
C. Rolling wave planning
D. Gold plating

Answer: D

D. Gold plating

200

Name a group technique for requirement collection.

Answer: Brainstorming, workshops, focus groups.

200

What does Collect Requirements aim to do?

Answer: Identify and document stakeholder needs and expectations.

200

What does the Scope Statement include?

Answer: Deliverables, assumptions, constraints, and boundaries of the project.

200

Allowing scope changes without control leads to: 

A. Risk analysis
B. Gold plating
C. Scope creep
D. Stakeholder alignment

Answer: C 

Scope creep

300

What is a deliverable? (Open-ended)

Answer: A unique product, service, or result created by the project.

300

What visual tool helps define high-level deliverables?

A. Flowchart
B. Mind Map
C. Risk Matrix
D. Pareto Chart  

Answer: B 

B. Mind Map

300

Which process creates the detailed product description? 

A. Define Scope
B. Develop Project Charter
C. Create WBS
D. Control Scope

Answer: A 

Define Scope

300

The graphical breakdown of project work is known as: 

A. WBS
B. Gantt Chart
C. Project Schedule
D. RACI Matrix

Answer: A 

WBS


300

What’s the risk of not having a clear WBS?

Answer: Misunderstandings, rework, missed deliverables.


400

The document that describes what's included and excluded from the project:

A. Requirements Traceability Matrix
B. WBS
C. Scope Statement
D. Project Charter  

✅ Answer: C 

Scope Statement

400

Which technique helps prioritize requirements?

A. Delphi Technique
B. SWOT Analysis
C. MoSCoW
D. Earned Value  

Answer: C 

C. MoSCoW

400

The process of breaking deliverables into smaller pieces: 

A. Validate Scope
B. Monitor and Control
C. Create WBS
D. Collect Requirements

Answer: C 

Create WBS

400

What provides detailed descriptions of WBS components? 

A. WBS Dictionary
B. Risk Register
C. Change Log
D. Issue Log

Answer: A 

WBS Dictionary

400

Assuming undocumented requirements can result in: 

A. Change requests
B. Clarity
C. Project success
D. Misunderstandings

Answer: D 

Misunderstandings

500

What is a WBS used for? (Open-ended)

Answer: Breaking down deliverables into smaller, manageable components.

500

What is the Delphi technique?

Answer: An anonymous method of reaching consensus among experts.

500

What is the purpose of Validate Scope?

Answer: To formally accept completed project deliverables.

500

What is the Requirements Traceability Matrix used for?

Answer: To link requirements to deliverables and ensure each one is fulfilled.

500

What happens if deliverables aren’t validated regularly?

Answer: They may be rejected or require rework.

M
e
n
u