Project Scope Management

Question 1

Identify the six processes in the Project Scope Management knowledge area

Answer 1

Plan Scope Management
Collect Requirements
Define Scope
Create WBS
Validate Scope
Control Scope

Project scope management includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully. Managing the project scope is primarily concerned with defining and controlling what is and what is not included in the project

Question 2

The process of creating a scope management and requirements management plans that document how the project and product scope will be defined, validated, and controlled and how the requirements will be defined, managed and controlled.

Answer 2

Plan Scope Management Process

Outputs: Scope Management Plan, Requirements Management Plan

Question 3

A subsidiary plan of the project or program management plan that describes how the scope will be defined, developed, monitored, controlled, and validated.

Answer 3

Scope Management Plan

Question 4

A subsidiary plan of the project or program management plan that describes how requirements will be analyzed, documented, and managed.

Answer 4

Requirements Management Plan

Question 5

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

Answer 5

Collect Requirements Process

Requirements are the foundation of the project and must be comprehensive, including both product and project requirements

Key Outputs: Requirements Documentation, Requirements Traceability Matrix

Question 6

An elicitation technique that brings together prequalified stakeholders and subject matter experts to learn about their expectations and attitudes about a proposed product, service, or result.

Answer 6

Focus Group

Used to collect requirements, focus groups gather representative feedback under the guidance of a facilitator.

Question 7

Focused Sessions attended by key cross-functional stakeholders to define product requirements.

Answer 7

Facilitated Workshops

Example: joint application development or joint application design (JAD) sessions and quality function deployment (QFD) sessions. Facilitated workshops improve communication, commitment, and buy-in.

Question 8

Creativity technique that allows participants to think and contribute creatively with minimal structure or boundaries.

Answer 8

Brainstorming

Question 9

A technique that enhances brainstorming with a voting process used to rank the most useful ideas for further brainstorming or for prioritization.

Answer 9

Group Technique

Question 10

A technique used to consolidate ideas created through individual brainstorming sessions into a single map to reflect commonality and differences in understanding and to generate new ideas

Answer 10

Mind Mapping

Question 11

A technique that allows large number of ideas to be classified for review and analysis.

Answer 11

Affinity Diagram

AKA: “sticky note process”

Question 12

Techniques used to select a course of action from different alternatives.

Answer 12

Voting Techniques

Plurality - largest group decides, even if majority is not reached
Majority - more than half the group agrees
Unanimity - everyone agrees.

Question 13

Written sets of questions designed to quickly accumulate information from a large number of respondents.

Answer 13

Questionnaires and Surveys

Question 14

Watching end-users do their work. Helpful when identifying difficult to articulate requirements. Also called job-shadowing or ghosting.

Answer 14

Observations

Question 15

A method of obtaining early feedback on requirements by providing a working model of the expected product before actually building it

Answer 15

Prototype

Using prototypes aligns with and is a form of progressive elaboration

Question 16

__________ is the comparison of actual or planned products, processes, and practices to those of comparable organizations to identify best practices, generate ideas for improvement, and provide a basis for measuring performance.

Answer 16

Benchmarking

Question 17

A visual depiction of the product scope showing a business system (process, equipment, computer systems, etc.), and how people and other systems (actors) interact with it.

Answer 17

Context Diagram

Question 18

A description of how individual requirements meet the business need for the people.

Answer 18

Requirements Documentation

Serves as the basis and foundation for the project and is based on the gathered requirements. In agile/adaptive projects, the requirements are captured in the product backlog.

Question 19

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

Answer 19

Requirements Traceability Matrix

Requirements may also be traced to: project scope, product design, WBS deliverables, test strategy and scenarios, etc.

Question 20

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

Answer 20

Define Scope Process

The project scope statement includes clearly defining the in-scope and out-of-scope requirements and the project deliverables.

Question 21

The description of the project scope, major deliverables, assumptions, and constraints.

Answer 21

Project Scope Statement

Includes in-scope and out-of-scope requirements. The scope statement is a component of the scope baseline and may be progressively elaborated. Ideally, however, the scope is defines in as much detail as possible to minimize the occurrence of scope creep (unmanaged changes to the project scope).

In practice, many organizations refer to the scope statement as the “scope of work” or “statement of work”

Question 22

The process of subdividing project deliverables and project work into smaller, more manageable components.

Answer 22

Create WBS Process

The project deliverables are composed into work packages using a graphical, hierarchical structure. Along with the WBS, there should be a WBS dictionary providing the back-end details of the work packages.

Question 23

A technique used for dividing and subdividing the project scope and project deliverables into smaller, more manageable parts.

Answer 23

Decomposition

Is used to break the deliverables down into work packages (the lowest level of the WBS). Decomposition will also be used to break the work packages down into schedule activities in the Define Activities Process

Question 24

Used in developing the WBS. The total of the lower level work rolls up to the higher levels. Nothing is left out and no extra work is completed

Answer 24

The 100% Rule

Question 25

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

Answer 25

Control Account

May contain multiple work packages, but each work package can only align with one control account, demonstrating a one-to-many relationship. They are typically the 2nd level of the WBS.

Question 26

A hierarchical decomposition of the total scope of work to be carried out by the project team to create the required deliverables

Answer 26

Work Breakdown Structure (WBS)

The WBS is a component of the scope baseline

Question 27

The work defined at the lowest level of the WBS for which cost and duration can be estimated and managed.

Answer 27

Work Package

The deliverables are decomposed to the work package level on a WBS. The work package owner is able to estimate, manage, and control the work of the work package, The work packages will be decomposed into schedule activities on the project schedule.

Question 28

A document that provides detailed deliverable, activity, and scheduling information about each component in the WBS

Answer 28

WBS Dictionary

Is a component of the scope baseline

Question 29

The approved version of a scope statement, 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 29

Scope Baseline

Question 30

The uncontrolled expansion to product or project scope without adjustments to time, cost, and resources.

Answer 30

Scope Creep

Question 31

Formalizes acceptance of the completed project deliverables by the end-user, customer, or requesting party.

Answer 31

Validate Scope Process

Key output: Accepted Deliverables

Compare to Control Quality

Question 32

A set of conditions that is required to be met before deliverables are accepted

Answer 32

Accepted Deliverables

Question 33

Examination of a work product to determine whether it conforms to documented standards

Answer 33

Inspection (used in Validate Scope Process)

Question 34

The process of monitoring the status of the project and product scope and managing changes to the scope baseline

Answer 34

Control Scope Process

Question 35

A technique for determining the cause and degree of difference between the baseline and actual performance.

Answer 35

Variance Analysis

Question 36

An analytical technique that uses mathematical models to forecast future outcomes based on historical results.

Answer 36

Trend Analysis

Question 37

The performance data collected from controlling processes, analyzed in comparison with project management plan components, project documents, and other work performance information.

Answer 37

Work Performance Information