Planning Process

Question 1

The planning Process Group is for

Answer 1

Establish Total Scope

Prgressive Elaboration

Question 2

What is in the Integration of planning

Answer 2

Making Objective Trade Off’s

-Scope, Schedule, Cost, Quality, Risk, Resources

PM responsible for integration

Develops course of action

Deveolps PM Plan & Documents

Question 3

For Itereative Planning

Answer 3

Team members create WBS

Additional team members added

Question 4

Agile Planning is described as

Answer 4

Promote team as experts

control team

collaborative decision making

Team broad skill base

Question 5

What is the difference between

Project Scope vs Product Scope

Answer 5

Project

Product

WORK that has to be done

Measured against project management plan

DELIVERABLE

Features and functions

Measured against product requirements

Question 6

Stakeholder Engagement Includes

Answer 6

Develop HOW to involve stakeholders

Needs, Interest, Impact, Expectations

Question 7

Inputs for Stakeholder Engagement

Answer 7

Project Charter

Stakeholder Register

PM Plan

EEF & OPA

Question 8

Outputs for Stakeholder Engagement

Answer 8

Stakeholder Engagement Plan

Desired vs Current engagement levels

Communication Requirements

Discretion distributing sensitive info

Question 9

SEAM stands for

Answer 9

Stakeholder Engagement Assessment Matrix

Compare and Document current vs desired engagement

Question 10

SEAM Matrix

Stakeholder Engagment Assessment Matirx

Answer 10

Stakeholder

Unaware

Resistant

Neutral

Supportive

Leading

Joe

Current ©

Desired (D)

Question 11

Describe Plan Scope Management

Answer 11

How scope will be defined, validated, and controlled

Question 12

Inputs to Plan Scope Management

Answer 12

Project Charter

PM Plan

EEF & OPA

Question 13

Outputs for Plan Scope Management

Answer 13

Scope Management Plan

Requirments Management Plan

Question 14

Scope Management Plan Describes

Answer 14

How to prepare scope statement

create WBS

How scope is validated, approved, controlled, and changed

Question 15

Requirements Management Plan describes

Answer 15

How requirements planned

how changes will be managed

product metrics

Question 16

Agile Plan Scope Management

Answer 16

Deliverables developed over multiple iterations

product backlog

highest priority items delivered

more time spent on refinement

Release versions

Customer is continuously engaged

Question 17

Collect Requirements

Answer 17

Determine/Document Stakeholder needs and requirements

Question 18

Inputs to Collect Requirements

Answer 18

Project Charter

Business Documents

Stakeholder Register

PM Plan

EEF & OPA

Question 19

Outputs to Collect Requirements

Answer 19

Requirements Documentation

Requirements Traceability Matrix

Question 20

Data Gathering for Requirements Collection

Answer 20

Interviews (PM Job)

Focus Groups

Question 21

4 interpersonal requirement techniques

Answer 21

Facilitation (QFD, JAD, User Stories)

Workshops (Cross Functional, Reconcile Differences)

Observation (Job Shadowing)

Nominal Group Technique NGT (Voting Process)

Question 22

Data Representation Techniques

Answer 22

Affinity Diagram

Mind Mapping

Context Diagrams

Question 23

Tools and Techniques to Collect Requirements

Answer 23

QFD Quality Function Deployment

-Voice of Customers

JAD Joint Application Development

-Bring business SME’s and developers work together

HOQ House of Quality

Question 24

What are the 4 interpersonal techniques to gather information

Answer 24

Facilitation

Observation

Workshops

Nominal Group Technique

Question 25

Facilitation includes what 3 things

Answer 25

**QFD** - Quality Function Deployment (Voice of Customer, Needs are sorted and prioritized) **JAD** - Joint Application Development (SME's and developers work otgether) **User Stories** (Required functionality)

Question 26

what are the 5 Decision making techniques

Answer 26

Unanimity - Everyone agrees Majority - \>50% agrees Plurality - Largest Block agrees Autocratic - One persons choice MCDA (Multi Criteria Decision Analysis) - Decision Matrix

Question 27

Define Scope

Answer 27

Detailed description of the project / product (Scope Statement)

Question 28

Inputs to define Scope

Answer 28

Project Charter PM Plan Project Documents EEF and OPA

Question 29

Outputs for Define Scope

Answer 29

Project Scope Statement Project Document Updates -Assumption Log

Question 30

Tools and techniques to Define Scope

Answer 30

Expert Judgment Product Analysis Data Analysis Decision Making (MCDA)

Question 31

What are the 6 tools for Product Analysis (Alternatives Analysis)

Answer 31

Value Analysis - Lowest cost without loss of quality.. Functional Analysis - Function based word pair (remove pollutants) PBS - Product Breakdown Structure - Hierarchy of product Requirements Analysis - Elicit Systems Analysis - desing related Systems Engineering - Design and managmenet of engineering projects

Question 32

What are the ouputs to the Scope Statement

Answer 32

Provides common understanding to stakeholders Describes all deliverables Inlcudes scope exclusions or boundaries Product or project scope description product acceptance criteria Assumptions - factors considered to be true Constraints -Limiting Factors

Question 33

Difference between Charter and Scope Project Charter vs Scope Statement

Answer 33

Charter Scope Statement **High Level Summary** **Detailed** **Project purpose justification** Scope description Measureable objectives Product acceptance Success criteria Deliverables High level requirements Scope Exclusions High level description Assumptions Schedule and budget summary Constraints Stakeholder list **Elaborates the Charter** Approval requirements Assign PM Authorizing persons names

Question 34

Describe WBS Work Breakdown Structure

Answer 34

Subdivide project deliverables into smaller more manageable componenets or packages

Question 35

Inputs to WBS

Answer 35

Project Documents (Scope / Requirements) PM Plan EEF and OPA

Question 36

Outputs to WBS

Answer 36

Scope Baseline Which includes WBS, WBS Dictionary **Updates** project documents

Question 37

Decomposition of WBS _This is on the TEST_

Answer 37

Hierarchical down to package level Work Package is lowest level of WBS Deliverables can have different levels of breakdown Agile: Epics are decomposed to user stories WBS must include project management work component Code of Accounts Decomp could have phases, deliverables, sub projects as first level of WBS 100% Rule: WBS defines total scope of the project

Question 38

WBS Notes

Answer 38

Created by Project Team Team development tool not time based; deliverable oriented communication between team and stakeholders WBS Dictionary Control Account - Management point Planning Package Heuristic - a rule of thumb Baseline Scope Baseline = WBS + WBS Dictionary + Scope Statement