Project Scope Management
Open in the Padhaiko app6.1 Develop preliminary project scope statement
Preliminary and Detailed Project Scope Statement
Develop Preliminary Project Scope Statement is the process of defining a high-level description of the project's deliverables, boundaries, acceptance criteria, constraints, and assumptions based on the Project Charter and stakeholder needs.
As planning progresses, this preliminary statement is refined via progressive elaboration into the detailed Project Scope Statement, which becomes part of the Scope Baseline.
Key Contents of a Project Scope Statement
- Project & Product Objectives: Measurable technical and business targets.
- Product Scope Description: Functional and non-functional characteristics of the ICT system.
- Project Deliverables: Tangible outputs (software builds, API documentation, server setup, training manuals) and intermediate project management artifacts.
- Project Boundaries (Exclusions): Explicitly lists what is out of scope to prevent misunderstandings (e.g., "Legacy data older than 5 years will NOT be migrated in Phase 1").
- Product Acceptance Criteria: Specific, testable conditions required before the customer signs off (e.g., zero critical bugs, pass rate on UAT test suite).
- Constraints & Assumptions: Fixed limits (budget cap, regulatory compliance) and factors assumed true for planning (e.g., client provides test data by Week 3).
- Initial Risks, Milestone Schedule & Order-of-Magnitude Cost Estimate.
6.2 Create work break down structure
Work Breakdown Structure (WBS)
A Work Breakdown Structure (WBS) is a deliverable-oriented hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
Each descending level of the WBS represents an increasingly detailed definition of the project work, ending at the Work Package level.
Fundamental WBS Principles and Rules
- The Rule: The WBS must capture of the work defined by the project scope—including project management, documentation, and testing deliverables—and no out-of-scope work. At every level, the sum of child elements must equal of their parent element.
- Deliverable-Oriented (Nouns, Not Verbs): WBS nodes represent tangible outcomes ("1.2 User Authentication Module"), whereas individual tasks/actions ("Write login controller") are defined later during Activity Definition (Chapter 7).
- Work Package (Lowest Level): The bottom-most level of any WBS branch where cost and duration can be reliably estimated and managed. A common ICT heuristic is the Hour Rule: each work package should require between and of effort (roughly 1 day to 2 weeks).
- WBS Numbering (Code of Accounts): Unique hierarchical codes (
1.0,1.1,1.1.1) link every work package to accounting, scheduling, and responsibility matrices. - Control Accounts & Planning Packages: A Control Account is a management control point where scope, budget, actual cost, and schedule are integrated and compared for Earned Value Management.
- WBS Dictionary: A companion document describing each WBS component in detail—work package ID, scope description, responsible owner, acceptance criteria, resources, and cost estimate.
Approaches to Structuring a WBS
| WBS Approach | Top-Level (Level 1) Grouping | When Preferred |
|---|---|---|
| By Deliverable / Product Component | 1.1 Frontend Portal, 1.2 Backend APIs, 1.3 Database, 1.4 Security & Testing, 1.5 Project Management | Modular software/hardware builds with parallel teams |
| By Project Phase (SDLC) | 1.1 Initiation, 1.2 Requirements, 1.3 Design, 1.4 Construction, 1.5 Testing & Rollout | Sequential Waterfall or phase-gate enterprise rollouts |
| By Subsystem / Organization | 1.1 Finance Module, 1.2 HR Module, 1.3 Inventory Module | Large ERP integrations across business units |
1.0 Campus Web Portal Project
|-- 1.1 Project Management
| |-- 1.1.1 Project Charter & PMP
| +-- 1.1.2 Status Tracking & Closure Reports
|-- 1.2 Web Application
| |-- 1.2.1 UI/UX Wireframes & Frontend
| |-- 1.2.2 Authentication & Role Access API
| +-- 1.2.3 Course & Grade Database Schema
|-- 1.3 Quality & Testing
| |-- 1.3.1 Automated Unit & Integration Tests
| +-- 1.3.2 User Acceptance Testing (UAT)
+-- 1.4 Deployment & Training
|-- 1.4.1 Cloud Provisioning & Cutover
+-- 1.4.2 Admin Runbook & User Training6.3 Scope verification
Scope Verification (Validate Scope)
Scope Verification (also called Validate Scope) is the Monitoring & Controlling process of formalizing acceptance of the completed project deliverables by the customer or project sponsor.
Inputs, Tools, and Outputs
- Inputs: Project Management Plan (Scope Baseline), Requirements Documentation, Requirements Traceability Matrix (RTM), and Verified Deliverables (deliverables that have already passed internal Quality Control testing).
- Tools & Techniques: Inspection (also called reviews, product reviews, audits, and walkthroughs; in software, User Acceptance Testing / Sprint Demo).
- Outputs: Accepted Deliverables (formally signed off), Work Performance Information, and Change Requests (if any deliverable is rejected or incomplete).
| Aspect | Quality Control (Control Quality) | Scope Verification (Validate Scope) |
|---|---|---|
| Primary Goal | Verify correctness—does the deliverable meet technical quality standards and have zero defects? | Verify acceptance—does the customer/sponsor formally accept the deliverable? |
| Who Performs It? | Internal QA / testing team | Customer, Product Owner, or Project Sponsor (with PM) |
| Typical Sequence | Performed first (usually before Scope Verification) | Performed after Quality Control produces Verified Deliverables |
| ICT Example | Running automated unit tests, penetration tests, and bug checks | Conducting UAT demo and obtaining client sign-off certificate |
6.4 Scope control
Scope Control
Scope Control is the Monitoring & Controlling process of monitoring the status of the project and product scope and managing changes to the Scope Baseline.
Preventing Scope Creep and Gold Plating
Two common failure modes threaten ICT projects during execution:
| Phenomenon | Definition | ICT Example | Prevention Mechanism |
|---|---|---|---|
| Scope Creep | Uncontrolled expansion of product or project scope without corresponding adjustments to time, cost, and resources | Client keeps asking for "one extra analytics export" via informal emails | Formal Change Control Board (CCB), strict Scope Exclusions list, Requirements Traceability Matrix |
| Gold Plating | Project team members add unrequested extra features believing it will delight the customer | A developer spends unbudgeted days building a dark-mode animation nobody asked for | Enforcing the rule ("only the work required"), code reviews, and Change Log discipline |
Scope Control Mechanism
- Variance Analysis: Comparing actual work completed against the Scope Baseline (and Requirements Traceability Matrix) to measure scope deviation and determine whether corrective or preventive action is needed.
- Integrated Change Control Linkage: Every legitimate scope change must flow through Perform Integrated Change Control (Chapter 5) so that schedule, budget, and risk baselines are updated alongside the WBS and WBS Dictionary.
Worked Out Examples
6.1
Building a WBS and Verifying the Rule (Cost Roll-Up): An ICT vendor wins a fixed-price contract of to build a Library Management System (1.0). The team decomposes the scope into four Level-1 deliverables and their Level-2 work packages:
1.1 Project Management:1.1.1 Planning & Tracking(),1.1.2 Client Reporting & Closure()1.2 Core Software Modules:1.2.1 Catalog & Search UI(),1.2.2 Borrowing & Fine Engine(),1.2.3 Database & Auth API()1.3 Testing & Verification:1.3.1 System & Load Testing(),1.3.2 UAT Support()1.4 Deployment & Training:1.4.1 Server Cutover & Training()
- Compute the rolled-up budget for each Level-1 deliverable (
1.1through1.4) and verify that the WBS satisfies the Rule against the contract. - During execution, a developer plans to add an unrequested mobile SMS alert feature costing "as a goodwill gesture." Identify this risk and state what the PM should do.
Rolling up work package costs to Level-1 deliverables:
Summing all Level-1 nodes:
The roll-up matches the baseline exactly, confirming scope coverage (including project management and testing).
Handling the unrequested SMS alert feature: Adding an unrequested feature not in the WBS is Gold Plating—it consumes ( of total budget), adds untested maintenance surface, and violates "only the work required." The PM must instruct the developer not to build it unless the client submits a formal Change Request that adjusts budget and schedule through Integrated Change Control.
- Level-1 roll-ups:
1.1= ,1.2= ,1.3= ,1.4= ; total ( rule satisfied). - The unrequested SMS feature is Gold Plating and must be stopped unless formally approved via a Change Request.
6.2
Distinguishing Quality Control, Scope Verification, and Scope Control in Practice: At the end of Phase 2 of a municipal tax-collection web portal:
- Situation A: The internal QA engineer runs automated security scans and finds 4 SQL-injection bugs in the tax-payment form.
- Situation B: After bugs are fixed, the municipal IT director inspects the live staging portal against the Requirements Traceability Matrix and signs the Phase 2 acceptance form.
- Situation C: Two days later, a ward clerk emails a developer asking to add a new Nepali-calendar PDF export button not listed in the WBS.
Identify which Scope/Quality process applies to each situation and justify your answer.
Classifying each situation:
- Situation A Quality Control: Internal QA checks technical correctness and defect compliance before presenting deliverables to the client.
- Situation B Scope Verification (Validate Scope): Once Quality Control delivers Verified Deliverables, the customer/sponsor formally inspects and signs off Accepted Deliverables.
- Situation C Scope Control (with Integrated Change Control): An informal request outside the Scope Baseline threatens Scope Creep. The PM must log a formal Change Request, analyze cost/schedule impact, and route it to the CCB rather than letting the developer code it directly.
- Situation A: Quality Control (internal defect verification).
- Situation B: Scope Verification (formal client acceptance of verified deliverables).
- Situation C: Scope Control (preventing Scope Creep by routing the new feature through formal Change Control).
Exercises
Practice Exercises — Project Scope Management
Differentiate between Product Scope and Project Scope, and list the key sections of a Project Scope Statement.
Product Scope vs. Project Scope:
- Product Scope describes the features, functions, and technical characteristics of the delivered product or service, measured against product requirements.
- Project Scope describes all the work that must be performed to deliver that product, measured against the Project Management Plan (Scope Baseline).
Key contents of a Project Scope Statement: Product scope description, project deliverables, explicit boundaries/exclusions (what is out of scope), formal acceptance criteria, constraints, and assumptions.
Product scope defines what features the system has (measured against requirements), while project scope defines all work needed to deliver it (measured against the PMP). A Project Scope Statement captures product description, deliverables, explicit exclusions, acceptance criteria, constraints, and assumptions.
Define a Work Breakdown Structure (WBS). Explain the Rule, the Hour Rule, and the purpose of the WBS Dictionary.
WBS and core rules: A WBS is a deliverable-oriented hierarchical decomposition of total project scope down to manageable Work Packages.
- Rule: The WBS includes of in-scope project work (including management and QA) and zero out-of-scope work; every parent equals the sum of its children.
- Hour Rule: A practical guideline recommending work packages be sized between and effort hours so they are neither micro-managed nor too coarse to track.
- WBS Dictionary: Companion reference detailing each WBS node's scope statement, owner, acceptance criteria, resources, and cost estimate.
A WBS hierarchically decomposes all project deliverables into work packages. The rule ensures complete, non-overlapping scope coverage; the rule sizes work packages between and hours; and the WBS Dictionary documents detailed specifications and acceptance criteria for every WBS item.
Compare Quality Control and Scope Verification. Which one is normally performed first, and why?
Comparison and ordering:
- Quality Control is performed by the internal project/QA team to verify that deliverables meet technical specifications and are free of defects (correctness), producing Verified Deliverables.
- Scope Verification is performed with the customer or sponsor to inspect verified deliverables and obtain formal written sign-off (acceptance), producing Accepted Deliverables.
- Order: Quality Control is normally performed first so defective work is caught and repaired internally before requesting formal client acceptance.
Quality Control checks internal technical correctness and runs first to produce Verified Deliverables; Scope Verification follows with the customer/sponsor inspecting those verified deliverables for formal acceptance.
Explain Scope Creep and Gold Plating with one ICT example of each, and describe two controls used to prevent them during Scope Control.
Scope Creep vs. Gold Plating:
- Scope Creep: Unapproved expansion of scope without adjusting time, cost, or resources (e.g., a client persuading a developer over chat to add an unbudgeted reporting dashboard).
- Gold Plating: Team members adding unrequested extra features thinking it adds value (e.g., building custom 3D animations not in the spec).
Two preventive controls:
- Enforcing a formal Change Control Board (CCB) workflow for every baseline change.
- Maintaining an explicit Project Exclusions list and Requirements Traceability Matrix (RTM) checked during code/sprint reviews.
Scope creep is unapproved external scope growth without baseline adjustments, whereas gold plating is adding unrequested features internally. Both are prevented via formal CCB change control, explicit scope exclusions, and RTM reviews.
A SaaS analytics portal has a total approved Scope Baseline budget of . Four Level-1 WBS nodes are estimated so far:
1.1 Project Management:1.2 Backend Data Pipeline:1.3 Web Dashboard:1.4 Security & Testing:
- Using the Rule, what budget remains for the final Level-1 node
1.5 Deployment & User Training? - After baseline approval, an approved Change Request adds an automated CSV export module costing . Compute the revised Scope Baseline budget and percentage scope-cost variance relative to the original baseline.
Finding missing WBS node 1.5 via the Rule:
Computing revised Scope Baseline after approved change:
- Budget for
1.5 Deployment & User Training: . - Revised Scope Baseline budget: ( increase).