Unit 5_Project Scope Managment.pdf

Project Scope Management Week 9 Dr. Bader Alshoumr Ass. Professor • Discuss the importance of why good project scope is important • Describe the process of planning scope management Learning Objectives • Discuss methods for collecting and documenting requirements to meet stakeholders needs and...

Project Scope Management Week 9 Dr. Bader Alshoumr Ass. Professor • Discuss the importance of why good project scope is important • Describe the process of planning scope management Learning Objectives • Discuss methods for collecting and documenting requirements to meet stakeholders needs and expectations • Illustrate the process for creating a work-breakdown structure • Explain the importance of validating scope and how it relates to defining and controlling scope Project Scope Management • Project scope management includes the processes to ensure that the project addresses all the work required to complete the project successfully • Poor project scope management is one of the key reasons projects fail. For IT projects, it is important for good project scope management to have strong user involvement, executive support, a clear statement of requirements, and a process for managing scope changes • Many software products are available to assist in project scope management 3/30/2023 Dr. Bader Alshoumr - Health Informatics - UoH 3 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 product created as part of a project • Project scope management includes the processes involved in defining and controlling what work is or is not included in a project • Project scope management involve 6 processes 1. 2. 3. 4. 5. 6. 3/30/2023 Planning scope management Collecting requirements Defining scope Creating the WBS Validating scope Controlling scope Dr. Bader Alshoumr - Health Informatics - UoH 4 Project Scope Management Summary Planning Scope Management • The project team uses expert judgment and meetings to develop two important outputs: i. the scope management plan ii. the requirements management plan • The scope management plan is a subsidiary part of the project management plan. It can be formal or informal and broad or detailed, based on the needs of the project • A good scope management plan should include the following information: 1. How to prepare a detailed project scope statement 2. How to create a WBS 3. How to maintain and approve the WBS 4. How to obtain formal acceptance of the completed project deliverables 5. How to control requests for changes to the project scope 10/26/2023 Dr. Bader Alshoumr - Health Informatics - UoH 6 • Collecting requirements is often the most difficult step in project scope management • Requirements are often broken down into different groups such as functional requirements, service requirements, performance requirements, quality requirements, and training requirement Collecting Requirements 10/26/2023 • A major consequence of not defining requirements well is rework, which can consume up to half of project costs, especially for software development projects • The project’s size, complexity, importance, and other factors affect how much effort is spent on collecting requirements • There are several ways to collect requirements. For example i. Interviewing stakeholders ii. Holding focus groups and facilitated workshops iii. Using group creativity and decision-making techniques iv. Conducting questionnaires and surveys v. Conducting observations vi. Prototyping and document analysis vii. Benchmarking Dr. Bader Alshoumr - Health Informatics - UoH 7 Defining Scope • Good scope definition is very important to project success because it helps improve the accuracy of time, cost, and resource estimates, it defines a baseline for performance measurement and project control, and it aids in communicating clear work responsibilities • Key inputs for preparing the project scope statement include the project charter, scope management plan, requirements documentation, and organizational process assets • The main tools and techniques used in defining scope include expert judgment, product analysis, alternatives generation, and facilitated workshops • The main outputs of scope definition are the project scope statement and project documents updates • Project scope statements should include at least i. a product scope description, ii. product user acceptance criteria, and iii. detailed information on all project deliverables 10/26/2023 Dr. Bader Alshoumr - Health Informatics - UoH 8 Creating the Work Breakdown Structure • A work breakdown structure (WBS) is a deliverable-oriented grouping of the work involved in a project that defines its total scope • The WBS is a foundation document in project management because it provides the basis for planning and managing project schedules, costs, resources, and changes • The primary inputs for creating a WBS are the project scope management plan, scope statement, requirements documentation, enterprise environmental factors, and organizational process assets • The main tool or technique are expert judgement and decomposition - that is, subdividing project deliverables into smaller pieces -. • The outputs of the process of creating the WBS are • the scope baseline includes the approved project scope statement and its associated WBS and WBS dictionary • project documents updates • A project team often organizes the WBS around project products, project phases, or the project management process groups 10/26/2023 Dr. Bader Alshoumr - Health Informatics - UoH 9 Sample Intranet WBS Organized by product 10/26/2023 Dr. Bader Alshoumr - Health Informatics - UoH 10 Sample Intranet WBS Organized by deliverables 10/26/2023 Dr. Bader Alshoumr - Health Informatics - UoH 11 Creating the Work Breakdown Structure • Creating a good WBS is no easy task and usually requires several iterations. However, there are some basic principles should be applied to creating any good WBS • A unit of work should appear in only one place in the WBS • A WBS item is the responsibility of only one person, even though many people might be working on it • Project team members should be involved in developing the WBS to ensure consistency and buy-in 10/26/2023 Dr. Bader Alshoumr - Health Informatics - UoH 12 Validating Scope • Scope validation involves formal acceptance of the completed project deliverables • This acceptance is often achieved by a customer inspection and then sign-off on key deliverables • The main inputs for scope validation are the scope management plan, scope baseline, requirements documentation, requirements traceability matrix, validated deliverables, and work performance data • The main tools for performing scope validation are inspection and group decision-making techniques • The main outputs scope validation are accepted deliverables, change requests, work performance information, and project documents updates • Some project teams know from the start that the scope is very unclear and that they must work closely with the project customer to design and produce various deliverables 10/26/2023 Dr. Bader Alshoumr - Health Informatics - UoH 13 Controlling Scope • Scope control involves managing changes to the project scope while keeping project goals and business strategy in mind • You cannot do a good job of controlling scope if you do not first do a good job of collecting requirements, defining scope, and validating scope • The project management plan, requirements documentation, requirements traceability matrix, work performance data, and organizational process assets are the main inputs to scope control • An important tool for performing scope control is variance analysis • The outputs of scope control include work performance information, change requests, project management plan updates, project documents updates, and organizational process assets updates 10/26/2023 Dr. Bader Alshoumr - Health Informatics - UoH 14