CHAPTER 5 - MANAGING PROJECT SCOPE Flashcards

1
Q

8/80 RULE

A

Planning method to create WBS. WP in a WBS should not take more than 80 and less than 8 hours of labor to create

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

ACTIVE OBSERVATION

A

Interact with worker, ask questions understand each step of work being completed. Sometimes even assist doing the work

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

AFFINITY DIAGRAMS

A

Cluster large number of similar ideas together for further analysis

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

ALTERNATIVES GENERATION

A

Scope definition by finding alternative solutions while considering cost, customer satisfaction, usage in operation

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

AUTOCRATIC

A

Decision making. Only one individual makes the decision

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

BRAINSTORMING

A

Generate as many ideas as possible about the project requirements. No ideas judged or dismissed.

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

CHANGE CONTROL SYSTEM (CCS)

A

Documented in scope management plan. Defines how changes to the project scope are managed and controlled.

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

CHANGE MANAGEMENT PLAN

A

A subsidiary plan that defines how changes will be allowed and managed within the project

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

CODE OF ACCOUNTS

A

Numbering system for each item in the WBS.

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

CONFIGURATION MANAGEMENT PLAN

A

Defines how features and functions to the deliverables will be monitored and controlled in the project

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

CONTEXT DIAGRAM

A

Shows relationship between elements of an environment and how they interact. E.g. server structure and user interaction

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

FOCUS GROUPS

A

Moderator led requirements collection method with SH

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

FUNTIONAL ANALYSIS

A

Study of functions in a system, project, product.
Studies goal of the product, how it will be used, expectations towards the product once it moves into operation. Also considers life cycle costing.

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

FUNDING LIMIT

A

Budget is determined in relation to project scope. Including qualifiers such as +-10%

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

INTERVIEWS

A

Requirements collection method. One on one conversations with interviewers

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

MAJORITY

A

Group decision method. More than 50% must agree

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

MIND MAPPING

A

Maps ideas to show the relationship among requirements. Can be reviewed to identify new solutions or rank the identified requirements

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

NOMINAL GROUP TECHNIQUE

A

Technique similar to brainstorming. Create as many ideas as possible and then rank them through voting.

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

PASSIVE OBSERVATION

A

Observer records information about work being completed without interrupting the process.

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

PLURALITY

A

Group decision method. Largest part of the group makes the decision. Even I’d less than 50%

21
Q

PRODUCT ACCEPTANCE CRITERIA

A

Project scope statement component that defines conditions and process for formal acceptance of the product

22
Q

PRODUCT BREAKDOWN

A

Scope definition technique that breaks down the product into a hierachacle structure similar to WBS for deliverables and project scope

23
Q

PRODUCT SCOPE

A

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

24
Q

PRODUCT SCOP3 DESCRIPTION

A

Narrative description of what the project is creating as a deliverable to the customer

25
Q

PROJECT ASSUMPTIONS

A

A factor in the planning process that is believed to be true but not proven to be true

26
Q

PROJECT BOUNDARY

A

States what is included and what is excluded from the project scope. Helps eliminate assumption between the PM, the team and the customer

27
Q

PROJECT BOUNDARY

A

States what is included and what is excluded from the project scope. Helps eliminate assumption between the PM, the team and the customer

28
Q

PROJECT CONSTRAINT

A

Anything that limits the project managers options. Budget, deadlines, resources.

29
Q

PROJECT OBJECTIVES

A

Goals that determine projects acceptability to the customer and overall success. Often include cost, schedule, technical requirements and quality demands.

30
Q

PROJECT REQUIREMENTS

A

Demands set by customer, regulations or the performing organization that must exist for the project deliverable to be acceptable.
Can be prioritized from “must have” “should have” “would like to have”.

31
Q

PROJECT SCOPE

A

Defines all the work and only the required work to complete the objectives.

32
Q

PROJECT SCOPE MANAGEMENT PLAN

A

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

33
Q

REQUIREMENTS DOCUMENTATION

A

Documentation of what stakeholders expect in the project that defines all of the requirements that must be present dor the work to be acceptable by the SH

34
Q

REQUIREMENTS MANAGEMENT PLAN

A

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

35
Q

REQUIREMENTS TRACEBILITY MATRIX

A

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

36
Q

SCHEDULE MILESTONES

A

Specific dates established by the customer that states when phases of the project should be completed. Often treated as project constraints

37
Q

SCOPE CREEP

A

Undocumented, unapproved changes to the project scope

38
Q

SCOPE VALIDATION

A

Formal inspection of the project deliverables, which leads to project acceptance.

39
Q

STAKEHOLDER ANALYSIS

A

Scope definition process. PT interviews the SH and categories, prioritizes and documents what the project customer wants and needs. The analysis determines, quantities and prioritizes the interests of the stakeholders. Requires quantification of SH objectives. For example satisfactory is not quantifiable.

40
Q

SYSTEMS ANALYSIS

A

Scope definition approach that studies and analyzes a system , it’s components and the relationship of the components within the system

41
Q

SYSTEMS ENGINEERING

A

Project scope statement creation process that studies how a system should work, designs and creates a system modela ND enacts the working system based on the project goals and customer expectation.
Aims to balance the time and cost of the project in relation to the scope of the project.

42
Q

UNANIMITY

A

A group decision method in which everyone must be in agreement

43
Q

VALUE ANALYSIS

A

Examines the functions of the projects product in relation to the cost of the features and functions. The grade of the product is in relation to the cost of the product.

44
Q

VALUE ENGINEERING

A

Approach to project scope statement creation. 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.

45
Q

WBS DICTIONARY

A

Defines all of the characteristics of each element within the WBS

46
Q

WBS template

A

Repopulate WBS for repetitive projects. Often using previous projects WBS as templates for current, similar projects

47
Q

WORK PACKAGE

A

Smallest item in the WBS

48
Q

WORK PERFORMANCE INFORMATION

A

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