Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

CAPM: 5 Project Scope Mgt

No description
by

Tricia Harney

on 7 October 2015

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of CAPM: 5 Project Scope Mgt

CAPM: 5 Project Scope Mgt
design by Dóri Sirály for Prezi
What are the six processes that make up Project Scope Management?
5.1 Plan Scope Management
5.2 Collect Requirements
5.3 Define Scope
5.4 Create WBS
5.5 Validate Scope
5.6 Control Scope
Process: 5.1 Plan Scope Management
Process Group: Planning
Knowledge Area: Scope Management
.1 Inputs
.1
.2
.3
.4
Process: 5.1 Plan Scope Management
Process Group: Planning
Knowledge Area: Scope Management
.1 Inputs
.1 Project management plan
.2 Project charter
.3 EFF's
.4 OPA's
Process: 5.1 Plan Scope Management
Process Group: Planning
Knowledge Area: Scope Management
.2 Tools & Techniques
.1
.2
Process: 5.1 Plan Scope Management
Process Group: Planning
Knowledge Area: Scope Management
.2 Tools & Techniques

.1 Expert judgment
.2 Meetings
What are the six processes that make up Project Scope Management?
Hint:
5.1 PSM
5.2 CR
5.3 DS
5.4 C WBS
5.5 VS
5.6 CS
Process: 5.1 Plan Scope Management
Process Group: Planning
Knowledge Area: Scope Management
.3 Outputs
.1
.2
Process: 5.1 Plan Scope Management
Process Group: Planning
Knowledge Area: Scope Management
.3 Outputs
.1
Scope management pan
.2

Requirements management plan
Process: 5.2 Collect Requirements
Process Group: Planning
Knowledge Area: Scope Management
.1 Inputs
.1
.2
.3
.4
.5
Process: 5.2 Collect Requirements
Process Group: Planning
Knowledge Area: Scope Management
.2 Tools & Techniques

.1 Interviews
.2 Focus Groups
.3 Facilitated Workshops
.4 Group Creativity Techniques
.5 Group Decision-making Techniques
.6 Questionnaires & Surveys
.7 Observations
.8 Prototypes
.9 Benchmarking
10. Context Diagrams
11. Document Analysis
Process: 5.2 Collect Requirements
Process Group: Planning
Knowledge Area: Scope Management
.2 Tools & Techniques:
Group Creativity Techniques
MATCH GAME
.1 Interviews
.2 Focus groups
.3 Facilitated workshops
.4 Group creativity technique
.5 Group decision-making techniques
.6 Questionnaires & surveys
.7 Observations
.8 Prototypes
.9 Benchmarking
.10 Context diagrams
.11 Document analysis
Process: 5.2 Collect Requirements
Process Group: Planning
Knowledge Area: Scope Management
.3 Outputs
.1
.2
Process: 5.2 Collect Requirements
Process Group: Planning
Knowledge Area: Scope Management
.3 Outputs
.1
Requirements documentation
.2
Requirements traceability matrix*

*________ associated w/each requirement

