SCOPE MANAGEMEN

Question 1

Collect Requirements Process Purpose

Answer 1

Gather all stakeholders’ requirements.

Question 2

Well-Defined Requirements

Answer 2

Measurable, clear, and logical.

Question 3

Requirements Traceability Matrix

Answer 3

Ensures all requirements are met and linked to project needs.

Question 4

Role of Requirements Traceability Matrix

Answer 4

Link requirements to project objectives.

Question 5

Facilitated Workshops (when collecting requirements)

Answer 5

Bring stakeholders together to discuss and identify requirements.

Question 6

Dealing with Competing Requirements

Answer 6

Use interpersonal and team skills for resolution.

Question 7

Ranking Requirements

Answer 7

Prioritize based on relevance to project constraints and scope.

Question 8

Outcome of Collect Requirements Process

Answer 8

Creation of the Requirements Document.

Question 9

Data Gathering for Large Groups

Answer 9

Utilize questionnaires and surveys.

Question 10

Affinity Diagram Use

Answer 10

Categorize and identify new requirements.

Question 11

Define Scope Process Aim

Answer 11

Create a detailed description of the high-level scope.

Question 12

Stakeholder Register

Answer 12

Contains information about stakeholders and their major requirements.

Question 13

Adaptive Environment Scope Handling

Answer 13

Scope refined with each iteration.

Question 14

Scope Baseline Components

Answer 14

Project Scope Statement, WBS Dictionary, and WBS.

Question 15

Revisions in Requirements Documentation

Answer 15

Triggered by gathering new requirements.

Question 16

Purpose of WBS

Answer 16

Break down project into manageable pieces.

Question 17

Scope Creep Definition

Answer 17

Uncontrolled expansion of project scope without proper change control.

Question 18

Preventing Scope Creep with WBS

Answer 18

Defines project boundaries clearly.

Question 19

WBS Dictionary Purpose

Answer 19

Prevent Scope Creep and provide detailed Work Package information.

Question 20

Uncontrolled Scope Changes

Answer 20

Leads to Scope Creep.

Question 21

Execution According to Scope Baseline

Answer 21

In predictive environments, execute exactly as defined.

Question 22

Creating the WBS

Answer 22

Responsibility of the Project Manager.

Question 23

Exclusion from WBS

Answer 23

Work item considered out of scope.

Question 24

Modifying WBS from Other Projects

Answer 24

To match your project’s needs.

Question 25

WBS Non-Inclusion

Answer 25

Does not show dependencies between activities.

Question 26

Validate Scope Process Purpose

Answer 26

Obtain customer acceptance of interim deliverables.

Question 27

Importance of Requirements Traceability Matrix in Validate Scope

Answer 27

Determines deliverable readiness for delivery.

Question 28

Quality Control vs. Validate Scope

Answer 28

Quality Control is internal; Validate Scope involves customer validation.

Question 29

Validate Scope Formal Validation

Answer 29

Ensures customer satisfaction with deliverables.

Question 30

Non-Passing Deliverable in Quality Control

Answer 30

Create a change request for Integrated Change Control.

Question 31

Close Project or Phase

Answer 31

Involves obtaining final product acceptance from customer.

Question 32

Outcome of Validate Scope Process

Answer 32

Verified Deliverables.

Question 33

Scope Management Plan and Requirements Documentation

Answer 33

Essential for meeting customer validation.

Question 34

Quality Control in Validate Scope

Answer 34

Ensures deliverables are ready for customer delivery.

Question 35

Customer Non-Validation of Deliverable

Answer 35

Leads to creation of a change request.

Question 36

Control Scope Process

Answer 36

Measure work against the scope baseline.

Question 37

Data Analysis in Control Scope

Answer 37

Use Variance and Trend Analysis for corrective actions.

Question 38

Additional Documents for Effective Control Scope

Answer 38

Requirements Documentation and Requirements Traceability Matrix.

Question 39

Handling Scope Misalignment

Answer 39

Create a Change Request to address variance.

Question 40

Scope Changes in Adaptive Environment

Answer 40

Normal and expected.

Question 41

Focus of Agile Scope Management

Answer 41

Adapting to scope changes throughout the project.

Question 42

Project Manager's Role in Controlling Scope

Answer 42

Monitor scope and prevent unnecessary changes.

Question 43

Deliverable Production in Adaptive Environment

Answer 43

Incrementally throughout the project life cycle.

Question 44

Business Case Document

Answer 44

Defines business value and project objectives.

Question 45

Product Roadmap in Agile

Answer 45

Illustrates high-level plan of feature delivery.

Question 46

Project Charter in Agile

Answer 46

Defines high-level vision, mission, and success criteria.