Logo

PM Quest

Document View

Phase 2 Review (Process Domain)

Core Focus: Phase 2 covers the Process domain (worth 50% of the PMP exam). It spans predictive planning, agile execution, integration, and risk management.

🔑 Key Chapter Breakdown

1. Agile & Adaptive Approaches (Chapter 3)

  • Roles:
    • Product Owner: Prioritizes the backlog, defines business value, aligns with customer.
    • Scrum Master: Servant leader, removes impediments, coaches the team.
    • Development Team: Technical experts, self-organizing, estimates work.
  • Key Concepts: WIP limits (Kanban), Sprint Burndowns, Customer feedback loops.

2. Integration & Scope (Chapter 4)

  • Project Charter: Approved by Sponsor, authorizes the project, establishes high-level requirements.
  • Scope Baseline: Project Scope Statement + WBS + WBS Dictionary.
  • Scope Creep vs. Gold Plating: Scope creep is unapproved scope addition; Gold Plating is adding unrequested features (never acceptable).

3. Schedule & Cost (Chapter 5)

  • Critical Path Method (CPM): The longest path of dependent activities. Float = 0.
  • Earned Value Management (EVM):
    • CV = EV - AC (Cost Variance)
    • SV = EV - PV (Schedule Variance)
    • CPI = EV / AC (Cost Performance Index: >1 is good, <1 is over budget)
    • SPI = EV / PV (Schedule Performance Index: >1 is good, <1 is behind schedule)
    • EAC = BAC / CPI (Estimate At Completion)
  • Schedule Compression: Crashing (adds cost) vs. Fast-Tracking (adds risk/rework).

4. Quality, Risk, & Procurement (Chapter 6)

  • Quality vs. Grade: Quality is compliance with requirements; Grade is degree of feature sophistication.
  • Risk Responses: Avoid, Mitigate, Transfer, Accept (threats). Exploit, Share, Enhance, Accept (opportunities).
  • Procurement Contracts: Fixed Price (seller bears risk) vs. Cost Reimbursable (buyer bears risk).

🎓 Phase 2 PMP Mindset Rules

  1. Change Control Process (Predictive): Any change in a predictive project must go through the Change Control Board (CCB). Follow the process: Identify -> Analyze Impact -> Submit CR -> Get CCB decision -> Update logs/plans -> Implement.
  2. No Change Requests in Agile: Agile scope changes are handled by the Product Owner prioritizing them in the Product Backlog for the next sprint.
  3. Plan is the Map: In predictive projects, refer back to the project management plan constantly.
  4. Agile Self-Organization: Agile teams manage their own tasks. The PM only steps in as a servant leader to coach and facilitate conflict resolution.