Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Project Management > Planning Process > Flashcards

Planning Process Flashcards

1
Q

The planning Process Group is for

A

Establish Total Scope

Prgressive Elaboration

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

What is in the Integration of planning

A

Making Objective Trade Off’s

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

PM responsible for integration

Develops course of action

Deveolps PM Plan & Documents

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

For Itereative Planning

A

Team members create WBS

Additional team members added

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

Agile Planning is described as

A

Promote team as experts

control team

collaborative decision making

Team broad skill base

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

What is the difference between

Project Scope vs Product Scope

A

Project

Product

WORK that has to be done

Measured against project management plan

DELIVERABLE

Features and functions

Measured against product requirements

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

Stakeholder Engagement Includes

A

Develop HOW to involve stakeholders

Needs, Interest, Impact, Expectations

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

Inputs for Stakeholder Engagement

A

Project Charter

Stakeholder Register

PM Plan

EEF & OPA

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

Outputs for Stakeholder Engagement

A

Stakeholder Engagement Plan

Desired vs Current engagement levels

Communication Requirements

Discretion distributing sensitive info

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

SEAM stands for

A

Stakeholder Engagement Assessment Matrix

Compare and Document current vs desired engagement

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

SEAM Matrix

Stakeholder Engagment Assessment Matirx

A

Stakeholder

Unaware

Resistant

Neutral

Supportive

Leading

Joe

Current ©

Desired (D)

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

Describe Plan Scope Management

A

How scope will be defined, validated, and controlled

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

Inputs to Plan Scope Management

A

Project Charter

PM Plan

EEF & OPA

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

Outputs for Plan Scope Management

A

Scope Management Plan

Requirments Management Plan

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

Scope Management Plan Describes

A

How to prepare scope statement

create WBS

How scope is validated, approved, controlled, and changed

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

Requirements Management Plan describes

A

How requirements planned

how changes will be managed

product metrics

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

Agile Plan Scope Management

A

Deliverables developed over multiple iterations

product backlog

highest priority items delivered

more time spent on refinement

Release versions

Customer is continuously engaged

17
Q

Collect Requirements

A

Determine/Document Stakeholder needs and requirements

18
Q

Inputs to Collect Requirements

A

Project Charter

Business Documents

Stakeholder Register

PM Plan

EEF & OPA

19
Q

Outputs to Collect Requirements

A

Requirements Documentation

Requirements Traceability Matrix

20
Q

Data Gathering for Requirements Collection

A

Interviews (PM Job)

Focus Groups

21
Q

4 interpersonal requirement techniques

A

Facilitation (QFD, JAD, User Stories)

Workshops (Cross Functional, Reconcile Differences)

Observation (Job Shadowing)

Nominal Group Technique NGT (Voting Process)

22
Q

Data Representation Techniques

A

Affinity Diagram

Mind Mapping

Context Diagrams

23
Q

Tools and Techniques to Collect Requirements

A

QFD Quality Function Deployment

-Voice of Customers

JAD Joint Application Development

-Bring business SME’s and developers work together

HOQ House of Quality

24
Q

What are the 4 interpersonal techniques to gather information

A

Facilitation

Observation

Workshops

Nominal Group Technique

25
Q

Facilitation includes what 3 things

A

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)

26
Q

what are the 5 Decision making techniques

A

Unanimity - Everyone agrees

Majority - >50% agrees

Plurality - Largest Block agrees

Autocratic - One persons choice

MCDA (Multi Criteria Decision Analysis) - Decision Matrix

27
Q

Define Scope

A

Detailed description of the project / product

(Scope Statement)

28
Q

Inputs to define Scope

A

Project Charter

PM Plan

Project Documents

EEF and OPA

29
Q

Outputs for Define Scope

A

Project Scope Statement

Project Document Updates

-Assumption Log

30
Q

Tools and techniques to Define Scope

A

Expert Judgment

Product Analysis

Data Analysis

Decision Making (MCDA)

31
Q

What are the 6 tools for Product Analysis

(Alternatives Analysis)

A

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

32
Q

What are the ouputs to the Scope Statement

A

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

33
Q

Difference between Charter and Scope

Project Charter vs Scope Statement

A

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

34
Q

Describe WBS

Work Breakdown Structure

A

Subdivide project deliverables into smaller more manageable componenets or packages

35
Q

Inputs to WBS

A

Project Documents (Scope / Requirements)

PM Plan

EEF and OPA

36
Q

Outputs to WBS

A

Scope Baseline

Which includes WBS, WBS Dictionary

Updates project documents

37
Q

Decomposition of WBS

This is on the TEST

A

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

38
Q

WBS Notes

A

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

39
Q
A

Project Management (5 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions