Confirming elicitation results

Once requirements have been elicited they have to be confirmed.

Though stakeholders might seem sure of they want, confirming the requirements with these stakeholders might yield additional insight, expose assumptions and possibly create additional requirements.

The confirm elicitation results activity is used to check the accuracy of the information which has been gathered in the elicitation activities.

The information is checked against the source of that information to ensure that it is accurate. This would prevent ambiguity, omissions, conflicts and may prevent errors.

The business analyst would need to collaborate with the stakeholders to confirm the elicitation results and ensure that they agree with the results.

If the results are incorrect the business analyst might need to elicit more requirements to clarify the incorrect information.

There are some elements that help with the confirm elicitation results activity and they are:

1. Compare elicitation results against source information: The elicitation results has to checked against the source of the information. This information source might be the stakeholders or documents.

2. Compare elicitation results against other elicitation results: The business analyst needs to compare the elicitation results to other elicitation results to ensure consistency.

The business analyst might go through numerous cycles of results confirmation and comparing the results of a latter cycle against those of an earlier one would help identify inconsistencies and errors.