1/8/2011
1
Project ManagementProject ManagementProject ManagementProject ManagementKnowledge AreasKnowledge Areas
Section Section –– 33Chapter Chapter –– 55pp
Project Scope ManagementProject Scope ManagementSession Objectives…1. To identify Project Scope Management 1. To identify Project Scope Management
knowledge area processes2. How to collect Requirements3. How to create Project Scope Statement4. How to create WBS and WBS Dictionary5 How to verify Scope the Deliverables 5. How to verify Scope the Deliverables
produced6. How to control Scope throughout the
Project
1/8/2011
2
Project Scope ManagementProject Scope ManagementExam Objectives…1 1 Collecting Requirements1. 1. Collecting Requirements2. 2. Creating Scope Definition3. 3. Creating Work Breakdown
Structure4 4 Verifying the Project Scope4. 4. Verifying the Project Scope5. 5. Managing the Scope
Project Scope ManagementProject Scope ManagementThe Processes in Project ScopeManagement are:Management are:1. 1. Collect Requirements2. 2. Define Scope3. 3. Create WBS4 4 Verify Scope4. 4. Verify Scope5. 5. Control Scope
1/8/2011
3
Project ScopeProject Scope
may be categorized as…
Product Scope:- Project Scope:-
Collect RequirementsCollect RequirementsThe process of defining and documenting customer needsThe customer requirements have to be elicited, analyzed and recordedThe Requirements are categorized as
Project Requirements Product Requirements
1/8/2011
4
Collect RequirementsCollect Requirements
•1. Project Charter•2. Stakeholder Register
•1. Interviews•2. Focus Groups•3. Facilitated Workshops•4. Group Creativity Techniques•5. Group Decision Making Techniques•6 Questionnaires and Surveys
Tools & Techniques
•1. Requirements Documentation•2. Requirements Management Plan•3. Requirements Traceability Matrix
Input
•6. Questionnaires and Surveys•7. Observations•8. Prototypes
Output
Collect RequirementsCollect Requirements
Inputs1 Project Charter1. Project Charter2. Stakeholder Register
1/8/2011
5
Collect RequirementsCollect RequirementsTools and Techniques1 Interviews1. Interviews2. Focus Groups3. Facilitated Workshops4. Group Creativity Techniques5. Group Decision Making Techniques6. Questionnaires and Surveys7. Observations8. Prototypes
Collect RequirementsCollect Requirements
Outputs1 Requirements Documentation1. Requirements Documentation2. Requirements Management Plan3. Requirements Traceability Matrix
1/8/2011
6
Tools & TechniquesTools & TechniquesGroup Creativity Techniques1. Brainstorming1. Brainstorming2. Nominal Group Techniques3. Delphi TechniqueGroup Decision Making Techniques1. Unanimity2 Majority2. Majority3. Plurality4. Dictatorship
Requirements DocumentationRequirements DocumentationContains..1. Business needs2. Business and Project objectives for
traceability3. Functional Requirements4. Non-Functional Requirements5. Quality Requirements6. Acceptance Criteria6. Acceptance Criteria7. Support and Training Requirements8. Requirements Assumptions and Constraints9. Business Rules
1/8/2011
7
Requirements Management PlanRequirements Management PlanContains..1 How requirements activities will be 1. How requirements activities will be
planned, tracked and reported2. How configuration activities will be
planned, tracked and reported3. Description of requirements
prioritizationprioritization4. How product metrics are defined5. How traceability structure is defined
Define ScopeDefine Scope
Defining the project scope is critical tothe success of the project since itthe success of the project since itdescribes exactly what the product orservice of the project is being made.Scope Definition is a process to prepare adetailed Project Scope Statement.
1/8/2011
8
Define ScopeDefine Scope
• 1. Project Charter• 2. Requirements
Documentation• 3. Organizational
Process Assets• 1. Expert Judgment
Tools & Techniques
• 1. Project Scope Statement
• 2. Project Document Updates
Input Output
Define ScopeDefine ScopeInputs
1 Project Charter1. Project Charter2. Requirements Documentation3. Organizational Process Assets
Tools & Techniques1. Expert Judgment2. Product Analysis3. Alternative Identification4. Facilitated Workshops
1/8/2011
9
Define ScopeDefine Scope
Outputs1 Project Scope Statement1. Project Scope Statement2. Project Document Updates
Stakeholder RegisterRequirements DocumentationRequirements Traceability MatrixRequirements Traceability Matrix
Define ScopeDefine ScopeProject Scope Statement defines whatwork will be performed and what work ispexcluded.Project Scope Statement includes…
Project Scope DescriptionProduct Acceptance CriteriaP j t D li blProject DeliverablesProject exclusionsProject Constraints & Assumptions
1/8/2011
10
Create WBSCreate WBSWBS decomposes the project work intosmaller, more manageable pieces of work.WBS is a deliverable-oriented hierarchicaldecomposition of Project WorkDecomposition of project deliverables1. The major deliverables of the project are
identified, including project managementactivities
2. Determine if adequate cost and timeestimates can be applied to the lowestproject work.
Create WBSCreate WBS
Decomposition of project deliverables3 Identify the deliverable’s constituent3. Identify the deliverable s constituent
components. Each component of thework can be measured, and may takevarying amounts of time to complete.
4. Verify the decomposition. The lower-level items must be evaluated toensure they are completed andaccurate
1/8/2011
11
Project Management PlanProject Management Plan
WBSCost
Estimating
•WBS is very important as it is input to 5core processes
Risk Management
Planning
Activity Definition
Resource Planning
Cost Budgeting
Create WBSCreate WBS
• 1. Project Scope Statement
• 2. Requirements Documentation
• 3. Organizational Process Assets
• 1. Decomposition
Tools & Techniques
• 1. WBS• 2. WBS Dictionary• 3. Scope Baseline• 4. Project Document
Updates
Input Output
1/8/2011
12
Create WBSCreate WBSInputs
1 Project Scope Statement1. Project Scope Statement2. Requirements Documentation3. Organizational Process Assets
Tools & Techniques1 Decomposition1. Decomposition
Create WBSCreate WBSOutputs
1 Work Breakdown Structure1. Work Breakdown Structure2. WBS Dictionary3. Scope Baseline
Project Scope StatementWBSWBSWBS Dictionary
1. Project Document Updates
1/8/2011
13
Create WBSCreate WBS
Project
PM 1.1
1.1.1 1.1.2
1 1 2 1 1 1 2 2
HW 1.2
1.2.1
1.2.2
SW 1.3 SYS Eng 1.4 Testing 1.5 Database 1.6
Level- 1
Level- 2
Level- 4
Level- 3
1.1.2.1 1.1.2.2
1.1.2.2.1 1.1.2.2.2
Level 4
Level- 5
Create WBSCreate WBSLevels of WBSProjectProject
o 1.1 Phase 11.1.1 Deliverable1.1.1.1 Deliverable
1 1 1 1 1 Deliverable1.1.1.1.1 Deliverable
WBS Identifier
1/8/2011
14
WBS DictionaryWBS DictionaryContains..
Code of accounts identifier.Description of work.Person / organization responsible tocompleting the component.List of schedule milestones.Associated schedule activities.R i d & C iResources required & Cost estimates.Quality requirements & Acceptancecriteria.Technical references.
Verify ScopeVerify ScopeVerify Scope is the process of the projectcustomer accepting the project deliverables.happens at the end of each project phase ora major deliverables are createdis ensuring that the deliverables the projectcreates are in alignment with the projectscopeVerification of Scope differs from qualityp q ycontrolQuality control is preformed before scopeverification
1/8/2011
15
Verify ScopeVerify Scope
• 1. Project Scope Statement
• 2. WBS Dictionary• 3. Project Scope
Management Plan• 4. Deliverables
• 1. Inspection
Tools & Techniques
• 1. Accepted Deliverables
• 2. Change Requests• 3. Project Document
Updates
Input Output
Verify ScopeVerify ScopeInputs1. Project Management Planj g
Project Scope StatementWBSWBS Dictionary
1. Requirements Documentation2. Requirements Traceability Matrix3. Validated DeliverablesTools & Techniques
1. Inspection
1/8/2011
16
Verify ScopeVerify ScopeOutputs
1 Accepted Deliverables1. Accepted Deliverables2. Change Requests3. Project Document Updates
ControlControl ScopeScopeProject Scope Control concerned withinfluencing the factors that create projectg p jscope changes and controlling the impactof those changes.Scope control assures all requestedchanges and recommended correctiveactions are processed through Integratedp g gChange Control ProcessUncontrolled changes are referred to asScope Creep
1/8/2011
17
Control ScopeControl Scope
•1. Project Management Plan•2. Work Performance Information
•3. Requirements Documentation•4. Requirements Traceability Matrix
•5. Organizational Process Assets
•1. Variance Analysis
Tools & Techniques
•1. Work Performance Measurements
•2. Organizational Process Assets•3. Change Requests•4. Project•Management Plan Updates•5. Project Document Updates
Input Output
Scope ControlScope ControlInputs
1. Project Management PlanScope BaselineScope Management PlanChange Management PlanConfiguration Management PlanRequirements Management Plan
1. Work Performance Information1. Work Performance Information2. Requirements Documentation3. Requirements Traceability Matrix4. Organizational Process Assets
1/8/2011
18
Scope ControlScope ControlTools & Techniques1. Variance AnalysisyOutputs1. Work Performance Measurements2. Organizational Process Assets Updates3. Change Requests4. Project Management Plan Updates5. Project Document Updates
Requirements DocumentationRequirements Traceability Matrix
Project Scope ManagementProject Scope ManagementTo Sum up…
1. We identified Project Scope Managementk l dknowledge area processes
2. We know how to collect requirements3. We know how to create Project Scope
Statement4. We know how to create WBS and WBS
Dictionary5 W k h t if S th5. We know how to verify Scope the
Deliverables produced6. We know how to control Scope throughout
the Project
1/8/2011
19
Questions ?