5.0 Project Scope Management Flashcards

1
Q

A planning heuristic for creating the WBS. The rule states that the work package in a WBS must take no more than 80 hours of labor to create and no fewer than 8 hours of labor to create

A

8/80 rule

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

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

A

Active observation

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

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

A

affinity diagrams

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

A scope definition process of finding alternative solutions for the project customer while consindering the customer’s satisfaction, the cost of the solution, and how the customer may use the product in operations.

A

Alternatives generation

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

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

A

Autocratic

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

This approach encourages participants to generate as many ideas as possible about the project requirements. No idea is judged or dismissed during this session.

A

Brainstorming

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

Documented in the scope management plan, this system defines how changes to the project scope are managed and controlled

A

change control system (CCS)

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

A numbering system for each item in the WBS. The PMBOK is a good example of a code of accounts as each chapter and its subheadings follow a logical numbering scheme. For example, PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOK.

A

Code of Accounts

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

These diagrams show the relationship between elements of an environment. For example, this diagram would illustrator the networks, servers, workstations, and people that interact with the elements of the environment

A

Context diagram

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

A moderator-led requirements collection method to elicit requirements from stakeholders

A

Focus groups

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

This is the study of the functions within a system, project, or what’s more likely in the 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 the customer has of the product once it leaves the project and moves into operations. This analysis may also consider the cost of the product in operations, which is known as life-cycle costing.

A

Functional Analysis

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

Most projects have a determined budget in relation to the project scope. There may be a qualifier on this budget, such as -/+ 10% based on the type of cost estimate created.

A

Funding limit

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

a requirements collection method used to elicit requirements from stakeholders in a 1:1 conversation.

A

Interviews

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

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

A

mind mapping

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

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

A

nominal group technique

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

the observer records information about the work being completed without interruping the process; sometimes called the invisible observer.

think of a new hire going on a preceptorship

A

passive observation

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

a group - decision method where the largest part of the group makes the decision when it’s less than 50% of the total. Consider 3 or 4 factions within the stakeholders

A

Plurality

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

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.

A

Product acceptance criteria

19
Q

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

A

Product breakdown

20
Q

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

A

product scope description

21
Q

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

A

Product scope

22
Q

This is a factor in the planning process that is held to be true but not proven to be true.

A

Project assumptions

23
Q

this clearly states what is included with the project and what’s excluded from the project. This helps to eliminate assumptions between the project management team and the project customer

A

Project boundaries

24
Q

This is anything that limits the PM’s options. Consider a predetermined budget, deadline, resources, or materials the project manager must use within the project – these are all examples.

A

Project constraints

25
Q

These are the measurable goals that determine a project’s acceptability to the project customer and the overall success of the project. They often include the cost, schedule, technical requirements, and quality demands.

A

Project objectives

26
Q

These are the demands set by the customer, regulations, or the performing organization that must exist for the project deliverables to be aceptable. Requirements are often prioritized in a number of ways, from “must have” to “should have” to “would like to have.”

A

Project requirements

27
Q

This defines all of the work, and only the required work, to complete the project objectives

A

project scope

28
Q

This project management subsidiary plan controls how the scope will be defined, how the project scope statement will be created, how the WBS will be created, how scope validation will proceed, and how the project scope will be controlled throughout the project.

A

Project scope management plan

29
Q

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

A

Requirements documentation

30
Q

The subsidiary plan defines how changes to the project requirements will be permitted, how requirements will be tracked, and how changes to the requirements will be approved.

A

Requirements management plan

31
Q

A table that maps the requirements throughout the project all the way to their completion.

A

Requirements traceability matrix (RTM)

32
Q

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

A

Schedule milestones

33
Q

undocumented, unapproved changes to the project scope.

A

Scope creep

34
Q

The formal inspection of the project deliverables, which leads to project acceptance

A

scope validation

35
Q

A scope definition process where the project mgmt team interviews the stakeholders and categories, prioritizes, and documents what the project customer wants and needs. the analysis is to determine, quantify, and prioritize the interests of the stakeholders. This demands quanitifcation of stakeholder objectives; goals such as “good”, “satisfaction”, and “speedy” are not quantifiable

A

Stakeholder analysis

36
Q

a scope definition approach that studies and analyzes a system, its components, and the relationship of the components within the system

A

systems analysis

37
Q

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

A

Systems engineering

38
Q

A group decision method where everyone must be in agreement

A

unanimity

39
Q

As with value engineering, this approach examines the functions of the project’s product in relation to the cost of the features and functions. this is where, to some extent, the grade of the product is in relationship to the cost of the product.

A

value analysis

40
Q

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

A

value engineering

41
Q

A WBS companion document that defines all of the characteristics of each element within the WBS

A

WBS dictionary

42
Q

A prepopulated WBS for reptitive projects. Previous project’s WBS are often used as templates for current similar projects.

A

WBS template

43
Q

The smallest item in the WBS.

A

work package

44
Q

Status of the deliverables: the work that’s been started, finished, or has yet to begin

A

Work performance information