Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

CAPM Exam Prep > Chapter 5: Project Scope Management > Flashcards

Chapter 5: Project Scope Management Flashcards

1
Q

Project Scope Management Processes

A 
PLANNING
1. Plan Scope Management
2. Collect Requirements
3. Define Scope
4. Create WBS
MONITORING AND CONTROLLING
5. Validate Scope
6. Control Scope
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Plan Scope Management

A

It is the process of creating a scope management plan that 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
3
Q

Collect Requirements

A

It is the process of determining, documenting and managing stakeholder needs and requirements to meet the objectives.

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

Scope Management Plan

A

It is a component of the project management plan that describes how the scope will be defined, developed, monitored, controlled and validated.

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

Requirements Management Plan

A

It is a component of the project management plan that describes how a project and product requirements will be analyzed, documented and managed

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

Joint Application Design/Development

A
  • Used in the software industry
  • A facilitation technique
  • Brings the business SMEs and development team to gather requirements and improve the software development process
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Quality Function Deployment

A
  • Used in Manufacturing Industry
  • A facilitation technique
  • Helps determine the critical characteristics of a new product development
  • Starts by collecting customer needs, AKA VOC (Voice of Customer)
  • These needs are then objectively sorted and prioritized and goals are set to achieve them
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

User Stories

A
  • A facilitation technique
  • Short, textual description of the required functionality
  • Often developed during the requirements workshop
    It describes
    1. Stakeholder role
    2. Who benefits from the feature
    3. What stakeholder needs to accomplish
    4. Benefits of stakeholders
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Prototyping

A

Method of obtaining early feedback on the requirement by providing a model of the expected product before actually building it.

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

Storyboarding

A

It is a prototyping technique showing a sequence or navigation through a series of images and illustrations.

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

Requirements Documentation

A

Describes how individual requirements meet the business needs of the project.

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

Requirements Traceability Matrix

A

It is a grid that links product requirements from their origin to their deliverables that satisfy them.
Acts as a means to track requirements throughout the project lifecycle thus ensuring that requirements mentioned 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
13
Q

Define Scope

A

A process of defining a detailed description of a project and product.

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

Project Scope Statement

A

Description of the project scope, major deliverables and exclusions

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

Create WBS

A

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

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

Work Packages

A

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

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

Decomposition

A

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

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

Scope Baseline

A

The approved version of Scope statement, WBS and WBS dictionary, which can be changed only through formal change control procedures and is used as a basis for comparison

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

WBS

A

Is the hierarchical decomposition of the total scope of the work to be carried out by the project team to accomplish the project objectives and create the project deliverables.
Each descending level of the WBS represents an increasingly detailed definition of the project work

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

Control Account

A

It is a management control point where scope, budget and schedule are integrated and compared with the earned value for performance measurement

  • One work package is assigned to one control account
  • One control account may have 2 or more work packages assigned to it
  • It may include one of more planning packages
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Planning package

A

It is a work breakdown structure below the control account and above the work package with known work content but without the detailed schedule

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

WBS dictionary

A

Is a document that provides detailed deliverable, scope and scheduling information about each component in the WBS

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
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
24
Q

Control Scope

A

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

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

8/80 Rule

A

A planning heuristic for creating the WBS. It states that work packages in a WBS should take no more than 80 hours of labour to create and no fewer than 8 hours of labour to create

26
Q

Active Observation

A

The observer interacts with the worker to ask questions and understand each step of the work being completed. In some cases, the observer could serve as an assistant in doing the work

27
Q

Affinity Diagrams

A

When stakeholders create a large number of ideas, you can create an affinity diagram to cluster similar ideas together for further analysis

28
Q

Alternatives generation

A

A scope definition process of finding an alternative solution for the project customer while considering the customers’ satisfaction, the cost of the solution and how customers may use the product in operations

29
Q

Autocratic

A

A decision method where only one individual makes the decision for the group

30
Q

Brainstorming

A

This approach encourages as many ideas as possible about the project requirements. No idea is judged or dismissed during the brainstorming process.

31
Q

Change Control System (CCS)

A

Documented in the scope management plan.

This system defines how changes in a scope management plan are managed and controlled

32
Q

Code of Accounts

A

A numbering system for each items in WBS

33
Q

Context Diagram

A

These diagrams show the relationships between elements of an environment

34
Q

Focus groups

A

A moderation-let requirements collection method to elicit requirements from stakeholders

35
Q

Functional Analysis

