PMP Certification Master Study Guide: PMBOK 7th & 8th Editions & Agile Practice Guide

PMBOK Process Groups & Project Foundations

• Project Definition:

  • A Project is a temporary endeavor undertaken to deliver change, creating a unique product, service, or result that provides business or customer value. It has a definitive start and end date.
  • Project Lifecycle: The sequence of phases that a project passes through from its inception to its completion (e.g., Feasibility Study, Customer Requirements, Build, Test, Transition).
  • Phase Gates: Strategic review points situated between project phases where performance is evaluated against project objectives to decide whether to proceed to the next phase, modify direction, or terminate the project.

• Development Approaches:

  • The Development Approach determines the delivery technique utilized throughout the project lifecycle:
  • Predictive: Requirements are fixed upfront. Activities are performed once for the entire project. Features a single final delivery with the primary goal of managing costs.
  • Iterative: Requirements are dynamic. Activities are repeated until correct. Features a single final delivery with the primary goal of solution correctness.
  • Incremental: Requirements are dynamic. Activities are performed once for a given increment. Features frequent smaller deliveries with the primary goal of speed.
  • Adaptive (Agile): Requirements are dynamic. Activities are repeated iteratively until correct. Features frequent small deliveries with the primary goal of maximizing customer value via continuous feedback.
  • Hybrid: Any combination of Predictive and Adaptive approaches, tools, or delivery styles tailored to project needs.

• The Triple Constraint:
  • The core project constraints consist of Scope, Cost, and Time, which collectively determine Quality.
  • Adjusting any single constraint inevitably impacts the remaining constraints.

• Organizational Roles and Authority Structure:
  • Project Manager (PM): Person assigned by the performing organization to lead the team responsible for achieving project objectives and delivering business value.
  • Functional Manager: Focuses on providing administrative and technical oversight over a specific functional or business unit.
  • Operations Manager: Responsible for maintaining smooth, ongoing business operational efficiency.
  • Project Manager Authority by Structure Type:
  • PMO / Project-Oriented: High to total authority, high to total resource availability, budget managed by Project Manager.
  • Matrix – Strong: Moderate to high authority, moderate to high resource availability, budget managed by Project Manager.
  • Matrix – Balanced: Low to moderate authority, low to moderate resource availability, mixed budget management.
  • Hybrid / Virtual: Low to moderate authority, mixed resource management.
  • Matrix – Weak / Multi-divisional / Functional (Centralized): Low authority, low resource availability, budget managed by Functional Manager.
  • Organic or Simple: Low authority, low resource availability, budget managed by Owner or Operator.

• Project Management Office (PMO) Types:
  • Directive PMO: Directs and manages projects directly. Project Managers are assigned by and report directly to the PMO. Exercises a High degree of control.
  • Controlling PMO: Provides support and enforces compliance through required methods, frameworks, templates, forms, and governance tools. Exercises a Moderate degree of control.
  • Supportive PMO: Acts as a consultative repository supplying templates, best practices, training, and historical project information. Exercises a Low degree of control.

• Project Manager Competencies (PMI Talent Triangle):
  • Ways of Working: Mastering diverse delivery methods (Agile, Waterfall, Hybrid) and tailoring methods to the environment.
  • Power Skills: Soft skills, collaborative leadership, emotional intelligence, and effective communication.
  • Business Acumen: Understanding organizational priorities, financial evaluation (cost versus benefit), strategic decision-making, and continuous domain learning.

Project Governance & Baseline Management

• Governance Process Mapping:

  • Focus Area 1: Initiate Project or Phase | Process Group: Initiate | Main Output: Project Charter
  • Focus Area 2: Integrate and Align Project Plan | Process Group: Plan | Main Output: Project Management Plan
  • Focus Area 3: Plan Sourcing Strategy | Process Group: Plan | Main Output: Sourcing Strategy Plan
  • Focus Area 4: Manage Project Execution | Process Group: Execute | Main Output: Project Deliverables, Work Performance Data
  • Focus Area 5: Manage Quality Assurance | Process Group: Execute | Main Output: Quality Reports
  • Focus Area 6: Manage Project Knowledge | Process Group: Execute | Main Output: Lessons Learned Register
  • Focus Area 7: Monitor and Control Project Performance | Process Group: Monitor & Control | Main Output: Work Performance Reports
  • Focus Area 8: Assess and Implement Changes | Process Group: Monitor & Control | Main Output: Approved Change Requests
  • Focus Area 9: Close Project or Phase | Process Group: Close | Main Output: Final Report, Final Product Transition

