Building & Training the Project Team Flashcards
Resource Management Plan
Traditional approach
How to staff project, manage
Documents: RBS, Resource calendars, project staff assignment, team perf assessment
Responsibility Assignment Matrix (RAM)
Team member matrix with tasks
shows gaps and over/under utilization
(ex: RACI)
Organization Breakdown Structure (OBS)
org chart without names, only roles
Resource Breakdown Structure (RBS)
chart with individuals and resource categories
Projectized organizations
teams led by PM
PM 100% dedicated to project
dedicated team resources
PM can hire
Functional organizations
shared resources
PM must negotiate for resources
PM and resources are PT
Matrixed organizations
hybrid of projectized and functional orgs
logs of negotiation
Multi-Criteria Decision Analysis
analyze people in unbiased manner
criteria: availability, cost, experience, ability, knowledge, skills
RACI
type of RAM R: Responsible/does work A: Accountable/answers to the work C: Consult (SME)/ or Support I: Inform/get notified about status only one person can be A, but people can have more than one role
Stakeholder Analysis
high involvement/low influence: keep satisfied
high involvement/high influence: manage closely
low involvement/low influence: monitor
low involvement/high influence: keep informed
Project Vision
a way to keep stakeholders involved
- show product adds value
- motivates dev team
Project Charter
formal authorization (unlike Team Charter)
Project Charter
formal authorization (unlike Team Charter) sponsor's signature
Kick off meetings attendees
PM, team, sponsor, functional manager, customers, vendors, key stakeholders
Resource Calendar
shows people’s availability, material resources, and skill resources
