SkarpSkarp

Chapter 17 of 21

Business Analysis Foundations: Roles, Stakeholders, and Elicitation Techniques

Step into the business analyst’s world to see how they uncover real needs, manage diverse stakeholders, and choose the right elicitation techniques for each situation.

27 min readen

Step 1 – Where Business Analysis Fits in Projects and the CAPM

Why Business Analysis Matters

Business analysis ensures projects solve the right problem and define clear, testable requirements that connect to real business value.

Key CAPM Domains

This topic lives mainly in the Business Analysis Frameworks domain (27%) but also touches Predictive and Agile domains.

Foundational Definitions

A project is "A temporary endeavor undertaken to create a unique product, service, or result." Stakeholders are anyone who may affect or be affected by project decisions or outcomes.

What CAPM Tests Here

Expect questions on BA vs PM vs PO roles, stakeholder power/interest analysis, choosing elicitation techniques, and facilitating effective workshops.

Step 2 – BA vs Project Manager vs Product Owner (Predictive and Agile)

Project Manager Role

The PM owns the plan, schedule, budget, and risk responses, especially in predictive life cycles with scope, time, and cost fixed early.

Product Owner Role

The PO owns the product backlog, prioritizing items by value, risk, and feedback, and representing customer and business needs.

Business Analyst Role

The BA understands current and future states, defines requirements, models processes, and maintains requirements traceability.

Key Distinction for CAPM

BA informs decisions but does not own the schedule (PM) or prioritization (PO). Exam items often test this separation of responsibilities.

Step 3 – Stakeholder Analysis with the Power/Interest Grid

Why Stakeholder Analysis?

You cannot elicit good requirements if you do not know who your stakeholders are, what they care about, and how much influence they have.

Power and Interest

Power is influence over decisions and resources; interest is how much a stakeholder cares about project outcomes.

Four Quadrants

High power/high interest: manage closely. High power/low interest: keep satisfied. Low power/high interest: keep informed. Low power/low interest: monitor.

BA Use of the Grid

Use power/interest placement to decide who joins workshops, who gets summaries, and how detailed and frequent your communication should be.

Step 4 – Example: Tailoring Communication and Engagement

Scenario Overview

You are BA for a new university student portal. Stakeholders include a sponsor, IT, Registrar staff, students, and a Data Protection Officer.

High Power/High Interest

The Vice Provost gets executive summaries and joins key scope workshops but not every detailed session.

Low Power/High Interest Users

Registrar staff and students need regular, clear communication and are prime candidates for interviews, observation, and prototype reviews.

Regulatory Stakeholder

The Data Protection Officer gets targeted updates and elicitation sessions focused on security and access-control requirements.

Step 5 – Core Elicitation Techniques and When to Use Them

Why Technique Choice Matters

The exam tests whether you can pick elicitation techniques that fit stakeholder types, distribution, and the kind of information you need.

Interviews and Workshops

Use interviews for deep, individual insights; use workshops to build shared understanding and resolve conflicts across groups.

Observation

Observation reveals how work actually happens, including informal approvals and workarounds that people may not mention in interviews.

Surveys and Prototyping

Surveys scale to large groups but lack depth. Prototypes turn abstract ideas into something concrete that users can react to.

Step 6 – Matching Techniques to Stakeholder Situations

Distributed Call Center

For many agents across locations, use surveys for breadth, then interviews and observation for depth and real workflow insight.

Regulatory Reporting Change

Use workshops with compliance and finance, interviews with the DPO, and report prototypes to validate regulatory and security needs.

HR Self-service Portal

Combine workshops for prioritization, prototypes for usability feedback, and observation to spot waste in current HR processes.

Exam Hint

When stakeholders are dispersed and you need trends, surveys beat workshops; workshops are better for alignment and conflict resolution.

Step 7 – Facilitating Collaborative Sessions and Managing Dynamics

Structured Turn-taking

Use round-robin or explicit turns so each participant speaks without interruption, especially when some are quiet or junior.

Staying on Track

Use a parking lot to capture off-topic points while keeping the workshop focused on its primary objectives.

Handling Dominant Voices

Thank them, then redirect to others, use time-boxes, or hold separate sessions to reduce intimidation and balance input.

From Solutions to Needs

Probe solution statements with "What problem does this solve?" and convert them into clear, testable requirements and acceptance criteria.

Step 8 – Thought Exercise: Rewriting Vague Requirements

Practice converting vague stakeholder statements into testable requirements with clear acceptance criteria.

Remember: acceptance criteria are "A set of conditions that is required to be met before deliverables are accepted."

For each statement below, pause and mentally rewrite it. Then compare with the suggested answer.

  1. Vague: "The system should be fast."
  • Your task: define measurable performance.
  • Sample rewrite: "The system shall display the student enrollment page within 2 seconds for 95% of requests during peak hours (9–11 am, Monday–Friday)."
  1. Vague: "Make the report easy to use."
  • Your task: express usability in observable terms.
  • Sample rewrite: "New finance analysts shall be able to generate the monthly revenue report without training, using at most 5 clicks, and with no more than one correction step."
  1. Vague: "Only authorized users can see student data."
  • Your task: specify security and access-control requirements.
  • Sample rewrite: "Only users in the 'Registrar' or 'Advising' roles may view full student academic records. Only 'Registrar' role users may modify grades. All access must be logged with user ID, timestamp, and action."

