5 - Scope

Front 1

Describe the "Project Scope Management" Knowledge Area.

Back 1

-The processes required to ensure that the project includes all the work required, and only the work required

-Defining and controlling what is and is not included in the project.

Front 2

What are the 5 processes included in the "Proj Scope Mgmt" knowledge area?

Back 2

1 Collect Requirements- defining and documenting stakeholders’ needs

2 Define Scope— Develop a detailed description of the project and product.
3 Create WBS— Subdivide project deliverables into smaller components.
4 Verify Scope—formalizing acceptance of the completed deliverables
5 Control Scope - Monitoring and managing changes to the scope baseline.

Front 3

What does "scope" refer to in the "Proj Scope Mgmt"? (2)

Back 3

1. Product scope. The features and functions that characterize a product, service, or result; and/or

2. Project scope. The work that needs to be accomplished to deliver a product, service, or result with the specified features and functions.

Front 4

Describe the "Collect Requirements" process in the Proj Scope Mgmt knowledge area.

Back 4

-Defining and documenting stakeholders’ needs to meet the project objectives (measurable)

-Requirements become the foundation of the WBS. Cost, schedule, and quality planning are all built upon these requirements.

Front 5

Name the 2 inputs to the "Collect Requirements" process in the Proj Scope Mgmt knowledge area.

Back 5

1 Project Charter - used to provide the high-level project requirements and high-level product description
2 Stakeholder Register - The stakeholder register is used to identify stakeholders that can provide information on project requirements.

Front 6

Name the 8 tools/techniques for the "Collect Requirements" process in the Proj Scope Mgmt knowledge area.

Back 6

1. Interviews with stakeholders
2. Focus groups
3. Facilitated Workshops
4. Group Creativity Techniques - brainstorming, Delphi technique, Affinity diagram, etc.
5. Group Decision Making Techniques
6. Questionnaires and Surveys
7. Observations
8. Prototypes

Front 7

Name the 3 outputs to the "Collect Requirements" process in the Proj Scope Mgmt knowledge area.

Back 7

1. Requirements documentation - describes how individual requirements meet the business need for the project.
2. Requirements management plan - documents how requirements will be analyzed, documented, and managed throughout the project.
3. Requirements traceability matrix - a table that links requirements to their origin and traces them throughout the project life cycle.

Front 8

What attributes must a requirement have to be acceptable?

Back 8

Unambiguous (measurable and testable), traceable, complete, consistent, and acceptable to key stakeholders.

Front 9

Describe the "Define Scope" process in the "Proj Scope Mgmt" k.a.

Back 9

- Define Scope is the process of developing a detailed description of the project and product.
- During planning, the project scope is defined and described with greater specificity as more information about the project is known.

Front 10

What are the 3 inputs for the Define Scope process in the Proj Scope Mgmt k.a.?

Back 10

1. The project charter provides the high-level project description and product characteristics. It also contains project approval requirements.
2. Requirements Documentation
3. Organizational Process Assets - Policies, procedures, and templates for a project scope statement

Front 11

What are the 4 tools/techniques for the Define Scope process in the Proj Scope Mgmt k.a.?

Back 11

1. Expert Judgment
2. Product Analysis
3. Alternatives Identification
4. Facilitated Workshops

Front 12

What are the 2 outputs for the Define Scope process in the Proj Scope Mgmt k.a.?

Back 12

1. Project scope statement - describes, in detail, the project’s deliverables and the work required to create those deliverables.
2. Project Document Updates

Front 13

What should the project scope statement include?

Back 13

- Product scope description
- Product acceptance criteria
- Project deliverables
- Project exclusions. Generally identifies what is excluded as from the project.
- Project constraints. i.e. predefined budget
- Project assumptions

Front 14

Describe the Create WBS process in the Project Scope Mgmt k.a.

Back 14

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

-Each descending level of the WBS representing an increasingly detailed definition of the project work.

-The WBS organizes and defines the total scope of the project, and represents the work specified in the current approved project scope statement.

Front 15

What are the 3 inputs to the Create WBS process?

Back 15

1. Project Scope Statement
2. Requirements Documentation
3. Organizational Process Assets

Front 16

What is the main tool/technique in the Create WBS process?

