Project Scope Management

Question 1

define product scope

Answer 1

the features and functions that characterize a product, service, or result.

Question 2

define project scope

Answer 2

the work performed to deliver a product, service, or result w the specified features and functions. the term is sometimes viewed as including product scope.

Question 3

define scope baseline

Answer 3

the approved version of a scope statement, work breakdown structure (WBS), and its associated WBS dictionary, that can be changed only through formal change control procedures and is used as a basis for comparison.
any change after this has been agreed upon requires a change request.

Question 4

what is WBS?

Answer 4

work breakdown structure

Question 5

define scope change

Answer 5

any change to the project scope. a change almost always requires an adjustment to the project cost or schedule.

Question 6

define scope creep

Answer 6

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

Question 7

define scope management plan

Answer 7

a component of the project or program management plan that describes how the scope will be defined, developed, monitored, controlled, and verified.

Question 8

define requirements management plan

Answer 8

a component of the project or program management plan that describes how requirements will be defined, developed, monitored, controlled, and verified.

Question 9

define decomposition

Answer 9

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

Question 10

define requirements traceability matrix

Answer 10

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

Question 11

what is the scope management process?

Answer 11

includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully.
determining what is, and what is not, included in the project.

Question 12

name the steps of the scope management process

Answer 12

plan scope management.
collect requirements.
define scope.
create WBS.
validate scope.
control scope.

Question 13

define gold plating

Answer 13

when a project team delivers more than what is expected based on the product/project scope; usually requires more time and cost to deliver.

Question 14

define plan scope management process

Answer 14

the process of creating a scope management plan that documents how the project scope will be:
defined,
validated,
and controlled.
provides direction on how to manage scope throughout project.

Question 15

name inputs, tools & techniques, and outputs for scope management process

Answer 15

inputs:
project management plan.
project charter.
enterprise environmental factors.
organizational process assets.

tools & techniques:
expert judgement.
data analysis.
meetings.

outputs:
scope management plan.
requirements management plan.

Question 16

define collect requirements process

Answer 16

the process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives.
key benefit is that it provides a basis to define and manage project and product scope.

Question 17

name inputs, tools & techniques, and outputs for collect requirements process

Answer 17

inputs:
project charter.
project management plan.
project docs:
- scope management plan.
- requirements management plan.
- stakeholder management plan.
- stakeholder register.
business docs.

tools & techniques:
expert judgement.
data gathering (such as interviews, questionnaires/surveys and observations).
data analysis (such as benchmarking).
prototypes.
context diagrams.

outputs:
requirements documentation.
requirements traceability matrix.

Question 18

benchmarking

Answer 18

the comparison of actual or planned practices, such as processes and operations, to those of comparable organizations to identify best practices, generate ideas for improvement, and provide a basis for measuring performance.

Question 19

context diagrams

Answer 19

a visual depiction of the product scope showing a business system (process, equipment, computer. system, etc.), and. how people and other systems (actors) interact with it.

Question 20

observations (AKA “shadowing”)

Answer 20

a technique that provides a direct way of viewing individuals in their environment performing their jobs or tasks and carrying out processes.

Question 21

prototypes

Answer 21

a method of obtaining early feedback on requirements by providing a working model of the expected product before actually building it.

Question 22

questionnaires & surveys

Answer 22

written sets of questions designed to quickly accumulate info from a large number of respondents.

Question 23

define requirements documentation

Answer 23

a collect requirements output.

a description of how individual requirements meet the business need for the project.

Question 24

define requirements traceability matrix

Answer 24

a collect requirements output.

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

the ability to describe and trace the life of a requirement, in both a forward and backward direction.

Question 25

name typical attributes used in the requirements traceability matrix

Answer 25

a unique identifier.
a textual description of the requirement.
the rational for inclusion.
owner of the requirement.
source of the requirement.
priority.
current status.
acceptance criteria.

Question 26

define the define scope process

Answer 26

the process of developing a detailed description of the project and the product.

key benefit is that it provides a clear account of what is in and out of scope for the project. properly prepared and once approved, serves as the basis for a common understanding of the project objectives and deliverables among all project stakeholders.

Question 27

name inputs, tools & techniques, and outputs for define scope process

Answer 27

inputs:
project charter.
project management plan:
- scope management plan
project docs:
- assumption log.
- requirements documentation.
- risk register.
organizational process assets.

tools & techniques:
expert judgement.
data analysis:
- alternatives generation
interpersonal team skills:
- facilitation/facilitated workshops.
- product analysis

outputs:
project scope statement.
project docs updates (assumption log, requirements documentation, requirements traceability matrix and stakeholder register).

Question 28

define risk register

Answer 28

contains response strategies that may affect the project scope, such as reducing or changing project and product scope to avoid or mitigate a risk.

Question 29

define product analysis

Answer 29