• Key Governance Artifact Comparison:

  • Business Case: Feasibility evaluation answering whether a project is required. Includes business/customer need, situation analysis, solution options, and final recommendation.
  • Benefits Management Plan: Describes how and when benefits will be delivered, along with target measurement metrics.
  • Project Charter: Formally authorizes the existence of a project and gives the Project Manager authority to apply organizational resources. Issued by the project initiator or sponsor.
  • Project Management Plan: Comprehensive master document encompassing all subsidiary plans (Scope, Schedule, Cost, Quality, etc.) and baselines.

• Project Logs Comparison:

  • Change Log: Records all requested changes to baselined items and tracks their current approval status.
  • Issue Log: Documents active project problems, severity, current status, and assigned resolution owners.
  • Assumption Log: Records all assumptions and dependencies made during project planning and estimation.

• Change and Configuration Management Plans:

  • Configuration Management Plan: Defines which project items and deliverables are baselined and tracks their specific version control.
  • Change Management Plan: Outlines the exact formal process for raising, evaluating, reviewing, and approving changes to baselined project items.

• Baseline and Change Control Execution:

  • Project Baseline: Approved version of work plans encompassing Scope Baseline, Schedule Baseline, Cost Baseline, and Performance Measurement Baseline.
  • Change Workflow:
  1. Stakeholder raises formal change request.
  2. Review impact against all baselines.
  3. Present change request to authorizer (Change Control Board - CCB, Sponsor, PM, or Team Member).
  4. Communicate outcome to stakeholders.
  5. Record result in the Change Log.

• Scope Creep: Uncontrolled expansion of scope without adjustments to time, cost, or resources.

• Gold Plating: Delivering extra, unrequested features to the customer beyond documented requirements.

  • Work Performance Data Flow:

• Work Performance Data: Raw project measurements collected during activity execution (e.g., defect counts, exact durations).

• Work Performance Information: Data analyzed and aggregated in relation to baselines to make it meaningful (e.g., scope delivered over time).

• Work Performance Reports: Formal representations of work performance information formatted for stakeholder decisions and actions.

• Project & Phase Closure Procedures:
  • Verify all procurement documentation is finalized, claims resolved, and contracts closed.
  • Complete final release of project physical and human resources.
  • Conduct retrospectives to document lessons learned and archive into Organizational Process Assets (OPAs).
  • Prepare the Final Report summarizing performance against original objectives and complete final product transition.

Stakeholder Engagement & Project Communication

• Stakeholder & Communication Process Mapping:

  • Focus Area 1: Identify Stakeholders | Process Group: Initiate | Output: Stakeholder Register
  • Focus Area 2: Plan Stakeholder Engagement | Process Group: Plan | Output: Stakeholder Engagement Plan
  • Focus Area 3: Plan Communications Management | Process Group: Plan | Output: Communications Management Plan
  • Focus Area 4: Manage Stakeholder Engagement | Process Group: Execute | Output: Change Requests
  • Focus Area 5: Manage Communications | Process Group: Execute | Output: Project Communications
  • Focus Area 6: Monitor Stakeholder Engagement | Process Group: Monitor & Control | Output: Work Performance Information, Change Requests
  • Focus Area 7: Monitor Communications | Process Group: Monitor & Control | Output: Work Performance Information, Change Requests, Plan/Document Updates

• Stakeholder Engagement Assessment & Mapping:

  • Stakeholder Register: Captures names, titles, organizational roles, power/interest scores, specific expectations, and communication needs.
  • Engagement Classification: Evaluates stakeholders across states: Unaware, Resistant, Neutral, Supportive, and Leading. Matrix tracks Current ($C$) vs. Desired ($D$) engagement.

• Mapping Frameworks:
  • Impact / Influence Grid: Categorizes stakeholders into quadrants: Monitor (low impact, low influence), Maintain (low impact, high influence), Keep Informed (high impact, low influence), and Collaborate With (high impact, high influence).
  • Salience Model: Classifies stakeholders based on three dimensions: Power, Urgency, and Legitimacy (represented as a 3D/Cube matrix).