Back 16

Decomposition

Front 17

What are the 4 outputs to the Create WBS process?

Back 17

1. WBS -
2. WBS Dictionary - provides more detailed descriptions of the components in the WBS, including work packages and control accounts.
3. Scope baseline - a component of the project management plan.
4. Project Document Updates

Front 18

Describe the Decomposition tool/technique in the Create WBS process.

Back 18

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

The work package level is the lowest level in the WBS, and is the point at which the cost and activity durations for the work can be reliably estimated and managed.

Front 19

What are some of the activities involved in decomposition of work for the WBS?

Back 19

- Identifying and analyzing the deliverables and related work,
- Structuring and organizing the WBS,
- Decomposing the upper WBS levels into lower level detailed components,
- Developing and assigning identification codes to the WBS components, and
- Verifying that the degree of decomposition of the work is necessary and sufficient.

Front 20

Name 3 forms you can create a WBS

Back 20

1. Using phases of the project life cycle as the first level of decomposition, with the product and project deliverables inserted at the second level
2. Using major deliverables as the first level of decomposition
3. Using subprojects developed by organizations outside the project team, such as contracted work

Front 21

Name 3 components of the scope baseline.

Back 21

1. Project scope statement. The project scope statement includes the product scope description, the project deliverables and defines the product user acceptance criteria.
2. WBS. The WBS defines each deliverable and the decomposition of the deliverables into work packages.
3. WBS dictionary. The WBS dictionary has a detailed description of work and technical documentation for each WBS element.

Front 22

Describe the Verify Scope process in the Proj Scope Mgmt ka.

Back 22

-Verify Scope is the process of formalizing acceptance of the completed project deliverables. Verifying scope includes reviewing deliverables with the customer or sponsor

Front 23

Describe the 4 inputs to the Verify Scope process.

Back 23

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

Front 24

Describe the main tool/technique for the Verify Scope process.

Back 24

Inspection - includes activities such as measuring, examining, and verifying to determine whether work and deliverables meet requirements and product acceptance criteria. Inspections are sometimes called reviews, product reviews, audits, and walkthroughs. In some application areas, these different terms have narrow and specific meanings.

Front 25

Describe the 3 outputs to the Verify Scope process.

Back 25

1. Accepted Deliverables - Deliverables that meet the acceptance criteria are formally signed off and approved by the customer or sponsor.
2. Change Requests
3. Project Document Updates

Front 26

Describe the Control Scope process in the Proj Scope Mgmt ka.

Back 26

Control Scope is the process of monitoring the status of the project and product scope and managing changes to the scope baseline.

Front 27

Describe the 5 inputs to the Control Scope process.

Back 27

1. Project Management Plan - contains the following information that is used to control scope:
- Scope baseline. The scope baseline is compared to actual results to determine if a change, corrective action, or preventive action is necessary.
- Scope management plan. The scope management plan describes how the project scope will be managed and controlled.
- Change management plan. The change management plan defines the process for managing change on the project.
- Configuration management plan. The 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.
- Requirements management plan can includes how requirements activities will be planned, tracked, and reported and how changes to the product, service, or result requirements will be initiated.
2. Work Performance Information
3. Requirements Documentation
4. Requirements Traceability Matrix
5. Organizational Process Assets

Front 28

Describe the main tool/technique for the Control Scope process.

Back 28

Variance Analysis - Project performance measurements are used to assess the magnitude of variation from the original scope baseline.

Front 29

Describe the 5 outputs to the Control Scope process.

Back 29

1. Work Performance Measurements
2. Organizational Process Assets Updates
3. Change Requests
4. Project Management Plan Updates:
- Scope Baseline Updates.
- Other Baseline Updates
5. Project Document Updates

Front 30

Project scope mangement

Back 30

Processes required to ensure that the project includes all the work required and only the work required
Defining and controling what is and is not part of the project

Front 31

6 parts of scope management

Back 31

Plan scope management
Collect requirements
Define scope
Create WBS
Validate scope
Control Scope

Front 32

What are collect requriements?

Back 32

Process of defining and documenting stakeholders need to make the project objectives
–Defining and managing customer expectations

Front 33

What are some collect requirements tools?

Back 33

