What is the main aim of scope control?

To prevent scope creep and gold plating by managing changes to the scope baseline

To increase the scope as the customer asks

What is done in variance analysis during scope control?

Find the cause and degree of difference between baseline and actual scope

Compute expected time from three estimates

In scope change control, what comes right after a change request is evaluated for impact?

Decision by the Change Control Board (approve, reject or defer)

Updating the WBS dictionary only

After a scope change is approved, what must be done?

Update scope baseline, WBS, schedule and cost and inform stakeholders

Nothing, the old baselines remain

Year not given

Project scope control

Short answer

Scope control monitors scope baseline status and manages changes to prevent scope creep. Change requests undergo impact assessment, CCB decision, baseline updates, and communication. Variance analysis compares actual scope against the baseline, feeding corrective actions.

What do you mean by project scope control? Explain it including scope change control.

Project scope control (Control Scope) is the process of monitoring the status of the project and product scope and managing changes to the scope baseline. It ensures that all requested changes and recommended corrective actions are processed through the integrated change control process. Its main aim is to prevent scope creep (uncontrolled additions) and gold plating.

Inputs, tools, outputs

Inputs	Tools	Outputs
Project management plan (scope baseline, scope management plan, change management plan)	Variance analysis	Work performance information
Requirements documentation and traceability matrix		Change requests
Work performance data		Updates to plan, documents, OPA

Activities

Monitor work performance data against the scope baseline.
Perform variance analysis: find the cause and degree of difference between baseline and actual scope.
Decide on corrective or preventive action.
Verify that approved changes are implemented and baselines updated.
Maintain the requirements traceability matrix.

Scope change control

A formal system to handle any request that changes the scope.

Change request -> Evaluate impact (time, cost, risk, quality)
   -> Change control board -> Approve / reject / defer
   -> Update scope baseline, WBS, schedule, cost
   -> Communicate to stakeholders

Key elements:

A written change request form.
A change log tracking status.
An impact assessment of every change.
A Change Control Board (CCB) with authority.
Procedures for urgent changes.
Update of all baselines after approval.

Causes of scope change

Missing requirements, customer requests, market or legal changes, technical problems, errors.

Good practice

Have a clear scope statement and WBS, involve the customer, get sign-off on requirements, watch for gold plating and inform stakeholders.

Example: A client asks for a chat feature in a finished web portal. The manager assesses 3 weeks and Rs 2 lakh of extra effort; the CCB approves it only with a revised budget.

✓ Answer checked by Claude Opus 5.5 (high effort)

Project scope management · ICT Project Management, chapter 7
Integrated change control · ICT Project Management, chapter 7
Preliminary project scope statement · ICT Project Management, chapter 7
Project scope versus product scope · ICT Project Management, chapter 7
Monitor and control project work · ICT Project Management, chapter 7
Schedule development and control · ICT Project Management, chapter 8
Work scope control · Construction Management, chapter 7 · asked 3×
Scope of CM and project life cycle phases · Construction Management, chapter 1 · asked 4×
Scope of project engineering; dynamic environment · Project Engineering, chapter 1
Project control and control cycle steps · Project Engineering, chapter 4 · asked 3×

All ICT Project Management chapter 7 questions →