Scope Management Flashcards Preview

PMP > Scope Management > Flashcards

Flashcards in Scope Management Deck (34):
1

Project scope

Work the project will do to deliver the product of the project; it encompasses the product scope.

Work performed to deliver a product service or result within the specified features and functions

Example: the orient scope will be a new train terminal that meets these technical specifications plus all the work needed to deliver the train terminal ( planning coordination and management activities )

2

Product Scope

Features and functions that characterize a product of a project; product deliverables with their associated features and functions

Example: on a project to build a new train terminal the product scope is a new train terminal that meets these technical specifications

3

Scope management process

Develop a plan for how you will plan manage and control scope and requirements
Determine requirements
Sort and balance the needs of the stakeholders
Create a WBS to break the scope into smaller pieces
Measure scope performance
Obtain validation that the completed scope of work is acceptable to the customer

4

Requirements management plan

Plan before you do

Describe the methods you intend to use to identify requirements and how you will analyze prioritize and manage and track changes to them

5

Collect requirements

Gathering more detailed input on what's required and any related assumptions, expectations from all stakeholders

Techniques:
Reviewing historical records
Interviews
Focus groups
Facilitated workshops
Brainstorming
Nominal group technique
Multi-criteria decision analysis
Mind maps
Affinity diagrams
Questionnaires and surveys
Observation
Prototypes
Benchmarking
Context diagrams
Group decision making

6

Reviewing historical records

Indicate what the requirements were on similar projects and help identify relevant processes and expectations

May provide Data about reporting requirements, project management requirements etc

7

Interviews

Expert interviews

Interviews stakeholders to elicit their requirements for a specific element of the product or project work

8

Focus groups

Helps to get a specific set of stakeholders or subject matter experts opinions and requirements for the product or aspect of the project

Selected from a specific demographic group of customers

9

Facilitated workshops

Bring together stakeholders with different perspectives to talk about the product and define requirements

10

Brainstorming

Encourage participants to build on each other's ideas might be good to include people from different perspectives and backgrounds

11

Nominal group technique

Meeting participants rank the most useful ideas generated during a brainstorming session

12

Multi-criteria decision analysis

Stakeholders quantify requirements using a decision matrix based on factors such as expected risk levels, time estimates and cost / benefit estimates

13

Mind maps

Diagram of idea or notes to help generate classify or record information... Looks like several trees coming out of a core word

14

Affinity diagrams

Ideas generated from other requirements gathering techniques are grouped by similarities and is then given a title

15

Questionnaire and surveys

Used for large groups and questions are asked to elicit requirements from respondents

16

Observation

Involves job shadowing watching a potential user or the product at work and sometimes participating to identify requirements

17

Prototypes

Model of the proposed product and presented to stakeholders for feedback

18

Benchmarking

Look at what the competitors are doing.. Measuring performance against that of another organization

19

Context diagrams

Shows the boundaries of the product scope by highlighting the product and its interfaces with people processes and systems

20

Group decision making

Delphi technique - a request for information is sent to experts who participate anonymously

Majority approach - if more than half of the participants support a decision

Dictatorship approach - one person makes the decision

21

Requirements documentation

After requirements have been collected and finalized they are documented

22

Balancing stakeholder requirements

Making sure the requirements can be met within the project objectives and involves prioritizing requirements and resolving immediate conflicts between them

23

Requirements traceability matrix

Helps link requirements to ensure the strategic goals are accomplished and requirement attributes ( ID number, source, status) also need to be documented

24

Define scope

What is and what isn't included in the project and its deliverables; iterative process PM needs to ensure scope meets the schedule and other project restraints before work begins

25

Product analysis

Analyze the objectives and description of the product stated by the consumer or sponsor and turn them into tangible deliverables; PM may need to determine and define deliverables as part of the project rather than receiving them

26

Project scope statement

Primary output of define scope process

Here is what we will do on the project
Here is the approved project scope and what is excluded
Deliverables
Acceptance criteria
Assumptions and constraints

27

WBS

Shows all the scope on the project broken down into manageable deliverables; Allows you to breakdown a project into pieces you can plan organize manage and control

Is a required element in project management
Without it elements may slip through the cracks
Is easier for the project team to look at than a list
Is deliverables oriented and includes nouns rather than actions
Graphical picture of the hierarchy of the project
Should exist for every project
Can be reused for other projects
Does not show dependencies

28

Control account

Tool that allows for the aggregation and analysis of work performance data regarding costs schedule and scope

29

Decomposition vs WBS

Decomposition is what you are doing and the WBS is the means to do it

30

WBS dictionary

Provides a description of the work to be done for each WBS work package and prevents scope creep

31

Scope baseline

Is the version of the WBS, WBS dictionary and project scope stamens approved at the end of planning before work begins

32

Validate scope

Planned meetings with the customer or sponsor to gain formal acceptance of deliverables during the project monitoring and controlling

Can be done at the end of each project phase
Can be done throughout monitoring and controlling phase
Formal acceptance of deliverables by the customer

33

Control scope

Measuring and assessing work performance data against the scope baseline and managing scope baseline changes

34

Scope management plan

How the scope will be planned managed and controlled

- how to achieve scope
- what tools to use to plan how the project will accomplish scope
- how to create the WBS
- what enterprise environmental factors and org process assets come into plan
- how scope will be managed and controlled
- how to obtain acceptance of deliverables