5 - Scope Management

Question 1

8/80 Rule

Answer 1

A planning heuristic for creating the WBS.

Creating WBS must take no more than 80 hours, no fewer than 8 hours.

Question 2

Active observation

Answer 2

Observer interacts with the worker to ask questions and understand each step of the work being completed. Observer can even take part to better understand.

Question 3

Affinity Diagrams

Answer 3

Use it when stakeholders create a large # of ideas.

Can cluster similar number ideas together for further analysis.

Question 4

Alternatives Generation

Answer 4

Scope definition process of finding alternative solutions for the customer while considering the customer’s satisfaction, cost, how the customer may use the product in operations.

Question 5

Autocratic

Answer 5

Decision making process where one person decides for whole group.

Question 6

Brainstorming

Answer 6

Encourages participants to generate as many ideas about project requirements. No idea is judged or dismissed.

Question 7

Change control system (CCS)

Answer 7

Defines how changes to scope are managed.

Documented in scope management plan.

Question 8

Change management plan

Answer 8

Subsidiary plan defines how changes will be allowed and managed within the project.

Question 9

Code of accounts

Answer 9

Numbering system for each item in the WBS.

E.g. regulations chapter, section, etc.

Question 10

Configuration management plan

Answer 10

Subsidiary plan - defines how changes to the features and functions of the project deliverables will be monitored and controlled within the project.

Question 11

Context diagram

Answer 11

Shows relationship between elements of an environment.

e.g. would show networks, servers, workstation, and people that interact with the elements in that environment.

Question 12

Focus Groups

Answer 12

Moderator-lead requirements collection method to elicit stakeholder requirements.

Question 13

Functional Analysis

Answer 13

Study of functions wihtin a system, project, or product the project will be creating.

Studies the goal of the product, how it will be used, expectations the customer has/.

May also consider cost of product in operations (known as life cycle costing).

Question 14

Funding limit

Answer 14

Predetermined budget to project scope.

Could be a qualifier (e.g. +/- 10%)

Question 15

Interviews

Answer 15

1-1 requirements collection method.

Question 16

Majority

Answer 16

Voting process - greater than 50% votes wins.

Question 17

Mind mapping

Answer 17

Maps ideas to show relationships among requirements and differences between requirements.

Question 18

Nominal group technique

Answer 18

Generate as many ideas as possible, then ranked by voting process.

Question 19

Passive observation

Answer 19

Observer records information about work without interrupting worker.

aka invisible observer.

Question 20

Plurality

Answer 20

Voting method where largest group makes decision (even if less than 50% total vote).

Like a minority government.

Question 21

Product acceptance criteria

Answer 21

A scope statement component - focuses on the conditions and processes that are required for formal acceptance of the product.

Question 22

Product breakdown

Answer 22

Scope definition technique:

Breaks down product into hierarchal structure, much like WBC breaks down project scope.

Question 23

Project scope description

Answer 23

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

Question 24

Product Scope

Answer 24

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

Question 25

Project assumptions

Answer 25

A factor in planning process that is held to be true but not proven.

Question 26

Project boundaries

Answer 26

Clearly states what is included/excluded in the project.

Helps eliminate assumptions.

Question 27

Project contraints

Answer 27

Limits PMs options. e.g. cost limit 10k.

Question 28

Project objectives

Answer 28

Measurable goals that determine project acceptability to the project’s customer and overall success of project. e.g. cost, schedule, etc.

Question 29

Project requirements

Answer 29

Demands set by customer, regulations, or the performing organization that must exist for the projects deliverables to be acceptable.

Often prioritized (must, should, would like)

Question 30

Project scope

Answer 30

Defines all of the work, and only the required work, to complete the project objectives.

Question 31

Project scope management plan

Answer 31

Subsidiary PM plan.

Controls how scope will be defined, scope statement creates, WBS created, scope validation will proceed, and how scope controlled.

Question 32

Requirements documentation

Answer 32

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.

Question 33

Requirements management plan

Answer 33

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

Question 34

Requirements Traceability Matrix (RTM)

Answer 34

Table that maps all requirements throughout project all the way to their completion (lots of fields to track status).

Question 35

Schedule Milestones

Answer 35

Specific dates where phases should be completed.

Often a project constraint.

Question 36

Scope creep

Answer 36

undocumented, unapproved changes to the project scope.

Question 37

Scope validation

Answer 37

Formal inspection of project deliverables.

Leads to project acceptance.

Question 38

Stakeholder analysis

Answer 38

Scope definition process - PM team interviews the stakeholders and categorizes, prioritizes, and documents what the customer needs.

Demands quantification of stakeholder objectives. e.g. goals such as “good” “speedy” are not quantifiable.

Question 39

Systems analysis

Answer 39

Scope definition approach that studies and analyzes a system, its components, and the relatoinship of components within a system.

Question 40

Systems engineering

Answer 40

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 teh project’s goals and customer expectations. Systems engineering aims to balance the time and cost of the project in relation to the scope of the projcet.

Question 41

Unanimity

Answer 41

Group decision. All must agree

e.g. court ruling.

Question 42

Value analysis

Answer 42

Examines functions of the project’s product in relation to the cost of the features and functions. Where the grade of the product is in relatoinship to the cost of the product.

Question 43

Value engineering

Answer 43

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

Question 44

WBS dictionary

Answer 44

Companion document to the WBS. Defines all characteristics of each element within the WBS.

Question 45

WBS Template

Answer 45

prepopulated WBS for repetitive projects.

Question 46

Work Breakdown Structure (WBS)

Answer 46

Deliverables-oriented breakdown of the project’s scope.

Question 47

Work Package

Answer 47

Smallest item in the WBS.

Question 48

Work performance information

Answer 48

Status of the deliverable: work that has been started, finished, or yet to begin.