Chapter 5 Project Scope Management Flashcards

1
Q

Product Scope

A

The features + functions that characterize a product, service, or result

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Project Scope

A

The work performed to deliver a product, service, or result with the specified features and functions.

Sometimes includes product scope

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Validate Scope

A

Process of formalizing acceptance of the completed project deliverables

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Requirements Management

A

AKA Business Analysis

Starts w/ needs assessment

Documenting, eliciting, and managing Stakeholder requirements happen in the the Project Scope Mgt process

Ends with requirements closure, which transitions the product, service or result of the recipient

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Adaptive or Agile

A

Deliberately spend less time trying to define scope in early stages and spend more time establishing process for it’s ongoing discovery and refinement.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Project Scope Management

A

Ensure that the project includes all the work required and only the work required to complete the project completely.

Documents how the project and product scope will be defined, validated and controlled.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Alternative Analysis

A

The evaluation of the different choices available to achieve a particular project management objective. It is an analytical comparison of different factors like operational cost, risks, effectiveness as well as the shortfalls in an operational capability

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Collect Requirements

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Affinity Diagram

A

Allows large numbers of ideas to be classified into groups for review and analysis.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Mind Mapping

A

Consolidates ideas using individual brainstorming sessions into a single map to reflect commonality and differences in understanding and generating new ideas

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Nominal Group Technique

A

Enhances brainstorming with a voting process used to rank the most useful ideas for further brainstorming or prioritization.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

User Stories

A

Short descriptions of required functionality often developed during a requirements workshop. Describe the stakeholders role, who benefits from the feature role, what the stakeholder needs to accomplish and the benefit to the stakeholder.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Requirements Traceability Matrix

A

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

Provides structure for managing changes to product scope.

Provides means to track throughout the project life cycle that requirements approved in the requirements documentation are delivered at the end of the project

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Define Scope

A
  • A detailed description of the project or product
  • Selects the final project requirements from the collect requirements process.
  • Can be highly iterative. Scope determined one iteration at a time
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Product Analysis

A
  • Used to define products + services
  • Asking questions about a product or service and forming answers to describe the use, characteristics, and other relevant aspects about what will be delivered.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Project Scope Statement

A
  • Description of the project scope, deliverables, assumptions, constraints.
  • Documents the entire scope. Project + Product scope
  • Project team able to perform more detailed planning
17
Q

WBS

Work Breakdown Structure

A

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

Key benefit is it provides the framework of what has to be delivered.

A hierarchal decomposition of the total scope of work to be carried out by the team to meet project objectives.

18
Q

Decomposition

A

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

Can be created thru various ways:

  • Top Down - use org specific guidelines and WBS templates
  • Bottom Up - Used to subgroup components
19
Q

WBS
Control Account
Planning Package

A

Control Account - A management control point where scope, budget and schedule are integrated and compared to the earned value for performance measurement.

Planning Package - A WBS component below the control account and above the work package with known work content but without scheduled activities

20
Q

WBS

Work Package

A

Lowest level of the WBS with unique identifiers

The identifiers provide a structure for the hierarchal summation of costs, schedule, and resourcing

21
Q

WBS Dictionary

A

A doc that provides detailed deliverables activity and schedule info about each component in the WBS

Most info in WBS Dictionary is created by other processes and added to this doc at a later stage

  • Resources
  • Schedule Milestones
  • Estimates
  • Quality Req’s
  • Acceptance Criteria
22
Q

Control Scope

A

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

Key Benefit: Scope baseline is maintained throughout the project.

Ensures all required changes are processed through integrated change control

23
Q

Scope Creep

A

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