Scope Management Flashcards

1
Q

Product Scope

A

Requirements for the final product

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

Project Scope

A

work the project team will do to deliver the product of the project, including the product scope

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

Inputs: Plan Scope Management

A
  • Project Charter
  • PM Plan
  • EEFs
  • OPAs
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Outputs: Plan Scope Management

A
  • Scope Management Plan
  • Requirements Management Plan
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Scope Management Plan

A
  • how to achieve scope
  • what tools to use to plan
  • how to create the WBS
  • how scope will be managed and controlled
  • how to obtain acceptance of deliverables
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Requirements Management Plan

A

aka business analysis plan

outlines how requirements are analyzed, prioritized, managed, and tracked

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

Types of Requirements

A
  • how the work is planned and managed
  • capabilities for product
  • stakeholder requirements (from stakeholder register)
  • quality measures
  • business procedures (i.e. reporting of expenses)
  • legal or ethical complaince
  • project management procedures
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Inputs: Collect Requirements

A
  • Project charter
  • PM Plan
  • Project docs
  • Business docs
  • Agreements
  • EEFs
  • OPAs
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Outputs: Collect Requirements

A
  • Requirements documentation (including acceptance criteria)
  • Requirements traceability matrix
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Affinity diagrams

A

Groups ideas for requirements by similarities; aid in determining whether all areas of scope have been identified

Also used for risks.

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

Nominal Group Technique

A
  • question or issue is posed
  • all meeting particiapants write down and share their ideas
  • group discussion
  • ideas ranked
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Delphi Technique

A

requirements are collected anonymously from SMEs (to avoid stakeholders influencing each other)

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

Facilitation

A

concensus-based approach that brings stakeholders with different perspectives to talk about the product & define reqirements.

user stories may be developed through facilitation

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

Quality Functional Deployment

A

type of facilitation, aka voice of the customer

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

Context Diagrams

A

shows boundaries of scope by highlighting the product and its interfaces with people, processes or systems

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

Requirement Traceability Matrix

A

links requirements to the objectives to ensure strategic goals are accomplished

(may also link to stakeholders and origin of requirement)

17
Q

Inputs: Define Scope

A
  • Project Charter
  • PM Plan
  • Project docs
  • EEFs
  • OPAs
18
Q

Outputs: Define Scope

A
  • Project Scope Statement
  • Project docs updates
19
Q

Project Scope Statement

A

douments the characteristics and boundaries of the project and its associated products, results, and services in addition to the acceptance criteria.

20
Q

Components of Project Scope Statement

A

Components may vary depending on project approach.

  • product scope
  • detailed list of deliverables*
  • acceptance criteria
  • exclusions
  • constraints
  • assumptions

* must be in all scope statements

21
Q

Scope Baseline

A

Scope statement, WBS, WBS dictionary

22
Q

Inputs: Create WBS

A
  • PM Plan
  • Project Docs
  • EEFs
  • OPAs
23
Q

Outputs: Create WBS

A
  • Scope Baseline
  • Project docs update
24
Q

Levels of WBS

A

Project

Control Accounts

Work Packages

Note: Work Packages should be work products or deliverables, NOT activities.

25
Q

Difference between task and activity

A

activity: particular piece of work scheduled for the project

tasks: smaller components of work that make up an activity

26
Q

WBS

A

a graphical picture of the hierarchy of a porject

identifies all deliverables to be completed

does not show dependencies

27
Q

PM uses for WBS

A
  • to determine appropriateness of scope-related change request
  • evaluate impact of changes that relate to scope
  • control scope creep
  • communicatins tool
  • onboarding of team members
28
Q

WBS Dictionary

A

provides a desription of the work to be done for each WBS work package + acceptance criteria for each deliverable

29
Q

Inputs: Validate Scope

A
  • PM Plan
  • Project docs
  • Verified Deliverables
  • Work Performance Data
30
Q

Outputs: Validate Scope

A
  • Accepted deliverables
  • Change requests
  • Work Performance Information
  • Project docs updates
31
Q

Validate Scope

A

process where deliverables are formally inspected and accepted by the customer or sponsor.

occurs immediately after Control Quality

32
Q

What is the difference between acceptance in Validate Scope & Close Project or Phase?

A

Validate Scope = (interim) deliverables acceptance

Close Project or Phase = final project acceptance

33
Q

Inputs: Control Scope

A
  • PM plan
  • Project docs
  • Work Performance Data
  • OPAs
34
Q

Outputs: Control Scope

A
  • Work Performance Information
  • Change Requests
  • PM Plan updates
  • Project docs updates
  • OPAs updates
35
Q

What process includes testing of interim deliverables?

A

Control Scope