Determine how many systems are involved.In some cases, you might also like to participate in the actual work process to get a hands-on feel for how the business function works today. You may need to watch people perform their job before you can understand the entire picture. This is especially helpful when gathering information on current processes. You show this to the client, who then gives you additional requirements. Prototyping is a way to build an initial version of the solution – a prototype. It can also be the only practical way to gather requirements from dozens, hundreds or thousands of people. These are good tools to gather requirements from stakeholders in remote locations or those that will have only minor input into the overall requirements. However, the group typically stays in the session until a complete set of requirements is documented and agree to. Joint Application Development (JAD) sessions are similar to general facilitated sessions. In this case, you are trying to gather a set of common requirements from the group in a faster manner than if you were to interview each of them separately. In a facilitated session, you bring a larger group together for a common purpose. Group interviews require more preparation and more formality to get the information you want from all the participants. These are similar to the one-on-one interview except that there is more than one person being interviewed. The most common technique for gathering requirements is to sit down with the clients and ask them what they need. There are a bunch of methods to pick from to elicit requirements. Step 1: Identify the Method of Elicitation There are 5 steps to Eliciting requirements. Nothing to be scared about? The key is to start. In short it’s the process of gathering the client requirements. Elicitation and collaboration work is never a ‘phase’ in business analysis rather, it is ongoing as long as business analysis work is occurring. The Elicitation and Collaboration knowledge area describes how business analysts identify and reach agreement on the mutual understanding of all types of business analysis information. Collaboration is the act of two or more people working together towards a common goal. It is the main path to discovering requirements and design information, and might involve talking with stakeholders directly, researching topics, experimenting, or simply being handed information. Elicitation is the drawing forth or receiving of information from stakeholders or other sources. It also describes the communication with stakeholders once the business analysis information is assembled. The Elicitation and Collaborationknowledge area describes the tasks that business analysts perform to obtain information from stakeholders and confirm the results.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |