CHATER 5 : CHATER 5 PROJECT SCOPE MANAGEMENT Projects can be completed in two ways: : Projects can be completed in two ways: Planned and then executed or
Executed, stopped, planned and then executed. Project Scope Management : Project Scope Management includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully.
Managing the project scope is primarily concerned with defining and controlling what is and is not included in the project. Project Scope Management Processes : Project Scope Management Processes Collect Requirements: The process of defining and documenting stakeholders’ needs to meet the project objectives.
Define Scope: The process of developing a detailed description of the project and product.
Create WBS: The process of subdividing project deliverables and project work into smaller, more manageable components. 4 Project Scope Management Processes : Project Scope Management Processes Verify Scope: The process of formalizing acceptance of the completed project deliverables.
Control Scope: The process of monitoring the status of the project and product scope and managing changes to the scope baseline 5 Slide 6: Verify Scope Define Scope Create WBS Control Scope Collect Req Proj Scope Mgmt 6 Context of Scope : Context of Scope Product scope. The features and functions that characterize a product, service, or result
Completion of the product scope is measured against the product requirements
Project scope. The work that needs to be accomplished to deliver a product, service, or result with the specified features and functions.
Completion of the project scope is measured against the project management plan 7 Scope Baseline : Scope Baseline The approved detailed project scope statement and
its associated WBS and WBS dictionary are the scope baseline for the project.
This base lined scope is then monitored, verified, and controlled throughout the lifecycle of the project. 8 Collect Requirements : Collect Requirements 9 Collect Requirements : Collect Requirements Collect Requirements is the process of defining and documenting stakeholders’ needs to meet the project objectives.
Requirements become the foundation of the WBS.
Product requirements can include information on technical requirements, security requirements, performance requirements etc. 10 Slide 11: Collect Requirements: Inputs, Tools & Techniques, and Outputs Slide 12: 12 GROUP CREATIVITY TECHNIQUE : GROUP CREATIVITY TECHNIQUE Brainstorming
The Delphi Technique
Idea Mind Maping 13 MIND MAP : MIND MAP 14 Slide 15: http://www.jiludwig.com/Requirements_Management.html 15 Slide 16: 16 GROUP CREATIVITY TECHNIQUE : GROUP CREATIVITY TECHNIQUE Brainstorming
The Delphi Technique
Idea Mind Maping
Affinity Diagram 17 Affinity Diagram : Affinity Diagram Affinity diagrams are great tools for assimilating and understanding large amounts of information.
When you work through the process of creating relationships and working backward from detailed information to broad themes, you get an insight you would not otherwise find. 18 Slide 19: 19 Group Decision Making Techniques : Group Decision Making Techniques Unanimity
Dictatorship 20 OUTPUTS : OUTPUTS Requirement Doc
Requirement Mgmt Plan
How requirement activity will be planned
Configuration mgmt activity as how changes to the product
Requirement Prioritization Process
Traceability structure 21 Slide 22: 22 Define Scope : Define Scope 24 Slide 25: Define Scope:
Inputs, Tools & Techniques, and Outputs WBS : WBS 27 Slide 28: Create WBS: Inputs, Tools & Techniques, and Outputs Points to remember;
Rolling Wave Planning
Work Package Slide 33: Verify Scope:
Inputs, Tools & Techniques, and Outputs CONTROL SCOPE : CONTROL SCOPE 35 Control Scope : Control Scope Process of monitoring the status of project and product scope and managing changes to the scope baseline
This step ensures all requested changes and recommended corrective or preventive actions are processed through ICC
Uncontrolled changes are often referred to as scope creep 36 Slide 37: Control Scope:
Inputs, Tools & Techniques, and Outputs Slide 39: Control Scope:
Inputs, Tools & Techniques, and Outputs