The conduct elicitation activity is a technique to understand stakeholder needs and identify potential solutions that may meet those needs. It involves guiding stakeholders and collaborating with them through the elicitation activity, doing research or running experiments, and capturing elicitation outcomes1. The inputs for this activity are the following2:
Requirements management plan: This document defines how requirements will be elicited, analyzed, documented, validated, and managed throughout the project lifecycle. It provides guidance on the elicitation approach, techniques, roles, responsibilities, and deliverables.
Business need: This is the problem or opportunity that the project intends to address. It provides the context and rationale for the elicitation activity and helps to define the scope and objectives of the project.
Solution scope: This is the set of capabilities and features that a solution must deliver in order to meet the business need. It defines the boundaries and assumptions of the project and helps to identify the stakeholders and sources of information for the elicitation activity.
Stakeholder list, roles, and responsibilities: This is the identification and description of the individuals and groups who have an interest or influence in the project. It defines their roles, responsibilities, expectations, and level of involvement in the elicitation activity.
Business analysis information: This is the collection of information that has been gathered, analyzed, and documented during the business analysis process. It includes the business analysis plan, the business case, the current and future state descriptions, the requirements, the assumptions, the constraints, the risks, the issues, and the change requests. It provides the input and reference for the elicitation activity and helps to avoid duplication or inconsistency of information.
Elicitation activity plan: This is the plan that describes the specific details of the elicitation activity, such as the purpose, scope, objectives, approach, techniques, participants, agenda, logistics, materials, and expected outcomes. It helps to prepare and organize the elicitation activity and ensure its alignment with the requirements management plan and the business analysis plan.
Documented elicitation results are not an input, but an output of the conduct elicitation activity. They are the records of the information that has been elicited from the stakeholders and other sources during the elicitation activity. They include notes, transcripts, recordings, models, diagrams, sketches, prototypes, surveys, questionnaires, and other artifacts that capture the stakeholder needs, expectations, preferences, assumptions, constraints, and feedback. They are used as an input for the confirm elicitation results activity, where they are checked for accuracy, completeness, and consistency. References: Conduct Elicitation - iiba.org, Exploring the CBAP Knowledge Areas - Institute i4
