Impact Project Stakeholders: Prioritization and Analysis for the Exam

Impact Project Stakeholders: Prioritization and Analysis for the Exam

PMBOK v8 Definition

Stakeholders with the most interest and the highest influence are often prioritized at the top of the list. Commonly used methods include MoSCoW (must have, should have, could have, and will not have), 100-point method, cost of delay, and Kano analysis. Prioritization rules may be specified by the organization in advance of the project and included in organizational process assets, or they may be tailored to the specific project.

Why It Matters for the Exam

This concept appears frequently in questions about stakeholder engagement, requirements prioritization, and risk management. You will see it in situational questions where you must determine which stakeholders to engage first or how to balance competing interests. The PMI exam tests your ability to apply prioritization methods correctly in real-world scenarios.

Key Points to Remember (for the exam)

  • Primary Prioritization Criteria: Stakeholders with the most interest and highest influence are prioritized first
  • Four Key Methods: MoSCoW, 100-point method, cost of delay, and Kano analysis
  • MoSCoW Breakdown: Must have, Should have, Could have, Will not have
  • Organizational Context: Prioritization rules may be specified in advance (organizational process assets) or tailored to the specific project
  • Risk Connection: Probability and impact matrix is the grid for mapping risk probability and impact on project objectives
  • Stakeholder Risk Appetite: Recorded in the risk management plan; expressed as measurable risk thresholds around each project objective
  • Common Confusion: Do not confuse stakeholder prioritization methods (MoSCoW, 100-point) with risk prioritization tools (probability and impact matrix)

Typical PMI Exam Example

You are managing a software development project with 15 identified stakeholders. During stakeholder analysis, you discover that the product owner has high influence but moderate interest, while end users have high interest but low influence. Using the PMBOK v8 approach, which stakeholders should be prioritized first? Answer: Those with the highest combination of interest and influence, starting with the product owner.

PMI Exam Traps

  • Trap: Thinking MoSCoW is only for requirements prioritization

    • Reality: MoSCoW is also a stakeholder prioritization method per PMBOK v8
  • Trap: Confusing the 100-point method with the probability and impact matrix

    • Reality: 100-point method is for stakeholder/requirement prioritization; probability and impact matrix is for risk prioritization
  • Trap: Assuming all prioritization rules come from the organization

    • Reality: Rules may be specified in advance OR tailored to the specific project
  • Trap: Believing stakeholder risk appetite is documented in the stakeholder register

    • Reality: Stakeholder risk appetite is recorded in the risk management plan

Important PMI Connections

Related ConceptRelationship TypeExam Attention Point
Probability and Impact MatrixComplementary ToolUsed for risk prioritization, not stakeholder prioritization
Risk Management PlanContains Stakeholder Risk AppetiteRisk appetite informs probability and impact definitions
Organizational Process AssetsSource of Prioritization RulesRules may be predefined or tailored
Stakeholder Engagement PlanOutput of Stakeholder AnalysisPrioritization feeds into engagement strategies

Quick Review Questions

  1. Which two criteria are used to prioritize stakeholders according to PMBOK v8?

  2. Name the four categories in the MoSCoW method.

  3. Where is stakeholder risk appetite recorded in project documentation?

  4. What is the difference between the 100-point method and the probability and impact matrix?

  5. Can prioritization rules be tailored to a specific project, or must they come from organizational process assets?

PMBOK v8 Reference

Section 5 – Tools and Techniques (Probability and Impact Matrix, Stakeholder Prioritization Methods)