Project Scope Management Knowledge Area

60 %
40 %
Information about Project Scope Management Knowledge Area
Business-Finance

Published on June 15, 2019

Author: AgileMercurial

Source: authorstream.com

Project Scope Management Knowledge Area: Project Scope Management Knowledge Area 6 Processes of Scope Management in a Project Project Scope: Project Scope Scope defines what work is required and managing scope ensures that the defined work is completed and only the defined work The Project Scope: The Project Scope Gold Plating / Scope Creep: Gold Plating / Scope Creep Gold Plating is the process of delivering more than what is required in the scope In many projects, customers will ask for things and insist that they aren’t change requests, the Project Manager must ensure that these requests are evaluated and will not impact the scope Changes to the scope must go through a change control process Product and Project Scope: Product and Project Scope Overview of Project Scope Management: Overview of Project Scope Management Process Groups and Project Scope Management: Process Groups and Project Scope Management 5.1 Plan Scope Management: 5.1 Plan Scope Management Belongs in the Planning Project Process Group 5.1 Plan Scope Management: 5.1 Plan Scope Management Scope Management Plan: Scope Management Plan Contains the process for defining the scope, how the scope will be created, and how it will be controlled and verified Part of the Project Management plan and is used as in input in creating the Project Management plan as part of the Integration processes Facilitates the creation of the Work Breakdown Structure (WBS) Describes the change request process Requirements Management Plan: Requirements Management Plan Describes how requirements will be collected and documented Includes the explanation on planning, tracking, and reporting of requirements Instructs on how to handle conflicting requirements from stakeholders 5.2 Collect Requirements: 5.2 Collect Requirements Belongs in the Planning Project Process Group 5.2 Collect Requirements: 5.2 Collect Requirements Collecting Requirements - Techniques: Collecting Requirements - Techniques Collecting Requirements - Techniques: Collecting Requirements - Techniques Collecting Requirements - Techniques: Collecting Requirements - Techniques Collecting Requirements - Techniques: Collecting Requirements - Techniques Documentation of Requirements: Documentation of Requirements Upon requirements being finalized, requirements need to be documented Assumptions, Dependencies, Constraints Stakeholder Requirements Solution/Technical Requirements Business Requirements Project Requirements Requirements pertaining to transition events Requirements Traceability: Requirements Traceability 5.3 Define Scope: 5.3 Define Scope Belongs in the Planning Project Process Group 5.3 Define Scope: 5.3 Define Scope Scope Statement: Scope Statement 5.4 Create WBS: 5.4 Create WBS WBS Levels: WBS Levels Generic WBS Example: Generic WBS Example WBS Dictionary: WBS Dictionary 5.5 Validate Scope: 5.5 Validate Scope Validating Scope Outputs: Validating Scope Outputs Accepted deliverables or phase project work May include change requests if the customer seeks a modification, a defect is found, or deliverables rejected for not meeting scope Validate Scope Process: Validate Scope Process 5.6 Control Scope: 5.6 Control Scope Belongs in the Monitoring & Controlling Project Process Group 5.6 Control Scope: 5.6 Control Scope Control Scope: Control Scope Sources: Sources A Guide to the Project Management Body of Knowledge – 6 th Edition https://www.pmi.org/ Joshua Render https://agile-mercurial.com

Add a comment

Related presentations