PROJECT SCOPE MANAGEMENT (FIFTH CHAPTER IN GUIDE PMBOK)

Get Started. It's Free
or sign up with your email address
Rocket clouds
PROJECT SCOPE MANAGEMENT (FIFTH CHAPTER IN GUIDE PMBOK) by Mind Map: PROJECT SCOPE MANAGEMENT (FIFTH CHAPTER IN GUIDE PMBOK)

1. IT CONSISTS OF FIVE PROCESSES

1.1. COLLECT REQUIREMENTS

1.1.1. INPUTS

1.1.1.1. Project charter

1.1.1.1.1. it is used to provide

1.1.1.2. Stakeholder register

1.1.1.2.1. it is used to identify stakeholders that can provide information on detailed project and product requirements

1.1.2. TOOLS &TECHNIQUES

1.1.2.1. Interviews

1.1.2.1.1. it could be

1.1.2.1.2. PURPOSE

1.1.2.2. Focus groups

1.1.2.2.1. Pre‐qualified stakeholders & subject matter experts conform an interactive discussion guided for a trained moderator

1.1.2.3. Facilitates workshops

1.1.2.3.1. Focused sessions that bring key Cross‐functional stakeholders together to define product requirements

1.1.2.4. Group creativity techniques

1.1.2.4.1. Activities to identify project and product requirements

1.1.2.4.2. EXAMPLES

1.1.2.5. Group decision making techniques

1.1.2.5.1. It is an assessment process of multiple alternatives. These techniques can be used generate, classify and prioritize products requirements

1.1.2.5.2. EXAMPLES

1.1.2.6. Questionnaires and surveys

1.1.2.6.1. These are written sets of questions designed to quickly accumulate information

1.1.2.7. Observations

1.1.2.7.1. They provide a direct way of viewing people’s jobs or tasks and carry out processes.

1.1.2.7.2. Also called,

1.1.2.8. Prototypes

1.1.2.8.1. It is a method to obtain a feedback of a model product before building it

1.1.3. OUTPUTS

1.1.3.1. Requirement documentation

1.1.3.1.1. It describes how individual requirements meet the business need for the project.

1.1.3.1.2. It can include but are not limited to

1.1.3.2. Requirements Management Plans

1.1.3.2.1. It is how requirement activities will be analyzed, documented, and managed throughout the project

1.1.3.2.2. They can include but are not limited to

1.1.3.3. Requirements Traceability Matrix

1.1.3.3.1. It is a table that links requirements to their origin and traces them throughout the project life cycle

1.1.3.3.2. it can include but is not limited to

1.1.4. OVERVIEW

1.2. DEFINE SCOPE

1.2.1. INPUTS

1.2.1.1. Project charter

1.2.1.2. Requirements documentation

1.2.1.3. Organizational process assets

1.2.1.3.1. Examples include but are not limited to

1.2.2. TOOLS &TECHNIQUES

1.2.2.1. Expert judgment

1.2.2.1.1. It is often used to analyze the information needed to develop the project scope statement

1.2.2.1.2. SOURCES

1.2.2.2. Product analysis

1.2.2.2.1. It includes techniques such as

1.2.2.3. Alternatives identification

1.2.2.3.1. It is a technique used to generate different approaches to execute and perform the work of the project

1.2.2.4. Facilitated workshops

1.2.3. OUTPUTS

1.2.3.1. Project Scope Statement

1.2.3.1.1. It describes in detail the project’s deliverables and the work requiredto create those deliverables

1.2.3.1.2. includes

1.2.3.2. Project document updates

1.2.3.2.1. Project document that can be updated include but are not limited to

1.2.4. OVERVIEW

1.3. CREATE WBS

1.3.1. INPUTS

1.3.1.1. Project scope statement

1.3.1.2. Requirements documentation

1.3.1.3. Organizational process assets

1.3.1.3.1. They include but are not limited to

1.3.2. TOOLS &TECHNIQUES

1.3.2.1. Decomposition

1.3.2.1.1. It is the subdivision of project deliverables into smaller more manageable components until the work and deliverables are defined to the work package level.

1.3.2.1.2. It involves the following activities

1.3.2.1.3. Structure

1.3.3. OUTPUTS

1.3.3.1. WBS

1.3.3.1.1. it is a deliverable-oriented hierarchical decomposition of the work to be executed by the project team, to accomplish the project objectives and create the required deliverables, with each descending level of the WBS representing and increasingly detail definition of the project work.

1.3.3.2. WBS dictionary

1.3.3.2.1. It is a document created by the Create WBS process that support the WBS

1.3.3.2.2. The information includes but is not limited to

1.3.3.3. Scope baseline

1.3.3.3.1. It is a component of the project management plan.

1.3.3.3.2. COMPONENTS:

1.3.3.4. Project document updates

1.3.3.4.1. Project documents that may be updated include, but are not limited to requirements documentation

1.3.4. OVERVIEW

1.4. VERIFY SCOPE

1.4.1. INPUTS

1.4.1.1. Project management plan

1.4.1.1.1. Components of the scope baseline include:

1.4.1.2. Requirements documentation

1.4.1.3. Requirements traceability matrix

1.4.1.4. Validated deliverables

1.4.1.4.1. Validated deliverables have been completed and checked for correctness by the Perform Quality Process

1.4.2. TOOLS &TECHNIQUES

1.4.2.1. Inspection

1.4.2.1.1. It includes activities such as measuring, examining, verifying work in order to check if the products and deliverables fulfill the requirements & acceptable criteria

1.4.3. OUTPUTS

1.4.3.1. Accepted deliverables

1.4.3.1.1. Meet the acceptance criteria

1.4.3.2. Change requests

1.4.3.2.1. Deliverables that have not been formally accepted are documented, along with the reasons for non-acceptance

1.4.3.3. Project document updates

1.4.3.3.1. Project document that may be update as a result of verify scope

1.4.4. OVERVIEW

1.5. CONTROL SCOPE

1.5.1. INPUTS

1.5.1.1. Project management plan

1.5.1.1.1. The PMP contains the following information that is used to control Scope

1.5.1.2. Work performance information

1.5.1.2.1. It is information about project progress, such as which deliverables have started, their progress and which deliverables have finished

1.5.1.3. Requirements documentation

1.5.1.4. Requirements traceability matrix

1.5.1.5. Organizational process assets

1.5.1.5.1. They include but are not limited to

1.5.2. TOOLS &TECHNIQUES

1.5.2.1. Variance analysis

1.5.2.1.1. It is used to assess the magnitude of variation from the original scope baseline.

1.5.3. OUTPUTS

1.5.3.1. Work performance measurements

1.5.3.1.1. Measurements can include planned vs. actual technical performance or other scope performance measurements

1.5.3.2. Organizational process assets updates

1.5.3.2.1. Organizational process assets that may be updated include but are not limited to

1.5.3.3. Change requests

1.5.3.3.1. Analysis of scope performance can result in a change request to the scope baseline or other component of the PMP

1.5.3.4. Project management plan updates

1.5.3.4.1. – Scope baseline updates

1.5.3.4.2. – Other baseline updates

1.5.3.5. Project document updates

1.5.3.5.1. Project document that may be updated include but are not limited to

1.5.4. OVERVIEW

2. INTRODUCTION

2.1. PRODUCT SCOPE

2.1.1. Covers the required features of the product and clarifies the boundaries what is not included.

2.2. PROJECT SCOPE

2.2.1. is concerned with the work of the project, and again clarifies the boundaries of what is not included.

3. THE END