Project Scope, Quality

& Risk Management

Week 4 – MGMT182 Scope Control & Validate Scope
Content
• Scope Baseline
• Control Scope Process
• Scope Creep Vs. Gold Plating
• Validating Scope Process
Scope Baseline
A scope baseline is a document that establishes the
deliverables included in a project.

Items that do not appear in the scope baseline are

considered “outside of scope”.

Project Teams must complete a formal change

control process for new deliverables introduced
after approval of the baseline document.
 SCOPE BASELINE DETAILS
Project Name [Insert Project Name]
Project Description [Provide a brief description of the project and its objectives.]
[Include a detailed statement defining the project scope, including the boundaries, objectives,
Project Scope Statement
deliverables, and exclusions.]
Project Objectives [List the specific objectives or outcomes the project aims to achieve.]
Project Deliverables [Outline the tangible or intangible products, services, or results that the project will deliver.]
Project Boundaries [Define the limits or boundaries of the project, including what is included and excluded.]
Assumptions [List the assumptions made regarding the project scope, constraints, dependencies, or external factors.]
[Identify any limitations or restrictions that may impact the project scope, such as budget, resources,
Constraints
time, or regulations.]
[Document the key requirements and expectations of project stakeholders, including customers,
Stakeholder Requirements
sponsors, users, or regulatory bodies.]
Approval [Indicate the approval status and relevant stakeholders who have approved the scope baseline.]
[Record any revisions or updates made to the scope baseline, including the date and reason for the
Revision History
changes.]
Controlling Scope
Controlling the scope means
managing the changes to the
scope baseline.
There will inevitably be changes
to this, but it is important to
ensure that these changes do not
build upon each other
incrementally.
This is something referred to as
scope creep and always produces
unacceptable risks because the
combined effects of these
incremental changes are seldom
considered in total.
 FACTOR SCOPE CREEP GOLD PLATING
The uncontrolled expansion or addition of project scope without The practice of exceeding project requirements or adding extra
Definition
proper evaluation or approval. features that are not requested or necessary.
Unintentional and typically occurs due to poor scope management Intentional and often driven by the desire to exceed expectations
Nature
or lack of effective change control. or gain additional stakeholder satisfaction.
Impact on Project Negative Potentially Negative
Often exceeds client expectations but leads to project delays, cost May initially please the client but can result in project delays,
Client Expectations
overruns, and decreased quality. increased costs, and decreased overall value.
Changes are made without proper evaluation or approval, leading Changes are made without proper evaluation or approval, leading
Approval Process
to scope creep. to unnecessary additions or enhancements.
Poor communication and lack of stakeholder alignment contribute Lack of communication or miscommunication between the project
Communication
to scope creep. team and stakeholders can lead to gold plating.
Effective project management processes should be in place to
Scope creep requires strong scope management and change
Control prevent gold plating and ensure adherence to project
control processes to prevent its occurrence.
requirements.
Gold plating may lead to project success if the additional features
Scope creep negatively impacts project success, often resulting in or enhancements are valuable and align with stakeholder
Project Success
missed deadlines, budget overruns, and compromised quality. expectations. However, it can also lead to project failure if it
causes delays or exceeds project constraints.
Scope creep shifts the focus from project objectives and Gold plating focuses on exceeding requirements without
Focus
requirements towards uncontrolled expansion. considering project constraints or stakeholder needs.
Proper scope management, effective change control processes,
Clear project requirements, effective communication, and
Mitigation and regular stakeholder engagement can help mitigate scope
managing stakeholder expectations can help mitigate gold plating.
creep.

Scope Creep Vs. Gold Plating

 SCOPE VALIDATION confirms that the work being
considered matches the details in the WBS, project scope
plan and project plan. This is done using reviews or audits
and user trials.

It differs from QUALITY CONTROL because it is concerned

with the acceptance of the definition of the deliverables
while quality control is concerned with whether or not the
deliverables meet their quality requirements.
Validate Scope
Vs Control
Scope Control scope
Validate
is the process
scope means
of monitoring
the process of
the status of
formalizing
the project and
acceptance of
product scope
the completed
and managing
project
changes to the
deliverables.
scope baseline.
Validating Scope Process
This is the process of formalizing acceptance of the completed project
deliverables.

Project team performs the assigned activities to complete the project

scope and throughout the project, deliverables of the project are
completed.

Once the deliverables are completed, they must be reviewed by the

customer to check whether they meet the agreed requirements in the
beginning of the project.

A deliverable is accepted and mark as completed only if it is accepted by

the customer after checks.
Validating Scope Process

Changes or
QC Customer
Complete Perform QC corrective
Inspection Accept
Deliverables Inspection action (if
repeated* Deliverable
applicable)*
 Controlling Scope Process Vs. Validating Scope Process –
An Overview
FACTOR CONTROLLING SCOPE PROCESS VALIDATING SCOPE PROCESS
Monitor and manage changes to the project scope Formally accept completed deliverables and ensure they
Purpose
throughout the project lifecycle. meet the defined acceptance criteria.
Prevent scope creep and ensure project stays within Confirm that deliverables meet stakeholder expectations
Objective
defined boundaries. and project requirements.
1. Reviewing change requests and assessing their
1. Reviewing completed deliverables against acceptance
impact on scope.
criteria.
2. Evaluating proposed changes through change
Activities 2. Engaging stakeholders to validate and provide
control processes.
feedback on deliverables.
3. Updating project documentation and
3. Obtaining formal acceptance of deliverables.
communicating approved changes.
Performed upon completion of deliverables or project
Timing Ongoing throughout the project lifecycle.
milestones.
Managing changes and ensuring adherence to the Ensuring deliverables meet quality standards and
Focus
approved scope baseline. stakeholder expectations.
Acceptance forms, sign-off sheets, validated scope
Change requests, change log, updated project scope
Documentation documentation, and communication of accepted
statement, and revised project documentation.
deliverables.