Conduct Elicitation Activity - Business Analyst


Meet with stakeholder(s) to elicit information regarding their needs.


Elicitation Activity Plan Template

The elicitation event takes place (brainstorming, focus groups, interviews, observation, prototyping, requirements workshops), or elicitation is performed (document analysis, interface analysis) or distributed (survey / questionnaire).


Business Need: Required to ensure that the business analyst understands what information should be elicited from the stakeholders. This input is used when eliciting business requirements (with the exception of the business need itself).

Organizational Process Assets: May include templates or processes for these activities.

Requirements Management Plan: Determines what information needs to be recorded and tracked as an outcome of the activity. In particular, many requirements attributes must be elicited and captured while performing this task.

Scheduled Resources: The relevant stakeholders, location, and other resources must be available.

Solution Scope and Business Case are required to ensure that the business analyst understands what information should be elicited from the stakeholders. These inputs are used when eliciting stakeholder, solution, and transition requirements.

Supporting Materials: Whiteboards, flipcharts, documents, and other materials must be available while the activity is conducted.


Tracing requirements: While eliciting the requirements it is important to guard against scope creep. Tracing requirements back to the business goals / objectives helps to validate whether a requirement should be included.

Capturing requirement attributes: While eliciting the requirements documenting requirements attributes such as the requirement’s source, value and priority will aid in managing each requirement throughout its life cycle.

Metrics: Tracking the elicitation participants and the actual time spent eliciting the requirements provides a basis for future planning.

For event-based elicitation techniques, eliciting requirements is highly dependent on the knowledge of the stakeholders, their willingness to participate in defining requirements, and the group’s ability to reach consensus. It is important that all defined stakeholders are heard during elicitation of requirements. It may be necessary to further clarify and possibly restate the requirements to encompass all stakeholders’ perspectives.


Data Dictionary and Glossary: A business glossary is an essential asset for all elicitation techniques. The glossary should contain key domain terms along with their business definitions.

General Techniques: Refer to each technique below for unique elements of conducting that particular technique.

  • Brainstorming
  • Document Analysis
  • Focus Groups
  • Interface Analysis
  • Interviews
  • Observation
  • Prototyping
  • Requirements Workshops
  • Survey / Questionnaire


Customer, Domain SME, End User, Supplier and Sponsor: May participate in this task as a source of requirements.

Implementation SME, Operational Support, Project Manager, Supplier and Tester: May participate to improve their understanding of the stakeholder needs and to aid stakeholders in understanding the tradeoffs faced by the project team.

Regulator: May participate directly (as a source of requirements) and may also dictate that a specific process be followed or that certain records be kept.


Elicitation Results: May include documentation appropriate to the technique and capture the information provided by the stakeholder.

All rights reserved © 2020 Wisdom IT Services India Pvt. Ltd Protection Status

Business Analyst Topics