• Directions of Influence:

  • Upward: Senior management, Project Sponsor, Steering Committee.
  • Downward: Project team members, subject matter experts.
  • Sideward: Peer Project Managers, Functional Managers competing for resources.
  • Outward: Third-party vendors, suppliers, customers, government agencies.

• Communication Channel Formula:

  • Calculation for total formal communication channels among $N$ stakeholders:   $\text{Channels} = \frac{N \times (N - 1)}{2}$
  • Example: For a team of $N = 10$ individuals:   $\text{Channels} = \frac{10 \times (10 - 1)}{2} = \frac{90}{2} = 45$

• Predictive vs. Agile Communication Styles:

  • Predictive: Formally planned communication schedules captured within the Communications Management Plan.
  • Agile: Prioritizes face-to-face, real-time communication. Uses co-located teams, osmotic learning, paired work, and transparent Information Radiators on team walls instead of heavy status decks.

• The Five Cs of Communication:

  • Correct grammar and spelling.
  • Concise expression with redundant words removed.
  • Clear purpose tailored to audience needs.
  • Coherent, logical flow of concepts.
  • Controlling the flow of ideas and structure.

• Push vs. Pull Communication:

  • Push Communication: Information sent directly to specific recipients who require it (e.g., emails, status reports, phone calls, letters).
  • Pull Communication: Centralized repositories where recipients access content at their own discretion (e.g., intranet web portals, databases, e-learning platforms).

Scope & Quality Management

• Scope Process Mapping:

  • Focus Area 1: Plan Scope Management | Process Group: Plan | Output: Scope Management Plan, Requirements Management Plan
  • Focus Area 2: Elicit and Analyze Requirements | Process Group: Plan | Output: Requirements Documentation
  • Focus Area 3: Define Scope | Process Group: Plan | Output: Project Scope Statement (Scope Description, Deliverable List, Acceptance Criteria, Exclusions)
  • Focus Area 4: Develop Scope Structure | Process Group: Plan | Output: Scope Baseline (Scope Statement, WBS, WBS Dictionary, Work Packages) / Agile: Product Backlog, User Stories
  • Focus Area 5: Monitor & Control Scope | Process Group: Monitor & Control | Output: Quality Reports, Verified Deliverables
  • Focus Area 6: Validate Scope | Process Group: Monitor & Control | Output: Accepted Deliverables

• Requirements Traceability Matrix (RTM):

  • Links requirements from initial high-level business objectives through user stories, work packages, test cases, and final deliverable sign-offs.

• Work Breakdown Structure (WBS) & Decomposition:

  • Decomposition: Technique of subdividing total project scope into progressively smaller, more manageable components.
  • WBS: Hierarchical breakdown of the total scope of work to be carried out by the project team.
  • WBS Dictionary: Document containing detailed auxiliary information for each WBS component (e.g., codes of account, statement of work, responsible organization, schedule milestones, cost estimates, acceptance criteria).
  • Work Package: The lowest level component of the WBS where cost and duration can be reliably estimated and managed.

• Control Scope vs. Validate Scope:

  • Control Scope / Quality Control: Internal verification process checking that deliverables are technically correct and meet quality requirements (Verified Deliverables).
  • Validate Scope: Formal process of obtaining customer or sponsor acceptance of completed deliverables (Accepted Deliverables).

• Cost of Quality (CoQ):

  • Cost to Fix: The cost of resolving defects increases exponentially as the deliverable progresses through project phases toward release.

• Cost of Conformance:

  • Prevention Costs: Money spent to prevent errors (e.g., training, process documentation, equipment maintenance, refactoring).
  • Appraisal Costs: Money spent to inspect or evaluate quality (e.g., testing, audits, inspections, reviews).

• Cost of Non-Conformance:

  • Internal Failure Costs: Costs incurred when defects are caught before delivery (e.g., rework, scrap, re-testing).

  • External Failure Costs: Costs incurred when defects reach the customer (e.g., warranty claims, recall costs, customer support, lost reputation).

  • Quality & Root Cause Analysis Frameworks:

