• INTRO
    • Domains are a group of related activities for effective delivery
    • Interactive, interdependent, integrated, interrelated focus areas to achieve project outcomes successfully.
    • the context of the org, project, deliverables, team, stakeholders, etc determines activities under each domain.
    • Principles guide behavior for these domains
  • Stakeholder Domain
    • Addresses activities/functions associated with stakeholders
    • Stakeholder agreement with project objectives: productive working relationship [significant number of changes in addition to scope may indicate lack of agreement]
    • Stakeholders who are beneficiaries are supportive while those who oppose do not negatively impact project outcomes [project issue register can show this]
    • Defining a clear vision can enable good alignment.
    • Effective stakeholder engagement steps:
      • Identify: Throughout
      • Understand & Analyze: feelings, beliefs, values
      • Prioritize: focus on the ones with the most power & interest in the project
      • Engage: ALWAYS. keep them participating. manage expectation.
      • Monitor
  • Team Performance Domain
    • Deals with activities/functions associated with people who are responsible for creating project deliverables.
    • Shared ownership, high-performing team, appropriate leadership
    • Aspects of team development:
      • vision & objectives
      • roles & responsibilities
      • Project team operations
      • guidance
      • growth
    • Project team culture:
      • establishing safe, respectful, environment to communicate openly
      • transparency, integrity, respect, positive, support, courage, celebrate success
    • Servant leadership: IMP for the exam for situational questions. Understanding & addressing the needs & developments of the project team.
      • are team members growing as individuals?
      • are team members becoming healthier, wiser, freer, more autonomous
      • are project teams more likely to become servant leaders?
  • Development & Lifecycle Approach
    • activities/functions associated with the development approach, cadence, and lifecycle phases of the project
    • Delivery cadence refers to the timings & frequency of deliverables.
    • Projects can have single delivery, multiple deliveries, or periodic deliveries.
    • Development approach:
      • predictive
      • adaptive, including iterative and incremental
      • hybrid
    • What influences the approach:
      • product, service, or result [scope, innovation, ease change, risk, requirements certainty]
      • the project
      • organization
    • Lifecycle: type & number of project phases in a project life cycle [feasibility, design, build, test, deploy, close]
    • The best approach is what makes your stakeholders happy, where deliverables bring value to your stakeholders.
  • Planning Performance
    • Deals with activities/functions associated with initial, ongoing & evolving organization necessary for delivery
    • The purpose of planning is to proactively develop an approach to create deliverables
    • Time spent planning is appropriate, evolving info is elaborated, manages expectations of stakeholders
    • Plan variables include development approach, project deliverables, organizational requirements
    • Planning: Consider delivery, estimating, schedules, scope, budget, how team will be made, communication w stakeholders, physical resources, planning for changes/risks
  • Work Performance
    • Deals with activities/functions associated with establishing processes, managing resources, and fostering a learning environment. It is connected with establishing the process & performing work done by project team to deliver outcomes
    • Project work keeps the team dedicated & project running correctly. Includes managing work flow, keeping team focused, efficient processes, communication with stakeholders, managing resources, monitoring, enabling knowledge transfer
    • Much of PM’s work is communication & engagement [stakeholders, team, product owners, etc.], balancing constraints, tailoring processes, review task boards
    • Lessons learned & how to improve [retrospectives]
    • The predictive approach has a change log & adaptive has a backlog
  • Delivery Performance
    • deals with activities associated with delivering the scope & quality that the project was taken to achieve
    • delivery is about meeting requirements, scope & quality expectations to produce the deliverable
    • QUALITY: This can be reflected in completion criteria, definition of done, statement of work, or requirements documentation.
  • Measurement Performance
    • deals with activities/functions associated with assessing project performance and takes actions to maintain acceptable performance
    • KEEPING THE PROJECT ON TRACK
    • Domain evaluates the amount to which work done in the delivery performance domain is meeting metrics identified in the planning performance domain
    • Ways to measure: KPIs — leading & lagging. leading predicts changes or trends. lagging measure deliverables or events, provide info after the fact
    • effective metrics: use of SMART criteria (specific, meaningful, achievable, relevant, timely)
    • What to measure:
      • deliverable metrics: info on errors/defects + measures of performance
      • delivery: WIP, lead time, cycle time, process efficiency
      • baseline performance: start & finish dates + actual cost to planned cost
      • resources: planned to actual resource utilization
      • business value: cost-benefit ratio
      • stakeholders: mood chart
      • forecast
    • metrics can be presented using dashboards, information radiators, visual controls
    • pitfalls with measurement: Hawthorne effect [measuring too much], vanity metric/demoralization [can make team look good/bad], misusing the metrics, confirmation bias [measuring just what we want]
    • Threshold/tolerance: when measuring, establishing what’s acceptable & what’s not
  • Uncertainty Performance
    • deals with activities/functions associated with risk & uncertainty
    • awareness of project environment, proactively exploring/responding to uncertainty, cost & schedule reserves are utilized
    • uncertainty can present threats/opportunities that teams explore, assess & handle
    • Risk/ambiguity/complexity/volatility — respond gather info, prepare for multiple outcomes, build in resilience.