(ANSWER: Attributes)
Process: 5.3 Define Scope
Process Group: Planning
Knowledge Area: Scope Management
.1 Inputs
.1
.2
.3
.4
Process: 5.3 Define Scope
Process Group: Planning
Knowledge Area: Scope Management
.1 Inputs
.1 Project charter
.2 OPA's
.3
Requirements documents
.4
Scope management plan
Process: 5.3 Define Scope
Process Group: Planning
Knowledge Area: Scope Management
.2 Tools & Techniques
.1
.2
.3
.4
Process: 5.3 Define Scope
Process Group: Planning
Knowledge Area: Scope Management
.2 Tools & Techniques
.1 Expert judgment
.2
Product
analysis
.3
Alternatives generation
.4
Facilitated workshops
Process: 5.3 Define Scope
Process Group: Planning
Knowledge Area: Scope Management
.3 Outputs
.1
.2
Process: 5.3 Define Scope
Process Group: Planning
Knowledge Area: Scope Management
.3 Outputs
.1
Project scope statement
.2 Project documents updates
Process: 5.4 Create WBS*
Process Group: Planning
Knowledge Area: Scope Management
.1 Inputs
.1
.2
.3
.4
.5
Process: 5.4 Create WBS
Process Group: Planning
Knowledge Area: Scope Management
.1 Inputs
.1 Project management plan
.2
Project scope statement
.3
Requirements documentation
.4 EEF's
.5 OPA's
Process: 5.4 Create WBS
Process Group: Planning
Knowledge Area: Scope Management
.2 Tools & techniques
.1
.2
Process: 5.4 Create WBS
Process Group: Planning
Knowledge Area: Scope Management
.2 Tools & techniques
.1
Decomposition
.2 Expert judgment
Process: 5.4 Create WBS
Process Group: Planning
Knowledge Area: Scope Management
.3 Outputs
.1
.2
Process: 5.4 Create WBS
Process Group: Planning
Knowledge Area: Scope Management
.3 Outputs
.1
Scope baseline
.2 Project documents updates
Process: 5.5 Validate Scope
Process Group: M&C
Knowledge Area: Scope Management
.1 Inputs
.1
.2
.3
.4
.5
Process: 5.5 Validate Scope
Process Group: Monitoring & Controlling
Knowledge Area: Scope Management
.1 Inputs
.1
Verified deliverables
*
.2
Requirements documentation
.3
Requirements traceability matrix
.4 Work performance
data
.5 Project management plan

*Formal acceptance of deliverables
Process: 5.5 Validate Scope
Process Group: Monitoring & Controlling
Knowledge Area: Scope Management
.2 Tools & techniques
.1
.2
Process: 5.5 Validate Scope
Process Group: M&C
Knowledge Area: Scope Management
.2 Tools & Techniques
.1 Inspection
.2
Group decision-making techniques
Process: 5.5 Validate Scope
Process Group: Monitoring & Controlling
Knowledge Area: Scope Management
.3 Outputs
.1
.2
.3
.4
Process: 5.5 Validate Scope
Process Group: Monitoring & Controlling
Knowledge Area: Scope Management
.3 Outputs
.1
Accepted deliverables
.2 Change requests
.3 Work performance

info
.4 Project documents updates
Process: 5.6 Control Scope
Process Group: Monitoring & Controlling
Knowledge Area: Scope Management
.1 Inputs
.1
.2
.3
.4
.5
Process: 5.6 Control Scope
Process Group: Monitoring & Controlling
Knowledge Area: Scope Management
.1 Inputs
.1 Project management plan
.2
Requirements documentation
.3
Requirements traceability matrix
.4 Work performance

data
.5 OPA's
Process: 5.6 Control Scope
Process Group: Monitoring & Controlling
Knowledge Area: Scope Management
.2 Tools & Techniques
.1
Process: 5.6 Control Scope
Process Group: Monitoring & Controlling
Knowledge Area: Scope Management
.2 Tools & Techniques
1.
Variance analysis
Process: 5.6 Control Scope
Process Group: Monitoring & Controlling
Knowledge Area: Scope Management
.3 Outputs
.1
.2
.3
.4
.5
Process: 5.6 Control Scope
Process Group: M&C
Knowledge Area: Scope Management
.3 Outputs
.1 Work performance

info
.2 Change requests
.3 Project management plan updates
.4 Project documents updates
.5 OPA's
Process: 5.2 Collect Requirements
Process Group: Planning
Knowledge Area: Scope Management
.1 Inputs
.1
Scope management plan
.2
Requirement management plan
.3 Project charter
.4 Stakeholder management plan
.5 Stakeholder register
The Project Scope Statement Includes
1.
2.
3.
4.
5
6.
The Project Scope Statement Includes:
ANSWER:
1.
Product Scope
2.
Project Scope
3. Deliverables
4. Acceptance Criteria
.5 Constraints and Assumptions
6. What is NOT part of the project
Scope Baseline is:
____________________
Of:
1.
2.
3.
Scope Baseline is:
Approved Version of
1. WBS
2. WBS Dictionary
3. Project Scope Statement

Pop Quiz! WBS Dictionary helps to prevent "________ ________"


ANSWER:
Scope Creep
Product Scope and Project Scope
________ Scope. Requirements that relate to the product. Can also be defined as the product ________ with all associated features and functions

________ Scope. Work the project will do to deliver the product of project

ANSWERS: Product; Project
A
Enhances brainstorming with a voting process used to rank the most useful ideas for further brainstorming or for prioritization
B
Used to generate and collect multiple ideas related to project and product requirements. Does not include voting or prioritization but is often used with other creativity techs that do
C
Ideas created through individual brainstorming sessions are consolidated into a single diagram to reflect commonality and differences in understanding and generating new ideas
D
Allows large numbers of ideas to be classified into groups for review and analysis
E
Utilizes a decision matrix to provide a systematic analytical approach for establishing criteria such as risk levels, uncertainty and valuation, to evaluate and rank many ideas

ANSWER: 1B, 2A, 3E, 4C, 5D
1.
Brainstorming
2.
Nominal Group Tech
3.
Multi-Criteria Decision Models
4.
Mind Maps
5.
Affinity Diagrams

Group Decision-Making Techniques
1. ________ Everyone agrees on single course of action.

2. ________ Decision is reached with >50% of vote. May be helpful when conflict occurs

3. ________ Largest block in group decides. Method is generally used when number of options is >two

4. ________ Single person is assigned to make decision

5. ________ Seeks general agreement

BONUS ________ ________ is an example of a unanimous decision-making technique

ANSWERS: Unanimous; Majority; Plurality; Dictatorship; Consensus, Delphi Technique
Requirements Traceability Matrix
1. Is a grid that links ________ requirements from their origin to the deliverable that satisfies them.

2. Helps ensure that each requirement adds business value by linking it to the ________ and ________ objectives

3. Helps to ensure that requirements approved in the ________ ________ are delivered at the end of the project

4. Provides a structure for managing changes to product ________

Bonus: The Requirements Traceability Matrix tracks requirements ________ the project life cycle

ANSWER
:
Product; Business and Project; Requirements Documents; Scope; Throughout

Context Diagrams
Visually depict the product scope by showing a business system and how other people and other systems interact with it PMBOK
1. Frequently used to define and model ____.

2. Shows boundaries of product ____ by highlighting the product and its ________ with people, processes, and systems

BONUS: Context Diagrams is a Tool & Technique of ________ ________ process

ANSWER: Scope; Scope; Interfaces; Collect Requirements
Note Product AND Project Scope are part of Project Scope Statement!
Work Breakdown Structure (WBS)
1. Process of ________ project deliverables and project work into smaller, more manageable components

2. ________ decomposition of total scope of work to be carried out by project team

3. Organizes and defines total scope of project and represents work specified in current approved ________ _______ ________

4. The planned work is contained within the lowest level of WBS components which are called ________ _______

BONUS: "Work" refers to ________ or ________


ANSWERS:
Subdividing; Hierarchical; Project Scope Statement; Work Packages; Products or Deliverables (not activities)
Output from Collect Requirements Process
Task vs. Activity
An "Activity" is a particular piece of work schedule for project, while "tasks" are the smaller components of work that make up that activity
*WBS are often numbered to help distinguish Work Packages
WBS (Continued)
1. WBS is finalized by assigning each ________ ________ to a ________ ________ and establishing a unique package from a code of accounts.

2. ________ ________ is a management control point where scope budget, actual cost and schedule are integrated and compared to ________ ________ when analyzing performance measurement

3. Each ________ ________ is associated with only one control account


ANSWER: Work Package; Control Account; Control Account; Earned Value; Work Package
Full transcript