Interviews
Focus groups
Facilitated workshops
Group creativity techniques
Group decision making techniques
Questionnaires and surveys
Observations
Prototypes
Benchmarking
Context diagrams
Documents analysis

Front 34

Define scope

Back 34

In the planning stage the scope of the project and the product are defined in more details

Front 35

What is the WBS?

Back 35

Deliverable–orientated decomposition of the scope to actual tasks to be performed
Provides basis for planning and managing project schedules costs and changes
Several levels

Front 36

What are the approaches to an WBS?

Back 36

Analogus – best practices in simular projects
Org guidelines
Top down – Big to small
Bottom up – detailed to big picture
Phase based – based on project phases (feasibility, devlopment, implementation etc)

Front 37

What does the WBS provide the foundation for?

Back 37

Activity–responsibility matrix
Network diagram scheduling
Costing and budgets
Risk analysis
Organizational structure
Coordination of objectives
Control

Front 38

What are the WBS guidelines

Back 38

Ensure there is a work package to produce every required deliverable
The activites in a completed WBS can be re–arranged and it will still be valid
Invlove the project team in identifying task, estimating duration and resources
Each supplier can provide a WBS for its sub–project
Each WBS must reflect the nature to be performed

Front 39

List inputs to Scope Planning process

Back 39

1. Enterprise Environmental Factors
2 Organizational Process Assets
3 Project Charter
4 Preliminary Project Scope Statement
5 Project Management Plan

Front 40

List tools in Scope Planning process

Back 40

1 Expert Judgment
2 Templates, Forms, Standards

Front 41

List outputs to Scope Planning process

Back 41

1 Project Scope Management Plan

Front 42

List inputs to Scope Definition process

Back 42

1. Organizational Process Assets
.2 Project Charter
.3 Preliminary Project Scope Statement
.4 Project Scope Management Plan
.5 Approved Change Requests

Front 43

List tools in Scope Definition process

Back 43

1 Product Analysis
.2 Alternatives Identification
.3 Expert Judgment
.4 Stakeholder Analysis

Front 44

List outputs to Scope Definition process

Back 44

1 Project Scope Statement
2 Requested Changes
3 Project Scope Management Plan (Updates)

Front 45

List inputs to Create WBS process

Back 45

1 Organizational Process Assets
.2 Project Scope Statement
.3 Project Scope Management Plan
.4 Approved Change Requests

Front 46

List tools in Create WBS process

Back 46

1 Work Breakdown Structure Templates
2 Decomposition

Front 47

List outputs to Create WBS process

Back 47

1 Project Scope Statement (Updates)
.2 Work Breakdown Structure
.3 WBS Dictionary
.4 Scope Baseline
.5 Project Scope Management Plan (Updates)
.6 Requested Changes

Front 48

List the inputs of the Scope Verification process

Back 48

1 Project Scope Statement
.2 WBS Dictionary
.3 Project Scope Management Plan
.4 Deliverables

Front 49

List the tools of the Scope Verification process

Back 49

1 Inspection

Front 50

List the outputs of the Scope Verification process

Back 50

1 Accepted Deliverables
.2 Requested Changes
.3 Recommended Corrective Actions

Front 51

List the inputs of the Scope Control

Back 51

.1 Project Scope Statement
.2 Work Breakdown Structure
.3 WBS Dictionary
.4 Project Scope Management Plan
.5 Performance Reports
.6 Approved Change Requests
.7 Work Performance Information

Front 52

List the tools of the Scope Control

Back 52

1 Change Control System
.2 Variance Analysis
.3 Replanning
.4 Configuration Management System

Front 53

List the outputs of the Scope Control

Back 53

1 Project Scope Statement (Updates)
.2 Work Breakdown Structure (Updates)
.3 WBS Dictionary (Updates)
.4 Scope Baseline (Updates)
.5 Requested Changes
.6 Recommended Corrective Action
.7 Organizational Process Assets (Updates)
.8 Project Management Plan (Updates)

Front 54

How is scope varification different from quality control?

Back 54

-Scope verification differs from quality control in that scope verification is primarily concerned with acceptance of the deliverables, while quality control is primarily concerned with correctness of the deliverables and meeting the quality requirements specified for the deliverables.