Business Analysis - Document Elicitation Result

The next step after preparation and conduction is documentation. BA need to document elicitation result for the next analysis. Please take look my summary about it from BABOK.

3.3 Document Elicitation Results

#Purpose
Record the information provided by stakeholders for use in analysis.

#Description
For an elicitation event (brainstorming, focus groups, interviews, observation, prototyping, requirements workshop) a summary of the output from the event, including issues is produced.

#Input
Elicitation Results : Includes the information provided by stakeholders that will be recorded and structured.

#Elements
Documentation can take a number of forms, including :

• Written documents describing the outcomes, such as meeting minutes
• Visual or audio recordings
• Whiteboards (either actual or virtual) where notes are retained until they are transferred to another medium.

The technique used for elicitation, as well as the business analysis approach, will determine what kind of documentation is possible and desirable.

#Techniques

• Brainstorming (9.3) : The activity generally produces the necessary documentation.
• Document Analysis (9.9) : A report of the findings should be produced.
• Focus Groups (9.11) : The results of a focus group are collated and summarized.
• Interface Analysis (9.13) : A report of the findings should be produced.
• Interviews (9.14) : Result of the interview are documented.
• Observation (9.18) : Results of observation are documented.
• Problem Tracking (9.20) : Elicitation may produce issues that need to be tracked to resolution.
• Prototyping (9.22) : The result of elicitation may undergo requirements analysis directly, without the need for an intermediate step to document them.
• Requirements Workshop (9.23) : The result of elicitation may undergo requirements analysis directly, without the need for an intermediate step to document them.
• Survey / Questionnaire (9.31) : The results of a survey are collated and summarized.

#Stakeholders
Business Analyst : Other stakeholders do not need to participate in this task.

#Output
Requirements [Stated] : Described from the perspective of the stakeholder. Stated requirements describe the stakeholder's need from the stakeholder's perspective.

Stakeholder Concerns : Includes issues identified by the stakeholder, risks, assumptions, constraints, and other relevant information.

...

Next : Confirm Elicitation Result