0% found this document useful (0 votes)
38 views

Project Scope Management: Copy Righted For Hosam Eid Mohammed (Kandeel)

This document discusses project scope management. It begins by asking why an organization needs a project and what resources the organization can use from its library to establish the project. It then discusses collecting requirements, defining the scope, creating a work breakdown structure (WBS), validating scope, and controlling scope. The key aspects are collecting stakeholder needs, documenting requirements, creating a project scope statement, developing a WBS to decompose the scope, and monitoring work performance to manage changes to the scope.

Uploaded by

Omer Khan
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
38 views

Project Scope Management: Copy Righted For Hosam Eid Mohammed (Kandeel)

This document discusses project scope management. It begins by asking why an organization needs a project and what resources the organization can use from its library to establish the project. It then discusses collecting requirements, defining the scope, creating a work breakdown structure (WBS), validating scope, and controlling scope. The key aspects are collecting stakeholder needs, documenting requirements, creating a project scope statement, developing a WBS to decompose the scope, and monitoring work performance to manage changes to the scope.

Uploaded by

Omer Khan
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 13

Project scope Management 

Copy righted for Hosam Eid Mohammed (kandeel)


Project scope Management 

Why do the 
Summary Description 
organization need the 
of the Project, 
project to be 
outlines module
established ?

What ever in the 
What ever the organization 
surrounding environment 
use out of it’s own library 
of the project & affect the 
to establish the project 
project (low, organizations, 
(template, processes, 
resource 
lessons learned,…Etc)
characteristic,…etc) 
Project scope Management 

Scope 

Quality
Project scope Management 

Planning 
Inputs
1. Plan Scope Management 
Outputs
Tools & Techniques

Initiation Project Charter  Expert Judgment  Scope Management Plan


Project management plan
Meetings  Requirement Management Plan
EEF and OPA

Project Charter 
The Birth Authorization of a project , Signed by the Sponsor & provides a High level project
requirements & high level project description, the Project charter names the Project manager & can
name the high level Roles in the project & the high level vendors & suppliers for special items, the
document includes as well a top level estimating budget for the project

Stakeholder Register 

Person or Organization that 
An Important Document Listing all the stockholders names
Stakeholder could impact or impacted by 
(definitions for organization)
the project 
Project scope Management 

Planning 
Inputs
2. Collect Requirement
Outputs
Tools & Techniques

Project Charter  Questioners and surveys 
Requirement Documentation
Stakeholder management plan Interviews  Observations 
Requirement Traceability matrix
Focus Groups Prototypes 
Scope Management Plan
Groups  creativity Techniques Brainstorming 
Requirement Management Plan
Groups Decision Making Nominal group

Unanimity ‐ Delphi Facilitated workshops Idea mind mapping 


Majority  Context diagram  Affinity diagram 
Plurality Document analysis Multicriteria decision

Planning 
Inputs
3. Define Scope
Outputs
Tools & Techniques

Project Charter  Expert Judgment

Product Analysis  Project Scope Statement
Scope Management Plan
Alternative Definition
Requirement Documentation Project Documents Update
Feasibility workshops 
OPA
Project scope Management 
Planning 
Inputs
4. Create WBS
Outputs
Tools & Techniques
Project Scope Statement
Decomposition Scope Baseline 
Requirement Documentation Expert Judgment
Project Document Update 
Scope Management Plan

OPA and EEF
Project Scope Statement

Product Scope definition WBS
Project Deliverables WBS Dictionary 
Project Constrains 
Acceptance Criteria
Project Assumption

WBS is a hieratical Arrangement of the project components & decomposition of 
the project scope into manageable parts that facilitate identifying the activities 
& assign the cost, time, Quantities & man‐hours to such activities & aggregating 
the totals to the WBS elements Up to the top level of the WBS so that we can 
determine the final cost & time for the project & accordingly we track & report 
the performance of the project  
Project scope Management 

Example of a WBS 
PROJECT
Level (0 – or Control Account level – Div 03 ) 0 

WBS 1 WBS 2 WBS 3 WBS 4 WBS 5


Level (1)
0.1  0.2  0.3 0.4 0.5

WBS 1 WBS 2 WBS 3


Level (2)
0.2.1 0.2.2 0.2.3

WBS 1 WBS 2 WBS 3 WBS 4 WBS 4


Level (3)
0.2.3.1  0.2.3.2 0.2.3.3 0.2.3.4 0.2.3.5

End Level (work Package level) after which the  WBS 1 WBS 2 WBS 3


Listing of the activities is being developed   0.2.3.4.1  0.2.3.4.2 0.2.3.4.3
Project scope Management 

The Philosophy of defining & detailing the definition of scope is to try to tend
the project to a manageable form, as we cant use the requirement nor the scope
definition to Manage the project or to achieve the goals of the project

After keep saying & repeating 
“Managing, Managing & 
Managing” could anyone here 
tell me what is the meaning of 
managing……?
Project scope Management 

Scope
Project scope Management 

Work Performance Data
Are the row observation and measurements identified during activities being 
performed to carryout the project work. Data are often viewed as the lowest level  
of detail from which information is delivered by other process. 

Technical  Actual start and 
Actual cost & 
Work completed  KPIs performance  finish dates of 
durations 
measurements  the schedule 

Work Performance Information 

The performance data collected from various controlling processes, analyzed in 
context, and integrated based on relationships across areas. Thus work 
performance data has been transformed to work performance information.

Implementation 
Estimate to  Estimated finish 
Status of delivery status of change  Forecasts 
complete cost  dates 
requests 
Project scope Management 

Monitoring & controlling 
Inputs
5. Validate Scope 
Outputs
Tools & Techniques

Project Management Plan Inspection Change Requests 


Requirement Documentation Accept Deliverables 
Requirement Traceability matrix Work Performance Information
Verified Deliverables Project Document Update 
Work Performance data

Monitoring & controlling 
Inputs
6. Control Scope 
Outputs

Tools & Techniques

Project Management Plan Variance Analysis Work Performance information


Requirement Documentation OPA Update 
Requirement Traceability matrix Change Requests 
Work Performance data PM Plan Update
OPA Project Document Update 
Project scope Management 

Resulted in 
Being Done upon 
release of 
4. Validate  the finishing of a 
payment & 
Scope  part , phase, stage 
official 
or sub‐product 
approval

There is no 
need of 
Being Done  releasing 
5. Control  payment, it is 
Periodically to  just 
Scope  avoid scope creep monitoring 
the 
performance
Project scope Management 

You might also like