Reflection questions:

  • How would you validate these requirements in testing?
  • Which stakeholders would you involve to confirm that the criteria are realistic (for example, IT for performance, business owners for usability)?

This kind of thinking directly supports exam skills on eliciting, specifying, and validating testable requirements, including nonfunctional requirements like performance and security.

Step 9 – Quick Check: Stakeholders and Techniques

Answer this CAPM-style question to check your understanding of stakeholder analysis and elicitation technique selection.

You are the BA on a project to replace an internal expense-claim system. Hundreds of sales staff across three regions use the current system, and you suspect many unofficial workarounds. You have limited time and must first identify the most common pain points and workarounds. Which combination of techniques is MOST appropriate to start with?

  1. A. Large in-person workshop with representatives from all three regions only
  2. B. Online survey to all sales staff, followed by targeted interviews and observation with a small sample
  3. C. One detailed interview with the sales director and finance manager only
  4. D. Prototyping a new interface immediately and asking a few users to test it
Show Answer

Answer: B) B. Online survey to all sales staff, followed by targeted interviews and observation with a small sample

Option B is best. A survey reaches a large, geographically distributed group to identify patterns in pain points. Follow-up interviews and observation with a sample let you explore specific workarounds and current-state behavior in depth. A single workshop (A) or a couple of interviews (C) risk missing front-line realities. Jumping straight to prototyping (D) without understanding current issues is premature.

Step 10 – Quick Check: Roles and Workshops

Test your understanding of BA vs PM vs PO roles and workshop facilitation.

During a requirements workshop for a new HR system, a senior manager dominates the discussion, proposing detailed screen layouts. Other participants are silent. As the BA, what is the BEST action?

  1. A. Accept the manager's ideas since their seniority indicates high power and authority
  2. B. Ask the project manager to remove the manager from the workshop
  3. C. Thank the manager, then use structured turn-taking and probing questions to involve others and focus on underlying needs and outcomes
  4. D. End the workshop early and switch to email-based requirements collection
Show Answer

Answer: C) C. Thank the manager, then use structured turn-taking and probing questions to involve others and focus on underlying needs and outcomes

Option C applies facilitation techniques: acknowledge contributions, then use structured turn-taking and probing questions to involve quieter participants and shift from solution design to needs and outcomes. A and B either over-defer or overreact to power. D abandons collaborative elicitation instead of managing it.

Step 11 – Flashcards: Key BA Foundations

Use these flashcards to reinforce key terms and distinctions that frequently appear in CAPM questions.

project
A temporary endeavor undertaken to create a unique product, service, or result.
stakeholder
An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
predictive life cycle
A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
adaptive life cycle
A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
product backlog
An ordered list of everything that is known to be needed in the product, managed by the product owner.
requirements traceability matrix
A grid that links product requirements from their origin to the deliverables that satisfy them.
acceptance criteria
A set of conditions that is required to be met before deliverables are accepted.
Power/Interest grid: High power / High interest
Manage closely: frequent, tailored communication and active involvement in key elicitation and decision-making.
When to prefer surveys
When stakeholders are numerous or geographically dispersed and you need broad, comparable input or trends rather than deep individual stories.
Key goal of BA workshop facilitation
Encourage balanced input, manage dominant participants, and shift discussion from proposed solutions to underlying needs and desired outcomes.

Step 12 – Pulling It Together and Next Practice Steps

Role Integration

BA, PM, and PO roles complement each other: PM manages constraints, PO manages backlog, BA ensures the solution meets real needs.

Stakeholders and Techniques

Use the power/interest grid to plan engagement and select elicitation techniques that fit stakeholder reach and information depth.

Facilitation and Requirements Quality

Run workshops that balance voices and turn vague wishes into testable requirements and acceptance criteria, including nonfunctional needs.

Your Next Steps

Use the upcoming Skarp diagnostic and mock exam to practice these skills; your spaced review queue will reinforce any weak spots.

Key Terms

project
A temporary endeavor undertaken to create a unique product, service, or result.
elicitation
The set of techniques used to draw out, discover, and clarify requirements and needs from stakeholders and other sources.
observation
An elicitation technique where the analyst watches stakeholders perform their work to understand current processes, workarounds, and pain points.
prototyping
An elicitation technique that uses mockups or working models of a solution to clarify requirements and gather feedback.
stakeholder
An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
product backlog
An ordered list of everything that is known to be needed in the product, managed by the product owner.
acceptance criteria
A set of conditions that is required to be met before deliverables are accepted.
adaptive life cycle
A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
power/interest grid
A stakeholder analysis tool that categorizes stakeholders based on their level of power (influence) and interest in the project outcomes.
predictive life cycle
A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
requirements traceability matrix
A grid that links product requirements from their origin to the deliverables that satisfy them.

Finished reading?

Test your understanding with a custom practice exam on this chapter.

Test yourself