Brainscape's Knowledge GenomeTM

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


See full index

My CAPM > Scope > Flashcards

Scope Flashcards

1
Q

scope processes

A 
plan scope mgmt
collect requirements
define scope
create WBS
validate scope
control scope
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

product scope

A

features and functions of a product, service or result

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

project scope

A

WORK PERFORMED to deliver a product with the specified features and functions.
project scope is sometimes viewed as product scope

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

plan scope management

A

create scope management plan that documents how project & product scope will be defined, validated and controlled

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

plan scope management

benefit

A

provides guidance and directions on how scope will be managed

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

plan scope management

inputs

A
  • project charter

- pmp: QUA, project life cycle description, development approach

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

plan scope management

TT

A

EDM

D: alternative analysis

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

plan scope management

outputs

A

scope management plan

requirements management plan

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

scope management plan

components

A

processes for

  • preparing a proj scp statement
  • For creating WBS
  • How scope baseline will be approved and maintained
  • How formal acceptance of deliverables will be obtained
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

requirements management plan

components

A

processes for:

  • How requirements activities will be planned, tracked and reported
  • Configuration mgmt activities: how to initiate changes to the product, service, or result, how to analyze the impact of the changes, and how to change approval authorization
  • requirements prioritize process
  • Metrics
  • Traceability structure for the traceability matrix
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

collect requirements

A

determine, documenting and managing stakeholder needs and requirements to meet objectives

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

collect requirements

benefits

A

provide basis for defining product & project scope

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

collect requirements

inputs

A
  • project charter
  • pmp: scope management plan, requirements management plan, stakeholder engagement
  • business case
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

collect requirements

TT

A

EDDD

  • data gathering: BIFQB
  • data representation: mind mapping
  • data analysis
  • Interpersonal & teams: facilitation
  • Context diagrams
  • Prototypes
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

collect requirements

outputs

A
  • Requirements documentation

- Requirements traceability matrix

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

context diagrams

A

a scope model

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

Prototypes

A

obtain early feedback on requirements. providing a model of the expected product before actually building it. storyboarding

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

Requirements documentation

A

describe how individual requirements meet the business need for the project. requirements need to be measurable and testable

19
Q

Requirements traceability matrix

A

a grid used to align requirements to the deliverables

a means to track requirements throughout the project life cyle

20
Q

different types of requirements

A
  • business
  • stakeholder
  • solution
  • transition and readiness
  • project
  • quality
21
Q

Tracing requirement includs

A

At a minimum, requirements can be traced to
business needs, project aims, project scope and WBS
deliverables, product design and development, testing,
and high-level requirements.

22
Q

define scope

A

develop a DETAILED description of project & product

the process can be highly iterative

23
Q

define scope

benefits

A

describe the boundaries and acceptance criteria

24
Q

define scope

inputs

A
  • project charter
  • pmp: scope
  • doc: requirements documentation
25
Q

define scope

TT

A

E

Data analysis: alternative analysis

26
Q

define scope

outputs

A
  • project scope statement

- updates: requirements doc, requirement traceability matrix

27
Q

project scope statement

typically includes

A
  • Product scope description (progressively elaborated)
  • Product acceptance criteria
  • Project deliverables
  • Project exclusions
  • Project constraints & assumptions

what is & what is not, included in the project.

28
Q

create WBS

A

the major deliverables are divided into smaller components that can be easily estimated (schedule and cost), managed, and controlled.

29
Q

create WBS

benefits

A

provides a framework of what has to be delivered

30
Q

create WBS

inputs

A
  • pmp: scope
  • project scope statement
  • project requirement documentation
31
Q

create WBS

TT

A

E

Decomposition

32
Q

create WBS

outputs

A

scope baseline

33
Q

work package

A

The smallest level of WBS work for which cost and schedule can be assessed and
administered

34
Q

WBS components

A
  • control accounts (may include 1 or more planning packages)
  • planning packages
  • work packages (the lowest level of the WBS).

100% rule: 100% of the work of a project (or program) needs to be represented in the WBS

35
Q

WBS & components

A

Any unit of work defined in the WBS:

  • control accounts (may include 1 or more planning packages)
  • planning packages
  • work packages (the lowest level of the WBS).

100% rule: 100% of the work of a project (or program) needs to be represented in the WBS

36
Q

validate scope

A

secure sign-off (formal acceptance) of the project scope at logical intervals ((each milestone, each deliverable, etc)
ACCEPT DELIVERABLES
validate early and validate often

37
Q

validate scope

inputs

A
  • pmp: scope,
  • requirements mgmt plan
  • scope baseline
  • verified deliverables
38
Q

validate scope

TT

A

inspection

voting

39
Q

validate scope

outputs

A

accepted deliverables

change requests

40
Q

control scope

A

monitor the status of project & product scope

manage changes to the scope baseline

41
Q

control scope

benefit

A

maintain scope baseline

42
Q

control scope

inputs

A 
- pmp: scope
  requirements management plan
  scope baseline
-docs:
  requirements doc, requirement traceability matrix
43
Q

control scope

TT

A

VT
variance analysis
trend analysis

44
Q

control scope

outputs

A

work performance info
change requests
scope/schedule/cost baseline updates
performance measurement baseline

My CAPM (12 decks)

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