PMBOK 5th Edition Chapter 5

88 terms by jcj2mail 

Create a new folder

Advertisement Upgrade to remove ads

What the purpose of Project Management Scope Management Knowledge Area

to ensure that the project includes all the work required, and only the work required, to complete the project successfully (p103)

Product Scope

The features and functions that characterize a product, service, or result (p103)

Project Scope

The work that needs to be accomplished to deliver a product, service, or result with the specified features and functions (p103)

What are the Project Scope Management PROCESSES

1. Plan Scope Management
2. Collect Requirements
3. Define Scope
4. Create WBS
5. Validate Scope
6. Control Scope (p103)

Plan Scope Mangement

Project Scope managment process of creating a scope management plan that documents how the project scope will be defined, validated and controlled.

Collect Requirements

the Project Scope Management Process of determining, documenting and managing stakeholders needs and requirements to meet the project objectives (p103)

Define Scope

the Project Scope Management Process of developing a detailed description of the project and product (p103)

Create WBS

the Project Scope Management Process of subdividing project deliverables and project work into smaller, more manageable components (p103)

Validate Scope

the Project Scope Management Process of formalizing acceptance of the completed project deliverables (p103)

Control Scope

the Project Scope Management Process of monitoring the status of the project and product scope and managing changes to the scope baseline (p103)

Name the inputs to Plan Scope Management

1. Project management plan
2. Project charter
3. Enterprise environmental Factors
4. Organizational process assets

Definition Project management plan

Input to Plan Scope Mangement that is the approved subsidiary plans of the project management plan are used to create the scope management plan and influence the approach taken for planning scope and managing project scope.

Definition Project Charter

Input to Plan Scope Management that is used to provide the project context needed to plan the management processes. Provides high-level project description and product charactersistics from the SOW.

Definition Enterprise Environmental factors

Input to Plan scope management that may include:
-Oganization's culture
-Infrastructure
-Personnel administration
-Marketplace conditions

Organizational Process Assets

Input to Plan scope managment that can influence the plan scope management process include:
-policies and procedures
-Historical information and lessons learned knowledge base.

Name the Tools/Techniques of Plan Scope management

1. Expert Judgment
2. Meetings

Expert Judgment

Plan Scope Managment Tools/techniques that refers to input receivved from knowledgeable and experienced parties with specialized education, knowledge, skill, experience, or training in developing scope management plans

Meetings

Plan scope management tools/techniques where project eams may attend project meetings to develop the scope management plan. Attendees include, manager, sponsor, team members, stakeholders anyone else with responsibility for scope.

Name the Outputs of Plan Scope Management

1. Scope management plan
2. Requirements management plan

Scope Management Plan

Output of plan scope management that is a component of the project or program management plan that describes how the scope will be defined, developed, monitored, controlled, and verified. Input to 'Develop Project Management Plan' process.

Components of Scope Management Plan

- Process for preparing a detailed project scope statement
- Process that enables the creation of the WBS from project scope statement
-Process that establishes how the WBS will be maintained and approved
-Process that specifies formal acceptance fo completed project deliverables will be obtained
- Process to control how requests for changes to the project scope statement will be processed.

Requirements Management Plan

Output to Plan Scope Management that describes how requirements will be analyzed, documented and managed.

Componenets of the Requirements Management Plan

-How requirements will be planned, tracked and reported
- How changes to the product will be intitiated, analyzed, traced, tracked and reported as well as the authorization required to approve these changes
-Requirements prioritizzation process
-Product metrics that will be used and rationale for using them
-Traceability structure to reflect which requirement attributes will be captured on the matrix.

Scope Baseline

the approved detailed project scope statement and its associated WBS AND WBS Dictionary (p103)

Requirement

the quantified and documented needs and expectations of the sponsor, customer, and other stakeholders (p105)

Project Requirements

include business requirements, project management requirements, delivery requirements (p105)

Product Requirements

include information on technical requirements, security requirements, performance requirements

Name the inputs of the Collect Requirements Process

1 Project Charter
2 Stakeholder register

Name the tools/techniques of the of the Collect Requirements Process

1 Interviews
2 Focus groups
3 Facilitated workshops
4 Group Creativity
5 Group decision making techniques
6 Questionnaires and surveys
7 Observations
8 Prototypes

Name the outputs of the Collect Requirement Process

1 Requirements documentation
2 Requirements Management Plan
3 Requirements traceability matrix

Interviews

a formal or informal approach to discover information from stakeholders by talking to them directly (p107)

Focus Groups

the bringing together pre qualified stakeholders and subject matter experts to learn about their expectations and attitudes about a proposed product, service, or result (p107)

Facilitated Workshops

focused sessions that bring key cross-functional stakeholders together to define product requirements (p107)

Group Creativity

group activities that can be organized to identify project and product requirements (p108)

Brainstorming

a technique used to generate and collect multiple ideas related to project and product requirements (p108)

Nominal Group Technique

a technique that enhances brainstorming with a voting process used to rank the most useful ideas for further Brainstorming or for prioritization (p108)

Delphi Technique

a selected group of experts answer questionnaires and provide feedback regarding the responses from each round of requirements gathering (p108)

idea/mind mapping

ideas created through individual brainstorming are consolidated into a single map to reflect commonality and difference in understanding , and generate new ideas (p108)

Affinity Diagram

this technique allows large numbers of ideas to be sorted into groups for review and analysis (p108)

Group Decision Making Techniques

an assessment process of multiple alternatives with an expected outcome in the form of future actions resolution (p 108)

