Techniques to elicit requirements – obtaining information from stakeholders takes effort but there are proven guide to have advantages and disadvantages, so select the ones that are most likely to work given your situation. Don’t forget that you can use more than one of these techniques together.
- Requirements workshops
1) Interviews could be conducted formally or informally.Best to go for a small group or 1 vs 1 interview, at least one person should be designated to take notes. Interviews are not always the best way to reach satisfaction because not all of the stakeholders may be heard , but they could be effective to obtain information.
2) A group of relevant stakeholders is invited to attend a session in which they will provide their feedback. Discussions will be a higher level of clarity on how the software should work, and what it is required to do.A clear agenda should be set for each requirements workshop. The scope varies, but you might want to keep each session restricted to a certain part of the business process or software application. Someone should be designated as the facilitator who can run the meeting, and a different person should take notes.
3) Brainstorming session should have clear goals, and each session should not be too broad. You may conduct a brainstorming session to get requirements for a specific piece of functionality or related a specific part of the application. Take 5 or 10 people max.
4) Prototyping is a requirements elicitation technique that stakeholders can use because some people are more visually-oriented than others, and having a prototype can trigger ideas regarding requirements
- Previous Post