• PDCA Cycle (Deming/Shewhart): Plan (identify root cause), Do (pilot solution), Check (verify test data), Act (adjust or operationalize standard).

• Six Sigma (DMAIC): Define problem, Measure current state, Analyze root causes, Improve process, Control variations.
• Ishikawa Diagram (Fishbone / Cause-and-Effect): Brainstorms causes placed into primary category categories (PIPS: People, Information, Process, Systems).

• Five Whys: Repeatedly asking "Why" to move past surface symptoms to the root cause.
• Pareto Analysis: 80/20 rule histogram that orders defect categories from highest to lowest frequency to highlight the vital few factors causing the majority of issues.

Schedule & Financial Management

• Schedule Process Mapping:

  • Focus Area 1: Plan Schedule Management | Process Group: Plan | Output: Schedule Management Plan
  • Focus Area 2: Develop Schedule | Process Group: Plan | Output: Schedule Baseline, Project Schedule, Schedule Data, Activity List, Milestone List
  • Focus Area 3: Monitor & Control Schedule | Process Group: Monitor & Control | Output: Work Performance Information, Schedule Forecasts, Change Requests

• Precedence Diagramming Method (PDM):

  • Finish-to-Start (FS): Successor activity cannot start until predecessor has finished.
  • Start-to-Start (SS): Successor activity cannot start until predecessor has started.
  • Finish-to-Finish (FF): Successor activity cannot finish until predecessor has finished.
  • Start-to-Finish (SF): Successor activity cannot finish until predecessor has started.

• Resource Optimization & Schedule Compression:

  • Resource Leveling: Adjusts start/finish dates when shared resources are over-allocated. Often changes the Critical Path.
  • Resource Smoothing: Adjusts activities within free and total float limits so the critical path is not altered.
  • Fast Tracking: Performing critical path activities in parallel rather than sequentially. Increases risk and rework.
  • Crashing: Adding extra resources to critical path tasks to reduce duration. Increases cost and risks diminishing returns.

• Critical Path Method (CPM):

  • The Critical Path is the sequence of activities that represents the longest path through a project, determining the shortest possible project duration.
  • Forward Pass: Determines Early Start ($ES$) and Early Finish ($EF$):   $EF = ES + \text{Duration} - 1$$ES = \max(EF_{\text{predecessors}}) + 1$
  • Backward Pass: Determines Late Finish ($LF$) and Late Start ($LS$):   $LS = LF - \text{Duration} + 1$$LF = \min(LS_{\text{successors}}) - 1$
  • Float (Slack): Amount of time an activity can be delayed without delaying the project finish date:   $\text{Float} = LS - ES = LF - EF$
  • Critical Path activities have a total float equal to $0$

• Estimating Techniques:

  • Analogous: Compares against past historical projects. Fast, low cost, but lower accuracy.
  • Parametric: Mathematical calculation using historical data and parameters (e.g., $\$100\,/\text{hour}$, $\$55\,/\text{meter}$).
  • Bottom-Up: Aggregates estimates from individual lower-level work packages up to total project level. Highly accurate, high effort.
  • Triangular (3-Point) Estimate:   $E = \frac{O + M + P}{3}$
  • PERT / Beta Distribution Estimate:   $E = \frac{O + 4M + P}{6}$
  • Wideband Delphi (Planning Poker): Iterative estimation technique where team members estimate anonymously, discuss high/low outliers, and re-vote until consensus is reached.

• Budget Construction & Reserve Structure:

  • Work Package Estimates + Contingency Reserves = Cost Baseline.
  • Cost Baseline + Management Reserves = Project Budget.
  • Contingency Reserves: Allocated for identified "known-unknowns" (risks in the Risk Register).
  • Management Reserves: Allocated for unidentified "unknown-unknowns" (unforeseen scope within project domain).

• Earned Value Analysis (EVA):
  • Budget at Completion (BAC): Total planned baseline budget.
  • Planned Value (PV): Authorized budget assigned to work scheduled up to a given point in time.
  • Earned Value (EV): Measure of work performed expressed in terms of authorized budget.
  • Actual Cost (AC): Real cost incurred for work performed.

