Planning Process Group: Integration Management & Scope Management

Question 1

The process group of processes necessary to establish the total scope of the effort, define and refine the objectives, and develop a course of action to obtain those objectives.

Answer 1

Planning Process Group

Question 2

Planning is an ___ process and may require revisiting one or both of the initiating processes.

Answer 2

iterative

Question 3

The process of defining, preparing, and coordinating all plan components and consolidating them into an integrated project management plan.

Answer 3

3.1 Develop Project Management Plan

Question 4

Documents how changes will be controlled; describes system to track & manage changes

Answer 4

Change Management Plan

Question 5

Outlines configurability of product features as well as project plans/documents;

Also defines the Configuration Management System which is part of the PMIS that tracks and manages changes to the deliverables (version control)

Answer 5

Configuration Management Plan

Question 6

Integrated scope-schedule-cost baselines

Answer 6

Performance measurement baseline

Question 7

Describes the product, service, or result development approach, such as predictive, iterative, agile, or a hybrid model

Answer 7

Development approach

Question 8

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

Answer 8

3.2 Plan Scope Management

Question 9

A document that describes how the scope will be defined, developed, monitored, controlled, and verified.

Answer 9

Scope Management Plan

Question 10

Document describing how requirements will be planned, tracked, and reported

Answer 10

Requirements Management Plan

Question 11

The process of determining, documenting, and managing stakeholder needs and requirements to meet objectives.

Answer 11

3.3 Collect Requirements

Question 12

Describes how individual requirements meet the business need.

Answer 12

Requirements Documentation

Question 13

Business and project objectives for traceability; business rules; and guiding principles.

Answer 13

Business requirements

Question 14

Requirements that Impacts other organizational areas, impacts to other entities.

Answer 14

Stakeholder requirements

Question 15

Functional and nonfunctional; support and training; quality standards

Answer 15

Solution requirements

Question 16

Levels of service, performance; milestone dates, contractual obligations, constraints, etc.

Answer 16

Project requirements

Question 17

Temporary capabilities during transition period

Answer 17

Transition requirements

Question 18

Identifies condition of criteria for successful completion of a deliverable

Answer 18

Quality requirements

Question 19

A project document used to record knowledge gained during a project so that it can be used in the current project and entered into the lessons learned repository.

Answer 19

Lessons Learned Register

Question 20

The knowledge gained during a project which shows how project events were addressed or should be addressed in the future for the purpose of improving future performance.

Answer 20

Lessons Learned

Question 21

A store of historical information about lessons learned in projects.

Answer 21

Lessons Learned Repository

Question 22

A grid that links product requirements from their origin to the deliverables that satisfy them.

Answer 22

Requirements Traceability Matrix

Question 23

The process of developing a detailed description of the project and product.

Answer 23

3.4 Define Scope

Question 24

Describes in detail the deliverables (product scope); sets forth constraints and assumptions along with how deliverables will be created (project scope)

Answer 24

Project Scope Statement

Question 25

Process of subdividing (decomposing) the project deliverables and project work into smaller, more manageable components

Answer 25

3.5 Create WBS

Question 26

Breaking project work and deliverables down into smaller, more manageable components

Answer 26

Decomposition

Question 27

The approved version of a scope statement, work breakdown structure (WBS), and its associated WBS dictionary, that can be changed using formal change control procedures and is used as a basis for comparison to actual results.

Answer 27

Scope Baseline

Question 28

The sum of the products, services, and results to be provided as a project.

Answer 28

Scope

Question 29

A list of requirements and the work required for the product are written in the form of user stories, they are estimated by scale and prioritized by value to the sponsoring organization.

Answer 29

Scope Decomposition using a Product Backlog

(Originated in the Agile development environment)

Question 30

Hierarchical decomposition of the total scope of work to be performed

Answer 30

WBS

Question 31

Provides detailed information about the deliverables, activities, cost and scheduling information, schedule activities, resources, quality requirements, milestones, etc.

Answer 31

WBS Dictionary

Question 32

A management control point where scope, budget, actual cost and schedule are integrated and compared to earned value for performance measurement.

Answer 32

Control Account (WBS)

Question 33

WBS component below the control account and above the work package level, with known work content but without detailed schedule activities; especially useful in agile environments.

Answer 33

Planning Package (WBS)

Question 34

Work defined at the lowest level of the WBS, for which cost and duration can be estimated and managed (one step removed from an activity list, which is considered a separate document)

Answer 34

Work Package (WBS)

Question 35

Any numbering scheme used to uniquely identify each component of the WBS

Answer 35

Code of Accounts (WBS)

Question 36

A list detailing all accounts used by the organization to identify areas of expenditures (not part of the WBS itself)

Answer 36

Chart of Accounts (WBS)