Chapter 6 - 2022 Scope Planning PDF

Summary

This document details concepts related to project scope management, including the planning of scope management, collecting requirements, and defining scope. It also describes a work breakdown structure (WBS) and different methods of developing a WBS. There is also content on topics such as stakeholder input and needs, requirements traceability matrices, and scope verification. The focus is on project planning and the management of project scope.

Full Transcript

CONTEMPORARY PROJECT MANAGEMENT, 4E Timothy J. Kloppenborg Vittal Anantatmula Kathryn N. Wells 1 Chapter 6 Scope Planning 2 Chapter 6 Core Objectives: Describe the planning of scope management...

CONTEMPORARY PROJECT MANAGEMENT, 4E Timothy J. Kloppenborg Vittal Anantatmula Kathryn N. Wells 1 Chapter 6 Scope Planning 2 Chapter 6 Core Objectives: Describe the planning of scope management, collecting requirements, & defining scope processes Create a requirements traceability matrix, project scope statement, & change request form Describe a work breakdown structure (WBS) and why it is important Compare different methods of developing a WBS Scope PlanningProcesses © 2015 Cengage Learning. All Rights Reserved. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. What is Project ScopeManagement? ment Scope refers to all the work involved in creating the products of the project and the processes used to create them 4 A deliverable is a product produced as part of a project, such as hardware or software, planning documents, or meeting minutes Project scope management includes the processes involved in defining and controlling what is or is not included in a project © 2015 Cengage Learning. All Rights Reserved. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. Project Scope Management PMP Prep Course – PMBOK 4th Edition Version 4.0 Project Scope vs. Product Scope Product Scope – the features and functions that characterize a product, service or result. Project Scope – the work performed to deliver the product, service, or result with the specified features and functions. “The term project scope is sometimes viewed as including product scope”. ©2011 Long Island Chapter of the Project Management Institute ALL RIGHTS RESERVED 6 Project Scope Management PMP Prep Course – PMBOK 4th Edition Version 4.0 ©2011 Long Island Chapter of the Project Management Institute ALL RIGHTS RESERVED 7 Project Scope Management PMP Prep Course – PMBOK 4th Edition Version 4.0 Project Scope Management Processes Scope planning: deciding how the scope will be defined, verified, and controlled Scope definition: reviewing the project charter and preliminary scope statement and adding more information as requirements are developed and change requests are approved Creating the WBS: subdividing the major project deliverables into smaller, more manageable components Scope verification: formalizing acceptance of the project scope by key project stakeholders Scope control: controlling changes to project scope which impact project cost and time goals ©2011 Long Island Chapter of the Project Management Institute ALL RIGHTS RESERVED 8 How Do We ManageScope? Five processes Collect Requirements Define Scope Create WBS Verify Scope Control Scope Collect Define Create Verify Control WBS Requirements Scope Scope Scope © 2015 Cengage Learning. All Rights Reserved. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. Collect Requirements Make sure the project team is absolutely clear on the project objectives Requirement– a condition or capability needed by a user to solve a problem or achieve an objective that satisfies a standard, specification, or any other formally- documented need. Collect requirements – a systematic effort to understand and analyze stakeholder needs to define and document these needs and requirements with a focus on meeting project objectives. © 2015 Cengage Learning. All Rights Reserved. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected we use. GatherStakeholder Input & Needs Use voice of the customer techniques (VOC) Ask questions Place yourself in the customer’s situation State customer desires in operational terms Collecting requirements is th same regardless of type of project. Generally Agile documentation is less formal, thus allowing for progressive elaboration © 2015 Cengage Learning. All Rights Reserved. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected we bsite for classroom use. Requirements Traceability Matrix Define Scope Define scope – the process of translation stakeholder needs and requirements into detailed specifications of the project outcomes & products 3-1- Reasons to Define Scope 3-2- How to Define Scope List deliverables and acceptance criteria Establish project boundaries Create a project work statement 3-3- Defining Scope in Agile Projects © 2015 Cengage Learning. All Rights Reserved. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected we use. 3-1 Reasons toDefine Scope © 2015 Cengage Learning. All Rights Reserved. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected we use. Project Scope Management PMP Prep Course – PMBOK 4th Edition Version 4.0 Create WBS Definition: “The process of subdividing (decomposition) project deliverables and project work into smaller, more manageable components.” The WBS is a hierarchical decomposition of the total scope of work to be carried out by the project team to: accomplish the project objectives create the required deliverables. organize and define the total scope of the project, represent the work specified in the current approved project scope statement. PMBoK® Guide,5th Edition, p. 125 ©2011 Long Island Chapter of the Project Management Institute ALL RIGHTS RESERVED 15 Project Scope Management PMP Prep Course – PMBOK 4th Edition Version 4.0 WBS Templates (cont’d) Various other Breakdown Structures include: Organizational Breakdown Structure (OBS) – i.e.: Org Chart Risk Breakdown Structure (RBS): illustrates the potential risks on the project, broken down by risk category Resource Breakdown Structure: illustrates the type of resources required on the project. Bill Of Materials (BOM): includes all components, assemblies and sub-assemblies required to build the product. ©2011 Long Island Chapter of the Project Management Institute ALL RIGHTS RESERVED 16 Work Breakdown Structure WBS: records task names Numbering – Applying numbers to the various work elements lets project team members know where work fits together within the project. WBS Dictionary Is the formal project document that provides detailed descriptions of key information for all Elements in the Work Breakdown Structure Is a supporting document to the (WBS). It provides supporting data about project tasks in the WBS. This information can be any type and format, ranging from textual information to numerical data to milestone dates Provides a discerption of the work to be done for each WBS work package Helps preventing the scope to creep by defining the details of work package Output of create WBS process The goals of developing a WBSand WBSDictionary are 1) for the project team to proactively and logically plan out the project to completion, 2) to collect the information about work that needs to be done for a project, and 3) to organize activities into manageable components that will achieve project objectives. The WBSand WBSDictionary are not the schedule, but rather the building blocks to it. The progression of WBSand WBSDictionary development is as follows: WBS(Diagram WBS Detailed or List) Dictionary Schedule Goal Goals Goal Define comprehensive Describe task Integrate detailed list of list of project activities Sequence activities project activities, 19 Estimate duration dependencies, constraints, and Estimate resources resources to reflect complete Identifyconstraints timeframe Work Packages Are the smallest unit of work that a project can be broken down to when creating your Work Breakdown Structure (WBS)., for which the cost and duration can be estimated & managed. © 2015 Cengage Learning. All Rights Reserved. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. Establish Change Control Projects are conducted in an atmosphere of uncertainty Plans must be made to ensure all potential changes are considered, accepted or rejected, and that their impact is factored into revised plans Change control system: a system of managing and controlling changes and modifications to the project plan and project deliverables Document potential changes to a project with a change request Every change to a project must be formally proposed Change request: a written request or formal proposal to change any project planning component, such as a document, project deliverable, or the baseline (scope, cost, and time). © 2015 Cengage Learning. All Rights Reserved. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected we use. Possible risk actions 25  Acceptance ◼ Where countermeasures not available or not cost-effective  Avoidance ◼ To reduce the likelihood of occurrence  Mitigation ◼ To soften the effect/s if the risk does occur  Transfer ◼ Making impact fall on another party, for example through insurance Summary Use scope planning to determine deliverables and acceptance criteria. Organize scope into a work breakdown structure (WBS). Decompose the project into smaller and smaller pieces. Assign WBS components. Create WBS by hand or use MS Project to create WBS. © 2015 Cengage Learning. All Rights Reserved. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license distributed with a certain product or service or otherwise on a password-protected website for classroom use. PMBOK Exams When in doubt, work backwards from your desired solution What would it take to make this project/product successful? Collect Requirements—get input from stakeholders, end-users, & SMEs Break down project deliverables into smaller and smaller pieces with a WBS Remember, these are things (nouns), not activities (verbs) Lowest level (work packages) should be small enough to monitor

Use Quizgecko on...
Browser
Browser