CCBA Stakeholder Engagement and Communication 1 — Questions and Answers
Question 1: What is the PRIMARY purpose of stakeholder analysis in business analysis?
- To rank stakeholders by their seniority in the organization
- To understand stakeholders' needs, influences, and attitudes to plan effective engagement (Correct answer)
- To identify which stakeholders should be excluded from the project
- To document stakeholder contact information for project records
Correct answer: To understand stakeholders' needs, influences, and attitudes to plan effective engagement
Stakeholder analysis examines stakeholders' interests, influence, impact, and attitude toward the change to enable the business analyst to plan appropriately tailored engagement strategies.
Stakeholder analysis creates a comprehensive understanding of each stakeholder's relationship to the initiative: their interests and stakes in the outcome, their level of influence over the initiative, the impact the change will have on them, and their current attitude (supportive, neutral, or resistant). This understanding enables the business analyst to plan engagement strategies that address concerns, leverage support, and ensure all relevant perspectives are captured.
Question 2: Which of the following BEST describes the role of a business analyst in stakeholder communication?
- Passing messages from project management to business stakeholders
- Acting as a bridge between business and technical stakeholders by translating requirements into language appropriate for each audience (Correct answer)
- Writing all project status reports on behalf of the project manager
- Ensuring that only approved information reaches stakeholders
Correct answer: Acting as a bridge between business and technical stakeholders by translating requirements into language appropriate for each audience
A key business analyst role is translating between business and technical domains — ensuring that business stakeholders' needs are understood by technical teams and that technical realities are communicated in business terms.
Business analysts serve as communication bridges between business stakeholders and technical teams. They translate business needs into requirements that developers can implement, and they translate technical constraints, options, and impacts back into business language that stakeholders can understand and act on. This bridging role is one of the most critical value-adds that business analysts bring to projects.
Question 3: An influential stakeholder is resistant to a proposed change. What is the MOST effective first step for the business analyst?
- Escalate the resistance to senior management immediately
- Seek to understand the stakeholder's concerns and address them through dialogue (Correct answer)
- Proceed without the stakeholder's input to avoid delays
- Document the resistance and move on with other stakeholders
Correct answer: Seek to understand the stakeholder's concerns and address them through dialogue
Understanding the root of resistance is the first step — the business analyst should engage the stakeholder to understand their concerns before attempting to resolve or escalate the situation.
Stakeholder resistance often stems from legitimate concerns — fear of job impact, doubts about solution viability, past negative experiences with change, or genuine disagreement about the approach. The business analyst's first step should be empathetic engagement: listening to understand the specific concerns, acknowledging them, and exploring whether requirements or the solution approach can address them. This builds trust and often transforms resisters into advocates.
Question 4: What is an 'influence/interest grid' used for in stakeholder engagement planning?
- Measuring the financial interest stakeholders have in the project
- Categorizing stakeholders by their level of influence and interest to prioritize engagement effort (Correct answer)
- Determining stakeholders' technical expertise levels
- Assigning stakeholders to project workstreams
Correct answer: Categorizing stakeholders by their level of influence and interest to prioritize engagement effort
An influence/interest grid categorizes stakeholders into quadrants based on their level of influence and interest, helping the business analyst determine how much engagement effort to invest with each group.
The influence/interest (or power/interest) grid maps stakeholders into four quadrants: high influence/high interest (manage closely), high influence/low interest (keep satisfied), low influence/high interest (keep informed), and low influence/low interest (monitor). This categorization guides the business analyst in allocating engagement effort appropriately — investing the most time with high-influence/high-interest stakeholders who most affect or are affected by the initiative.
Question 5: What is the key difference between a 'push' and 'pull' communication strategy?
- Push communication is formal; pull communication is informal
- Push communication sends information to stakeholders; pull communication allows stakeholders to access information on demand (Correct answer)
- Push communication is used with executives; pull communication with end users
- Push communication requires face-to-face delivery; pull communication is digital
Correct answer: Push communication sends information to stakeholders; pull communication allows stakeholders to access information on demand
Push communication actively distributes information to stakeholders (emails, reports, presentations), while pull communication makes information available for stakeholders to access when needed (portals, wikis, shared drives).
Push communication delivers information directly to recipients regardless of whether they requested it (emails, newsletters, meeting minutes). Pull communication stores information in accessible locations for stakeholders to retrieve when needed (project wikis, document repositories, dashboards). An effective communication plan typically uses both: push for time-sensitive decisions and updates, pull for reference information and detailed documentation.
Question 6: When should a business analyst escalate a stakeholder issue rather than resolve it independently?
- Whenever a stakeholder disagrees with any requirement
- When the issue involves authority, resources, or decisions beyond the business analyst's scope (Correct answer)
- Whenever the issue is technically complex
- Only when the project sponsor requests it
Correct answer: When the issue involves authority, resources, or decisions beyond the business analyst's scope
Escalation is appropriate when the issue involves authority, resource allocation, or strategic decisions that exceed the business analyst's mandate — these require decision-makers with the appropriate authority.
Business analysts should resolve issues within their authority and domain, but escalate when issues involve: decisions that require organizational authority the BA doesn't possess, resource or budget commitments, unresolvable conflicts between high-level stakeholders, regulatory or legal implications, or risks that could significantly impact project success. Knowing when to escalate is a key professional judgment skill.
CCBA Stakeholder Engagement and Communication 1
What is the PRIMARY purpose of stakeholder analysis in business analysis?