Planning Process Flashcards
The planning Process Group is for
Establish Total Scope
Prgressive Elaboration
What is in the Integration of planning
Making Objective Trade Off’s
-Scope, Schedule, Cost, Quality, Risk, Resources
PM responsible for integration
Develops course of action
Deveolps PM Plan & Documents
For Itereative Planning
Team members create WBS
Additional team members added
Agile Planning is described as
Promote team as experts
control team
collaborative decision making
Team broad skill base
What is the difference between
Project Scope vs Product Scope
Project
Product
WORK that has to be done
Measured against project management plan
DELIVERABLE
Features and functions
Measured against product requirements
Stakeholder Engagement Includes
Develop HOW to involve stakeholders
Needs, Interest, Impact, Expectations
Inputs for Stakeholder Engagement
Project Charter
Stakeholder Register
PM Plan
EEF & OPA
Outputs for Stakeholder Engagement
Stakeholder Engagement Plan
Desired vs Current engagement levels
Communication Requirements
Discretion distributing sensitive info
SEAM stands for
Stakeholder Engagement Assessment Matrix
Compare and Document current vs desired engagement
SEAM Matrix
Stakeholder Engagment Assessment Matirx
Stakeholder
Unaware
Resistant
Neutral
Supportive
Leading
Joe
Current ©
Desired (D)
Describe Plan Scope Management
How scope will be defined, validated, and controlled
Inputs to Plan Scope Management
Project Charter
PM Plan
EEF & OPA
Outputs for Plan Scope Management
Scope Management Plan
Requirments Management Plan
Scope Management Plan Describes
How to prepare scope statement
create WBS
How scope is validated, approved, controlled, and changed
Requirements Management Plan describes
How requirements planned
how changes will be managed
product metrics
Agile Plan Scope Management
Deliverables developed over multiple iterations
product backlog
highest priority items delivered
more time spent on refinement
Release versions
Customer is continuously engaged
Collect Requirements
Determine/Document Stakeholder needs and requirements
Inputs to Collect Requirements
Project Charter
Business Documents
Stakeholder Register
PM Plan
EEF & OPA
Outputs to Collect Requirements
Requirements Documentation
Requirements Traceability Matrix
Data Gathering for Requirements Collection
Interviews (PM Job)
Focus Groups
4 interpersonal requirement techniques
Facilitation (QFD, JAD, User Stories)
Workshops (Cross Functional, Reconcile Differences)
Observation (Job Shadowing)
Nominal Group Technique NGT (Voting Process)
Data Representation Techniques
Affinity Diagram
Mind Mapping
Context Diagrams
Tools and Techniques to Collect Requirements
QFD Quality Function Deployment
-Voice of Customers
JAD Joint Application Development
-Bring business SME’s and developers work together
HOQ House of Quality
What are the 4 interpersonal techniques to gather information
Facilitation
Observation
Workshops
Nominal Group Technique
Facilitation includes what 3 things
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)
what are the 5 Decision making techniques
Unanimity - Everyone agrees
Majority - >50% agrees
Plurality - Largest Block agrees
Autocratic - One persons choice
MCDA (Multi Criteria Decision Analysis) - Decision Matrix
Define Scope
Detailed description of the project / product
(Scope Statement)
Inputs to define Scope
Project Charter
PM Plan
Project Documents
EEF and OPA
Outputs for Define Scope
Project Scope Statement
Project Document Updates
-Assumption Log
Tools and techniques to Define Scope
Expert Judgment
Product Analysis
Data Analysis
Decision Making (MCDA)
What are the 6 tools for Product Analysis
(Alternatives Analysis)
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
What are the ouputs to the Scope Statement
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
Difference between Charter and Scope
Project Charter vs Scope Statement
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
Describe WBS
Work Breakdown Structure
Subdivide project deliverables into smaller more manageable componenets or packages
Inputs to WBS
Project Documents (Scope / Requirements)
PM Plan
EEF and OPA
Outputs to WBS
Scope Baseline
Which includes WBS, WBS Dictionary
Updates project documents
Decomposition of WBS
This is on the TEST
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
WBS Notes
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