• Earned Value Formulas:
  • Cost Variance (CV):   $CV = EV - AC$(Positive = Under Budget, Negative = Over Budget)
  • Schedule Variance (SV):   $SV = EV - PV$(Positive = Ahead of Schedule, Negative = Behind Schedule)
  • Cost Performance Index (CPI):   $CPI = \frac{EV}{AC}$(Greater than $1.0$ = Under Budget, Less than $1.0$ = Over Budget)
  • Schedule Performance Index (SPI):   $SPI = \frac{EV}{PV}$(Greater than $1.0$ = Ahead of Schedule, Less than $1.0$ = Behind Schedule)

Resource, Risk & Procurement Management

• Resource Process Mapping:

  • Focus Area 1: Plan Resource Management | Process Group: Plan | Output: Resource Management Plan, Team Charter
  • Focus Area 2: Estimate Resources | Process Group: Plan | Output: Resource Requirements, RBS
  • Focus Area 3: Acquire Resources | Process Group: Execute | Output: Assignments, Resource Calendars
  • Focus Area 4: Lead the Team | Process Group: Execute | Output: Team Performance Assessments
  • Focus Area 5: Monitor & Control Resourcing | Process Group: Monitor & Control | Output: Work Performance Information

• Team Lifecycle & RACI Framework:

  • Tuckman's Ladder: Forming (orientation), Storming (conflict/differing styles), Norming (cohesion), Performing (high trust/synergy), Adjourning (project wrap-up).
  • RACI Matrix: Defines explicit team assignments:
  • R - Responsible: Doer of the activity.
  • A - Accountable: Ultimate sign-off authority (Only one Accountable per task).
  • C - Consulted: SME providing two-way inputs.
  • I - Informed: Kept updated on progress via one-way communication.

• Conflict Resolution Modes:

  • Collaborate / Problem Solve: Win-Win. Integrates multiple perspectives. Preferred standard approach.
  • Force / Direct: Win-Lose. Pushes one viewpoint using formal authority. Used in urgent emergencies.
  • Compromise / Reconcile: Lose-Lose. Both sides give up something to find a middle ground.
  • Smooth / Accommodate: Lose-Win. Concedes position to maintain relationship harmony.
  • Withdraw / Avoid: Retreats from the issue temporarily to allow cooling off or gathering facts.

• Organizational Motivation Theories:

  • Maslow's Hierarchy: Physiological Needs $\rightarrow$ Safety Needs $\rightarrow$ Love/Belonging $\rightarrow$ Esteem $\rightarrow$ Self-Actualization. Lower levels must be met before upper levels motivate.

• Herzberg's Two-Factor Theory: Hygiene Factors (salary, working conditions, job security) eliminate dissatisfaction; Motivational Factors (achievement, recognition, meaningful work) build intrinsic drive.

• McGregor's Theory X and Y: Theory X assumes workers are lazy and require strict control; Theory Y assumes workers are self-motivated and take pride in quality output.

• Parkinson's Law: Work expands to fill the total time allocated to its completion.

• Student Syndrome: People delay starting tasks until the last possible minute before a deadline.

  • Risk Management & Analysis Tools:

• Risk Register: Active document tracking Risk Title, Category, Probability, Impact, Score, Responses, and Owners.

• Risk Breakdown Structure (RBS): Hierarchical categorization of potential risks.

• Probability and Impact Matrix: Evaluates and prioritizes qualitative risk exposure scores.

• Quantitative Risk Tools:
  • Tornado Diagram (Sensitivity Analysis): Compares relative impact of variables with high uncertainty against stable baselines.

* **Decision Tree Analysis**: Evaluates Expected Monetary Value ($EMV$) across branches:

    $EMV = \text{Probability} \times \text{Financial Impact}$

* **Monte Carlo Simulation**: Computer-simulated statistical model running thousands of project scenarios to derive probability distributions of schedule/cost outcomes.

• Risk Strategies Summary:

  • Threat Responses: Escalate (outside authority), Avoid (eliminate threat scope), Transfer (shift to third party), Mitigate (reduce probability/impact), Accept (passive or active reserve monitoring).
  • Opportunity Responses: Escalate (outside scope), Exploit (ensure realization), Share (partner with third party), Enhance (increase probability/impact), Accept (take advantage if it occurs).

• Procurement Process & Dispute Resolution:

  • Procurement Steps: Make or Buy Analysis $\rightarrow$ Procurement Strategy $\rightarrow$ Statement of Work (SOW) $\rightarrow$ Source Selection Criteria $\rightarrow$ Send Bid Documents $\rightarrow$ Collect Proposals $\rightarrow$ Select Seller & Sign Contract.

• Alternative Dispute Resolution (ADR) Sequence:
  1. Negotiation: Direct discussion between parties.
  2. Mediation: Neutral third party facilitates consensus.
  3. Arbitration: Independent panel issues binding ruling.
  4. Litigation: Formal court lawsuit as a last resort.
• Contract Types:
  • Fixed Price: Firm Fixed Price (FFP), Fixed Price Incentive Fee (FPIF), Fixed Price Economic Price Adjustment (FP-EPA). Best when requirements are locked down.
  • Cost Reimbursable: Cost Plus Fixed Fee (CPFF), Cost Plus Incentive Fee (CPIF), Cost Plus Award Fee (CPAF). Best when scope is evolving.
  • Time and Materials (T&M): Hybrid model charged per hour/unit. Best for external staff augmentation.

Artificial Intelligence & Emerging Trends

• AI System Classification:
  • Artificial Intelligence (AI): Systems capable of autonomous reasoning, learning, and action.
  • Machine Learning (ML): AI subfield utilizing data-driven neural networks to predict outputs from inputs.
  • Deep Learning (DL): Advanced ML leveraging multi-layered artificial neural networks for complex feature extractions.
  • Generative AI (GenAI): DL subset using Large Language Models (LLMs) to synthesize new text, media, code, and imagery.
  • GPT: Generative Pre-trained Transformer architecture.

• AI Application Strategies:
  • Automation: Automated reporting, process automation, real-time telemetry monitoring, routine task tracking.
  • Assistance: Dynamic schedule optimization, risk impact modeling, schedule conflict resolution.
  • Augmentation: Brainstorming idea generation, predictive risk identification, stakeholder sentiment analysis.

• AI Implementation Ethics & Risks:
  • Bias: Algorithmic skew inherited from biased training datasets.
  • Data Privacy: Protection of sensitive corporate data from public training models.
  • Accountability: Maintaining human-in-the-loop oversight over output decisions.
  • Reliability & Hallucinations: Validating factual accuracy of generated data.
  • Copyright & IP: Intellectual property ownership challenges regarding generated media.

Agile Practice Guide & Frameworks

• Agile Overview & Relationships:
  • Agile combines Iterative (regular reflection and refinement) and Incremental (frequent small releases) approaches to navigate complex, high-uncertainty environments.

• Agile Manifesto Values:

  • Individuals and Interactions over Processes and Tools.
  • Working Software over Comprehensive Documentation.
  • Customer Collaboration over Contract Negotiation.
  • Responding to Change over Following a Plan.

• Complexity Modeling (Stacey Matrix):

  • Plots Requirements Uncertainty against Technical Uncertainty:
  • Simple: Linear approaches (Waterfall).
  • Complicated / Complex: Adaptive approaches (Agile).
  • Chaos: High technical and requirements uncertainty; inherently risky.

• Agile Team Structure & Servant Leadership:

  • Dedicated, small teams ($3$ to $12$ cross-functional members) working in co-located or virtual open environments.
  • T-Shaped Roles (Generalizing Specialists): Deep domain specialization combined with broad cross-functional skills.
  • Product Owner (PO): Maximizes value by owning and prioritizing the Product Backlog.
  • Team Facilitator / Scrum Master: Servant leader who removes blockers, facilitates ceremonies, coaches team dynamics, and protects team focus.

• Scrum Core Ceremonies:

  • Sprint Planning: Timeboxed session where team commits to user stories matching their velocity.
  • Daily Stand-up: $15$-minute daily sync answering: What did I complete yesterday? What will I work on today? Are there any blockers?
  • Backlog Refinement (Grooming): Continuous breaking down of features into estimated user stories with acceptance criteria.
  • Sprint Review: End-of-sprint working demonstration to stakeholders to collect immediate feedback.
  • Retrospective: Team process reflection focusing on continuous improvement (Kaizen).

