ABSTRACT
This chapter shows that what International Institute of Business Analysis refers to as requirements elicitation. It discusses some of the drivers behind the process of selecting the appropriate elicitation techniques for a project. The goal of the business analyst is to be a communications link between the customer and the developer. The business analyst must find the right elicitation technique. The biggest reason for selecting an elicitation technique is the customer. The basic, traditional interviewing approach is to identify key stakeholders, interview each of them, and then analyzes the results from all the interviews. Purpose of the affinity diagram is to group ideas together into categories. The forced pair ranking is probably the simplest and most common technique for prioritizing requirements. The selection of the best requirements elicitation techniques is difficult but critical to the success of the analysis phase. The approach that is selected must be validated with the sponsor and other key stakeholders.