Unanimity

everyone agrees on a single course of action (p108)

Majority

Support from more than 50% of the members of the group (p108)

Plurality

the largest block in a group decides even if a majority is not achieved (p108)

Dictatorship

one individual makes the decision for the group (p108)

Questionnaires/Surveys

a written set of questions designed to quickly accumulate information from a wide number of respondents (p 109)

Observations

a direct way of viewing individuals in their environment and how they perform their jobs or tasks and carry out processes (p 109)

Prototypes

the method of obtaining early feedback on requirements by providing a working model of the expected product before actually building it (p 109)

Requirements Documentation

describes how individual requirements meet the business need for the project (p 109)
list all the project, technical, and other types of requirements that must be present for the project product, along with their acceptance criteria (p 124)

Requirements must be

unambiguous (measurable and testable), traceable, complete, consistent, and acceptable to key stakeholders (p 109)

Requirements Management Plan

documents how requirements will be analyzed , documented and managed throughout the project (p 110)

Requirements Traceability Matrix

a table that links requirements to their origin and traces them throughout the project life cycle (p 111)

Define Scope

the process of developing and detailed description of the project and product (p 112)

Name the inputs of the Define Scope process

1 Project Charter
2 Requirements Documentation
3 Organizational Process Assets

Name the tool/techniques of the Define Scope process

1 Expert judgement
2 Product Analysis
3 Facilitated Workshops

Name the outputs of the Define Scope process

1 Project scope statement
2 Project documentation updates

Alternatives Identification

a technique used to generate different approaches to execute and perform the work of the project (p 114)

Project Scope Statement

describes in detail the projects deliverables and the work required to create those deliverables (p 115)

Product Scope Description

Progressively elaborated the characteristics of the product, service, or result described in the project charter and requirements documentation (p 115)

Product Acceptance Criteria

Defines the process and criteria for accepting completed products, services, or results (p 115)

Project Deliverables

both the outputs that comprise the product or service of the project (p 115)

Project Exclusions

generally identifies what is excluded from the project (p 115)

Project Constraints

list and describes the specific project constraints associated with the project scope that limits the teams options (p115)

Project Assumptions

list and describe the specific project assumptions associated with the project scope and the potential impact o those assumptions if they prove to be false (p 116)

Create WBS

the process of subdividing project deliverables and project work into smaller more manageable components (p 116)

WBS

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 (p 116)

Work Packages

contained within the lowest levels of the WBS, can be scheduled, cost estimated, monitored and controlled (p 116)

Name the inputs of the Create WBS process

1 Project Scope Statement
2 Requirements Documentation
3 Organizational Process Assets

Name the tools/techniques of the Create WBS process

1 Decomposition

Name the outputs of the Create WBS Process

1 WBS
2 WBS Dictionary
3 Scope Baseline
4 Project Documents Updates

Decomposition

the subdivision of project deliverables into smaller, more manageable components until the work and deliverables are defined to the work package level (p 118)

WBS Dictionary

provides more detailed descriptions of the components in the WBS, including work packages and control accounts (p 121)

Name the component of the Scope Baseline

1 Project Scope Statement
2 WBS
3 WBS Dictionary (p 122)

Verify Scope

the process of formalizing acceptance of the completed project deliverables (p 123)

Name the inputs to the Verify Scope process

1. Project Management Plan
2. Requirements Documentation
3. Requirements Traceability Matrix
4. Validated Deliverables

Name the tools/techniques Verify Scope process

1. Inspection

Name the outputs of the Verify Scope process

1. Accepted deliverables
2. Change requests
3. Project document updates

Validated Deliverables

deliverables that have been checked for correctness by the Perform Quality Control Process (p 124)

Accepted Deliverables

deliverables that meet the acceptance criteria are formally signed off and approved by the customer or sponsor (p 125)

Control Scope

the process of monitoring the status of the project and product scope and managing changes to the scope baseline (p 125)

Project Scope Creep

uncontrolled changes (p 125)

Name the inputs to the Control Scope Process

1 Project Management Plan
2 Work Performance information
3 Requirements Documentation
4 Requirements Traceability Matrix
5 Organizational Process Assets

Name the tool/techniques of the Control Scope Process

1 Variance analysis

Name the outputs of the Control Scope Process

1 Work Performance measurements
2 Organizational Process assets Updates
3 Change request
4 Project Management Plan Updates
5 Project Document Updates

Scope Management Plan

describes how the project scope will be managed and controlled (p 126)

Change Management Plan

defines the process for managing change on the project (p 126)

Configuration Management Plan

defines those items that are configurable, those items that require formal change control, and the process for controlling changes to such items (p 126)

Requirements Management Plan

includes how requirements activities will be planned, tracked, and reported and how changes t the product, service, or result requirements will be initiated (p 127)

Variance Analysis

the use of project performance measurements to asses the magnitude of variation from the original scope baseline (p 127)

Please allow access to your computer’s microphone to use Voice Recording.

Having trouble? Click here for help.

We can’t access your microphone!

Click the icon above to update your browser permissions above and try again

Example:

Reload the page to try again!

Reload

Press Cmd-0 to reset your zoom

Press Ctrl-0 to reset your zoom

It looks like your browser might be zoomed in or out. Your browser needs to be zoomed to a normal size to record audio.

Please upgrade Flash or install Chrome
to use Voice Recording.

For more help, see our troubleshooting page.

Your microphone is muted

For help fixing this issue, see this FAQ.

Star this term

You can study starred terms together

NEW! Voice Recording

Create Set