4 Techniques to confirm elicitation results
May 19, 2020

4 Techniques to confirm elicitation results

By Lau

“Don’t ask the mind to confirm what is beyond the mind. Direct experience is the only valid confirmation. “

– Sri Nisargadatta Maharaj–
Don't ask the mind to confirm what is beyond the mind. Direct experience is the only valid confirmation.- Sri Nisargadatta Maharaj Click To Tweet

In this article, you are going to learn four techniques that will give you more tools when it comes to getting the confirmation for the elicitation results. This post will help you if you are a business analyst beginner and you want to make sure the business requirements you have gathered meet the stakeholder’s expectations. And is also going to be useful to identify any possible error and solve it before resources are committed.

First, let’s talk about what the propose to confirm elicitation’s results is. The purpose of Confirm Elicitation Results is to check the information gathered during an elicitation session for accuracy and consistency with other information. The goal of it is finding any error before moving on to the next software development life cycle’s phase.

The elicitation results can be compared against other sources such as document and stakeholder knowledge and other elicitation results to ensure consistency, for example comparing collected results through multiple elicitation activities to confirm that the information is consistent and accurately represented. This review may discover errors, omissions, conflicts, and ambiguity.

Fortunately, there are four techniques that you can use to make sure the gathered requirements and the stakeholder’s needs match.

4 techniques to confirm elicitation results.

1. Document Analysis.

Documenting the analysis can help to be used as a parameter of comparison between what you have understood in the elicitation and with any other existing documents and source can say.

2. Interviews.

Sometimes a document phase to compare the existing information with the business need, for these cases, it is going to be necessary to meet the stakeholder in person. A good practice in these cases is to write down what is being clarified in the meeting.

3. Reviews.

Reviews are very useful to compare them with the business needs and with the gathered information collected in the elicitation.

4. Workshops.

This technique is often used to conduct reviews of the drafted elicitation results using any level of formality. A predetermined agenda, scripts, or scenario tests may be used to walk through the elicitation results, and feedback is requested from the participants and recorded.

To recap, you have learnt what to confirm elicitation results is, why is that important and what are the four techniques to confirm elicitation results by mitigating the risk of possible misunderstandings from the elicitation stage.

You might also like to read about How to communicate business analysis information effectively

And don’t forget to download this FREE Digital Book: The Master Strategy for BA Beginners where you will learn how to get your first BA job by following 3 strategic steps.

See you soon. 😉