for projects that have a product as a deliverable: a tool to define scope that generally means asking questions about a product and forming answers to describe the use, characteristics, and other relevant aspects of what is going to be manufactured.

Question 30

define alternatives generation

Answer 30

a technique used to develop as many potential options as possible in order to identify different approaches to execute and perform the work of the project.

Question 31

define facilitated workshops

Answer 31

an elicitation technique using focused sessions that bring key cross-functional stakeholders together to define product requirements.

Question 32

define alternative analysis

Answer 32

a technique used to evaluate identified options in order to select which options or approaches to use to execute and perform the work of the project.

Question 33

name 4 techniques that can be used to aid in the alternatives generation effort

Answer 33

alternative analysis
brainstorming
nominal group technique
mind mapping

Question 34

define brainstorming

Answer 34

a general data gathering and creativity alternatives generations technique that can be used to identify risks, ideas, or solutions to issues by using a group of team members or subject matter experts.

Question 35

define nominal group technique

Answer 35

an alternatives generations technique that enhances brainstorming w a voting process used to rank the most useful ideas for further brainstorming or for prioritization.

Question 36

define mind mapping

Answer 36

an alternatives generations technique used to consolidate ideas created through individual brainstorming sessions into a single map to reflect commonality and differences in understanding and to generate new ideas.

Question 37

define create WBS process

Answer 37

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

key benefit is that it provides a structured vision of what has to be delivered.

Question 38

name inputs, tools & techniques, and outputs for create WBS process

Answer 38

inputs:
project management plan:
- scope management plan
project docs:
- project scope statement.
- requirements documentation.
enterprise environmental factors.
organizational process assets.

tools & techniques:
expert judgement.
decomposition.

outputs:
scope baseline.
project docs updates (assumption log, requirements documentation).

Question 39

define decomposition

Answer 39

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

Question 40

define work package

Answer 40

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

Question 41

what are the steps of decomposition?

Answer 41

step 1 - gather info on major project deliverables (SOW).
step 2 - start development of the WBS at the highest level.
step 3 - begin decomposing each of the higher WBS components into lower-level deliverables.
step 4 - identify each work package and WBS components w a unique code (1.2.3).
step 5 - ensure that the WBS is at a sufficient level to estimate from.

Question 42

how is the WBS finalized?

Answer 42

by assigning each work package to a control account and establishing a unique identifier for that work package from a code of accounts. these identifiers provide structure for a hierarchical summation of costs, schedule, and resource info.

Question 43

define control account

Answer 43

sometimes called cost center, its a management control point where scope, budget, actual cost, and schedule are integrated and compared to earned value for performance measurement. each control account may include one or more work packages, but each of the work packages should be associated w only one control account.

Question 44

define validate scope process

Answer 44

the process of formalizing acceptance of the completed project deliverables.

key benefit is that validating the deliverables increases the chance of final acceptance of the project.

Question 45

name inputs, tools & techniques, and outputs for validate scope process

Answer 45

inputs:
project management plan:
- scope management plan.
requirements management plan.
project docs:
- requirements traceability matrix.
- requirements documentation.
- lessons learned register.
- quality reports.
verified deliverables.
work performance data.

tools & techniques:
inspection.
decision making (such as voting).

outputs:
accepted deliverables.
change requests.
work performacne info.
project docs updates:
- lessons learned register.
- requirements documentation.
- requirements traceability matrix.

Question 46

define inspection

Answer 46

examining or measuring to verify whether an activity, component, product, result, or service conforms to the specified requirements.
might be conducted thru formal reviews, audits, walk-throughs, etc.

defects list is common method for recording incomplete or incorrect work, and often needed to be completed for the project or phase to be accepted.

Question 47

define control scope process

Answer 47

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

key benefit is that it allows the scope baseline to be maintained throughout the project.

Question 48

name inputs, tools & techniques, and outputs for control scope process

Answer 48

inputs:
project management plan:
- scope management plan.
- requirements management plan.
- change management plan.
- configuration management plan.
- scope baseline.
- performance measurement baseline.
project docs:
- requirements traceability matrix.
- requirements documentation.
- lessons learned register.
organizational process assets.
work performance data.

tools & techniques:
data analysis (such as variance analysis and trend analysis).

outputs:
project management plan updates:
- scope management plan.
- requirements management plan.
- change management plan.
- configuration management plan.
- scope baseline.
- performance measurement baseline.
change requests.
work performance info.
project docs updates:
- lessons learned register.
- requirements documentation.
- requirements traceability matrix.
organizational process assets updates.

Question 49

define variance analysis

Answer 49

a technique used for determining the cause and degree of difference between the baseline and actual performance.

variances must be considered potential drivers for change requests as well as indicators the Scope, Time/Schedule and Cost/Budget constraints may need to be re-evaluated to determine if the project management plan or individual sub plans need to be updated.