Project Scope Management

Plan Scope Management
To Plan how the project scope will be defined, validated and controlled

Collect Requirements
To determine, document, and manage stakeholder needs and requirements.

Tools and techniques of Collect requirements
Group Creativity Techniques

1. Brainstorming
2. Nominal Group Technique
3. Delphi Technique
4. Idea and Mind Map Diagram
5. Affinity Diagram

Group Decision Making Techniques
1. Unanimity
2. Majority
3. Plurality
4. Dictatorship

Benchmarking – Compare actual or planned practices to those comparable organizations
To Identify best practices
Generate ideas for improvement
Providing a basis for measuring performance

Organizations compared can be Internal and External
Context Diagram for IT Case Study


Requirements Management Plan

Requirements Traceability Matrix

It’s a table that links requirements to their origin and traces them throughout the life of the project
Its provides a means to track requirements throughout the lifecycle of the project, helping to ensure that requirements approved in the requirements documentation are delivered at end of the project

Finally it provides a structure for managing changes to the product scope
This process includes, but is not limited to tracing

1.Requirements to business needs,opportunities,goals and objectives
2.Requirements to project objectives
3.Requirements to product scope/WBS deliverables
4.Requirements to product design
5.Requirements to product development
6.Requirements to test strategy and test scenarios
7.High-level requirements to more detailed requirements

Define Scope
To develop a detailed description of the project and product

Difference between Project Scope and Product Scope
Product Scope
The feature and functions that characterize a product, service or result
Completion measured against the requirements

Project Scope
The work that must be performed to deliver a product, service or result
Completion is measured against the plan

Project Scope Statement

1.Project Objectives
2.Product Scope description
3.Project requirement
4.Project boundaries
5.Project deliverables
6.Project acceptance criteria
7.Project constraints/assumptions
8.Initial Identified risk
9.Schedule milestones
10.Initial project organization
11.Fund limitation
12.Configuration management requirement
13.Approval requirement

Elements of the project charter and project scope statement
Project Charter
Project purpose or justification
Measurable project objectives and related success criteria
High-level requirements
High-level project description
High-level risks
Summary milestone schedule
Summary budget
Stakeholder list
Project approval requirements
(What constitutes success, decides it, who signs off)
Assigned Project manager, responsibility and authority level
Name of authority of the sponsor or other person(s) authorizing the project charter

Project Scope Statement
Project scope description (progressively elaborated)
Acceptance criteria
Project deliverables
Project exclusions
Project constraints
Project assumptions

Create WBS(Work Breakdown Structure)
The Process of subdividing project deliverables and project work into smaller, more manageable components

Sample WBS Organized by Phase

WBS Dictionary Template

Miscellaneous Terms
Work Package – A deliverable at the lowest level of WBS
Code of Accounts – Numbering systems used to identify unique components of WBS
Control Accounts – ( Cost Center ) A management control point where scope,budget,actual cost and schedule are integrated and compared to EV for performance management
Rolling Wave Planning – It is form of Progressive Elaboration. Work for near term is planned in details

Validate Scope
To formalize acceptance of the completed project deliverables

Control Scope
To monitor the status of the project and product scope and managing changes to the scope baseline