• Kanban Framework:
  • Visual system managing flow. Key principle: Limit Work in Progress (WIP) to prevent multitasking bottlenecks and optimize cycle times.

• Crystal Sizing Framework:
  • Scaled framework based on Team Size ($1-6$ clear, $7-20$ yellow, $21-40$ orange, $41-100$ red, $100-200$ maroon) and Project Criticality (Comfort, Discretionary Money, Essential Money, Life).

• DSDM Inverted Constraint Triangle:
  • In traditional projects, Scope is fixed while Time/Cost are variable. In DSDM/Agile, Time, Cost, and Quality are Fixed, while Scope is Variable (managed via MoSCoW prioritization).

• Scaling Agile (Scrum of Scrums):
  • Multi-team coordination model where representatives from individual Scrum teams attend higher-level syncs to manage cross-team dependencies and impediments.

• Human-Centered Design (Double Diamond):
  • Framework dividing problem-solving into four steps: Discover (diverge), Define (converge on problem definition), Develop (diverge on solutions), and Deliver (converge on deployed output).

PMBOK Guide 7th Edition Performance Domains & Models

• 12 Principles of Project Management:

  1. Diligent, respectful, and caring stewardship.
  2. Collaborative team environment.
  3. Effective stakeholder engagement.
  4. Focus on value.
  5. Systems thinking & interactions.
  6. Leadership behaviors.
  7. Tailored delivery approach.
  8. Quality built into processes & deliverables.
  9. Navigating complexity.
  10. Optimized risk responses.
  11. Adaptability & resiliency.
  12. Enabling change to achieve envisioned future state.

• Product Lifecycle Management:

  • Manages product development across phases: Introduction $\rightarrow$ Growth $\rightarrow$ Maturity $\rightarrow$ Decline / Retirement.

• Emotional Intelligence (EI) Quadrants:
  • Self-Awareness: Understanding how you affect the team.
  • Self-Management: Thinking before acting and building trust.
  • Social Awareness: Practicing empathy and active listening.
  • Social Skill: Establishing rapport and managing team dynamics.

• Organizational Change Models:
  • ADKAR: Awareness $\rightarrow$ Desire $\rightarrow$ Knowledge $\rightarrow$ Ability $\rightarrow$ Reinforcement.
  • Kotter's 8 Steps: Create Urgency $\rightarrow$ Form Coalition $\rightarrow$ Create Vision $\rightarrow$ Communicate Vision $\rightarrow$ Remove Obstacles $\rightarrow$ Create Short-Term Wins $\rightarrow$ Build on Change $\rightarrow$ Anchor in Culture.
  • Satir Change Model: Late Status Quo $\rightarrow$ Foreign Element $\rightarrow$ Chaos $\rightarrow$ Transforming Idea $\rightarrow$ Integration $\rightarrow$ New Status Quo.
  • Bridges Transition Model: Manages psychological transition through Ending, Neutral Zone, and New Beginning.

PMP Exam Fast Track & Content Outline (ECO)

• Universal Exam Mindset Rules:

  • Assess First: Never take drastic action before evaluating impact, reviewing relevant management plans, or uncovering root causes.
  • Collaborate: Choose options emphasizing team inclusion, coaching, and stakeholder alignment.
  • Do Not Escalate Early: Resolve issues directly with functional managers or team members before escalating to senior executives.
  • Proactive PM: The PM is an empowered servant leader who removes impediments and protects psychological safety.

• ECO Focus Domain Tasks Summary:

  • People Domain (42%):
  • Manage Conflict: Analyze context, implement agreed resolution strategies.
  • Lead Team: Determine leadership style, empower team members, support diversity.
  • Support Team Performance: Measure against KPIs, appraise performance, clear blockers.
  • Process Domain (50%):
  • Execute Scope & Baselines: Manage scope changes through CCB; avoid scope creep/gold plating.
  • Manage Risks: Continually evaluate probability/impact and maintain active Risk Register.
  • Manage Communications & Stakeholders: Deliver tailored messages via pull/push channels.
  • Business Environment Domain (8%):
  • Manage Compliance: Verify regulatory, safety, and quality compliance requirements.
  • Evaluate External Changes: Survey external environmental changes (market, geopolitical, legal) and adjust product backlog/scope priority accordingly.