1. PROJECT SCOPE MANAGEMENT
BUS(445)
Zammel mongia
هــ

2. What is Project Scope Management?
Scope refers to all the work involved in creating the products of the project and the processes used to create them.
A deliverable is a product produced as part of a project, such as hardware or software, planning documents, or meeting minutes
Project scope management The processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully”
Zammel mongia
هــ

3. Product and project scope
Product Scope:
The feature and functions that characterize a product, service, or results
Project Scope:
The work performed to deliver a product, service, or result with the specified feature and functions.
Zammel mongia
هــ

4. How Do We Manage Scope?
The knowledge area of Project Scope Management consists of the following processes:
Planning Scope Management
Collect Requirements
Define Scope
Create WBS
Verify Scope
Control Scope
Zammel mongia
هــ

5. Scope Planning and the Scope Management Plan
The scope management plan is a document that includes descriptions of how the team will prepare the project scope statement, create the WBS, verify completion of the project deliverables, and control requests for changes to the project scope
Key inputs include the project charter, preliminary scope statement, and project management plan
It can be formal or informal, broadly framed or highly detailed, based on the needs of the project.
It should be reviewed with the project sponsor to make sure the approach meets expectations
Zammel mongia
هــ

6. Collect Requirements
*This process involves the documentation of the stakeholders needs with the intention of meeting the project objectives. *During this process managers seek to use multiple techniques and tools for the collection of the project requirements from the stakeholders. *If this process if performed thoroughly and correctly, it reduces the number of surprises as the project moves towards completion.
Zammel mongia
هــ

7. Collect Requirements Tools & Techniques Outputs Interviews
Focus groups
Facilitated workshops
Group creativity techniques
Group decision making techniques
Questionnaires and surveys
Observations
Prototypes
Requirements docs
Project Charter
Stakeholder Register
Requirements mgmt plan
Requirements traceability matrix
Collect
Requirements
Define
Scope
Create WBS
Verify
Control
Zammel mongia
هــ

8. Define Scope
The Process of developing a detailed description of the project and product . *It involves the defining of a detailed description of the project and its major deliverables. *This process clearly states what the project is supposed to and what it cannot accomplish . *The supporting documents are reviewed ensuring that the project will work up to the stated goals. The resulting scope will then state the stakeholder’s needs and communicate the expectations for the performance of the project.
Zammel mongia
هــ

9. Define Scope Inputs Tools & Techniques Outputs Project Charter
Expert judgement
Product analysis
Alternatives identification
Facilitated workshops
Outputs
Project Scope Statement
Requirements documentation
Project Document Updates
Organizational Process Assets
Collect
Requirements
Define
Scope
Create WBS
Verify
Control
Zammel mongia
هــ

10. Work Breakdown Structure
WBS is the process of subdividing project deliverables and project work into smaller, more manageable components.
WBS is a foundation document that provides the basis for planning and managing project schedules, costs, resources, and changes
Zammel mongia
هــ

11. Work Breakdown Structure
Inputs for creating a WBS:
* The project scope statement
* project management plan are the primary
Outputs from WBS
*the WBS itself,
*the WBS dictionary,
*a scope baseline
* Updates to the project scope statement and scope management plan
The WBS is often depicted as a task-oriented family tree of activities
The WBS can be organized around project products, project phases or using the project management process groups
هــ
Zammel mongia

12. Create WBS Outputs Inputs Tools & Techniques Project scope statement
Decomposition
Work Breakdown Structure (WBS)
Requirements documentation
Organizational process assets
WBS Dictionary
Scope Baseline
Project Document Updates
Collect
Requirements
Define
Scope
Create WBS
Verify
Control
Zammel mongia
هــ

13. Validate Scope
It is very difficult to create a good scope statement and WBS for a project
It is even more difficult to verify project scope and minimize scope changes
Scope verification involves formal acceptance of the completed project scope by the stakeholders
Acceptance is often achieved by a customer inspection and then sign-off on key deliverables
Zammel mongia
هــ

14. Validate Scope Inputs Outputs Project Management Plan Inspection
Accepted Deliverables
Requirements Documentation
Change Requests
Requirements Traceability Matrix
Project Document Updates
Validated Deliverables
Collect
Requirements
Define
Scope
Create WBS
Verify
Control
هــ
Zammel mongia

15. Control Scope
Scope control involves controlling changes to the project scope
Goals of scope control are to:
Influence the factors that cause scope changes
Assure changes are processed according to procedures developed as part of integrated change control
Manage changes when they occur
Tools for performing scope control include a change control system and configuration management
Variance is the difference between planned and actual performance
هــ
Zammel mongia

16. Control Scope Tools & Techniques Outputs Inputs
Project Management Plan
Work Performance Measures
Variance analysis
Work Performance Information
Organizational Process Assets
Requirements Documentation
Change Requests
Project Management Plan Updates
Requirements Traceability Matrix
Project Document Updates
Organizational Process Assets
Collect
Requirements
Define
Scope
Create WBS
Verify
Control
Zammel mongia
هــ

17. Best Practices for Avoiding Scope Problems
1. Keep the scope realistic: Don’t make projects so large that they can’t be completed; break large projects down into a series of smaller ones
2. Involve users in project scope management: Assign key users to the project team and give them ownership of requirements definition and scope verification
3. Use off-the-shelf hardware and software whenever possible: Many IT people enjoy using the latest and greatest technology, but business needs, not technology trends, must take priority
4. Follow good project management processes: As described in this chapter and others, there are well-defined processes for managing project scope and others aspects of projects
هــ
Zammel mongia