A
  • This is the study of functions within a system, project or what more likely in a project scope statement, the product the project will be creating.
  • Functional analysis studies the goals of the product, how the product will be used and the expectations that the customer has of the product once it leaves the project and moves into operations
  • Functional analysis may also consider the cost of the products in operations which is known as life-cycle costing
36
Q

Funding Limit

A

Most projects have a determined budget in relation to the project scope. There may be a qualifier on this budget, such as plus or minus 10 percent based on the type of cost estimate created

37
Q

Interviews

A

A requirements collection method to elicit requirements from stakeholders in a one to one conversation

38
Q

Majority

A

A group decision method where more than 50 percent of the group must be in agreement

39
Q

Mind Mapping

A

This approach maps ideas to show the relationship among requirements and differences between requirements. The map can be reviewed to identify new solutions or to rank identified requirements

40
Q

Nominal Group Technique

A

As with brain storming participants are encouraged to generate as many ideas as possible, but the suggested ideas are ranked by a voting process

41
Q

Passive Observer

A

The observer records information about the work being completed without interrupting the process
- sometimes called the invisible observer

42
Q

Plurality

A

A group-decision method where the largest part of the group makes the decision when its less than 50% of the total

43
Q

Product Acceptance Criteria

A

This project scope statement component works with the project requirements but focuses specifically on the product and what the conditions and processes are for formal acceptance of the product

44
Q

Product Breakdowm

A

A scope definition technique that breaks down a product into hierarchical structure, much like a WBS breaks down a project scope

45
Q

Product Scope Definition

A

This is a narrative description of what the project is creating as a deliverable for the project customer

46
Q

Product Scope

A

Defines the product or service that will come as a result of completing the project. It defines the features and function that characterize the product.

47
Q

Project Boundary

A

A project boundary clearly states what is included in the project and what is excluded from the project.
This helps eliminate assumption between the project management team and the project customer

48
Q

Project Constraint

A

A constraint is anything that limits the project managers’ options. Examples: Predetermined budget, deadline, materials or resources the project manager must use within the project

49
Q

Project Objectives

A

These use measurable goals that determine a projects acceptability to the project customer and overall success of the project. Objectives often include the cost, schedule, technical requirements and quality demands

50
Q

Project Requirements

A

These are demands set by the customer, regulations or performing organization that must exist for project deliverables to be acceptable

51
Q

Project Scope

A

Defines the scope and only the required work to complete the project objectives

52
Q

Project Scope Management Plan

A

This project management subsidiary plan control

  1. how the scope will be defined
  2. How the project scope statement will be created
  3. how the WBS will be created
  4. how the scope validation will proceed
  5. how the project scope will be controlled throughout the project
53
Q

Requirements Documentation

A

This document of what the stakeholders expected in the project defines all the requirements that must be present for the work to be accepted by the stakeholders

54
Q

Requirements Management Plan

A

This subsidiary plan defines

  • how changes to the project requirements will be permitted
  • how requirements will be tracked
  • how changes to the requirements will be approved
55
Q

Schedule Milestones

A

The project customer may have specific dates when phases of the project should be completed. These milestones are often treated as project constraints.

56
Q

Scope Validation

A

The formal inspection of project deliverables which lead to project acceptance

57
Q

Stakeholder Analysis

A

A scope definition process where the project management team interviews the stakeholders and categorizes, prioritizes and documents what the project customer wants and needs. The analysis is to determine, quantify and prioritize the interests of the stakeholders. Stakeholder analysis demands quantification of stakeholder objectives: goals such as “good”, “satisfaction” and “speedy” arent quantifiable

58
Q

System Analysis

A

A scope definition approach that studies and analyses a system, its components and the relationships of components within the system

59
Q

Systems Engineering

A

This project scope statement creation process studies how a system should work, designs and creates a system model and then enacts the working system based on the projects goals and the customer expectations. Systems engineering aims to balance the time and cost of the project in relation to the scope of the project

60
Q

Value Analysis

A

This approach examines the functions of the projects products in relation to the cost of the features and functions. This is where, in some extent, the grade of the product is in relation to the cost of the product.

61
Q

Value Engineering

A

This approach to product scope statement creation attempts to find the correct level of quality in relation to a reasonable budget for project achieving an acceptable performance of the product

62
Q

WBS template

A

A prepopulated WBS for repetitive projects. Previous projects WBS are often used as a template for current situations

CAPM Exam Prep (13 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions