Pmp: Pmp Project Management Professional Exam Study Guide Chapter 3

Front 1

Develop Project Management Plan has 4 inputs

Back 1

1. Project Charter
2. Outputs from other processes
3. Enterprise environmental factors
4. Organizational process assets

Front 2

PMIS

Back 2

Part of Enterprise environmental factors. Automated or manual system used to document the project management plan and subsidiary plans. Incorporates the configuration management system and change contort system.

Front 3

The project management plan describes:

Back 3

the processes you'll use to perform the project and describes how the project will be executed, monitored, controlled and how the work of the project will be executed to meet the objectives.

Front 4

Project Charter contains:

Back 4

• project objectives
  
• project description
  
• high level requirements
  
• summary milestones schedule
  
• summary budget
  

Front 5

The scope management plan describes:

Back 5

Input into the Project Management Plan

how project scope will be defined and verified, how the scope statement will be developed, how the WBS will be created and defined and how project scope will be managed and controlled. Project scope is measured against the project management plan, but project scope is measured against the product requirements.

Front 6

Plan Scope Management has 2 tools:

Back 6

Expert Judgment

Meetings

Front 7

The Requirements Management Plan

Back 7

Input into the Project Management Plan

Describes how the requirements will be analyzed, documented, traced, reported, and managed through out the project.

Front 8

Requirements describe

Back 8

the characteristics of the deliverable. Also can describe the functionality and a deliverable must have or specific conditions a deliverable must meet to satisfy the objectives of the project.

Front 9

Tools and Techniques to help identify requirements

Back 9

Interviews

Focus Groups

Facilitated Workshops

Group Creativity Techniques

Front 10

Defining project scope is critical to the success of the project because it spells out exactly what the product or service of the project looks like

Back 10

Why is defining project scope so critical

Front 11

First do requirements gathering

Back 11

Then scope definition

Front 12

Product analysis

Back 12

a method for converting the product description and project objectives into deliverable and requirements. Most helpful when the project's end result is a product.

Front 13

Tools to help do product analysis

Back 13

• perform value analysis
  
• product breakdown
  
• systems engineering techniques
  
• system analysis
  
• value engineering techniques
  

Front 14

Alternatives generation

Back 14

A technique used for discovering different methods or ways of accomplishing the work of the project.

Ex. brainstorming to figure out a different way of going about doing the work of the project

Front 15

Project scope statement

Back 15

documents the project objectives, deliverables, and the work required to produce the deliverables so that it can be used to direct the project team's work and is a basis for future project decisions.

Front 16

Difference between Project Charter and Scope Statement

Back 16

Project charter is a high level description for the project

Project scope statement is a detailed description of the project and product scope and describes how the final product or result of the project twill be accepted.

Front 17

Assumptions

Back 17

Things you believe to be true, have to be documented.

Front 18

Decomposition

Back 18

Subdividing deliverable into smaller components - the purpose of the WBS process.

Front 19

100% Rule

Back 19

Collectively, all the levels of the WBS roll up to the top so that all the work of the project is captured (and no additional work is added).

Front 20

Scope baseline

Back 20

approved version of the detailed project scope statement, the WBS and the WBS dictionary.