In the real world, business analysts often have to go the extra mile to elicit requirements, regardless of the circumstances. Despite the difficulty of identifying these elusive requirements, business analysts are expected to rise up to the challenge - every single time.
This post outlines some of the steps that can be taken to ensure that accurate requirements are elicited:
1. Use a scribe this involves facilitation and interviewing.
2. To avoid curiosity business analyst should also ask questions openly to verify the answer.
3. The business analyst should also confirm the out put of elicitation session and this should be done right after meeting the stakeholder to confirm the conversation is still fresh in everyone's mind
4. Business analyst should also use the Prototype . Prototypes and wire frames are most effective tool to stimulate the discussion specially in conflict requirements
5. Trace requirement is another tool for eliciting the requirement from the business this make sure every requested feature or requirement links back to a specific business objective .
Hopefully this will help you!!
Feel free to pass your comments