CAPM Practice: Determine how project methodologies influence business analysis processes

Stakeholder landscapes change — new stakeholders emerge as the product evolves, priorities shift, and organizational contexts change. Adaptive projects acknowledge this by treating stakeholder analysis as an ongoing activity rather than a one-time upfront exercise.

**Why not A:** Conducting stakeholder analysis only during the closing phase is far too late. Stakeholder analysis must inform requirements gathering, communication planning, and engagement strategies from the start of the project. Waiting until closing provides no value for these critical planning activities.

**Why not C:** Stakeholder analysis is a core BA responsibility across all methodologies. BAs identify, categorize, and plan engagement for stakeholders as part of their requirements planning work. Claiming it is not a BA responsibility contradicts established BA frameworks like BABOK.

**Why not D:** Performing stakeholder analysis only once at project start fails to account for changing stakeholder landscapes. New stakeholders may emerge, priorities may shift, and organizational contexts may change throughout the project, requiring periodic reassessment of the stakeholder map.