What is Requirement Elicitation?
Why is it important in the software development process?
A project can fail for the following reasons:
- Poorly defined requirements
From the project management prospective most of the project fail when they do not meet the following criteria:
- a. Deadline
- b. Cost
- Lack of communication
- A bad leadership
- A bad team
Widely used/ accepted techniques for requirement elicitation
1. Task analysis
- a. What are the stakeholder’s (Client and users) goals
- b. What they want to achieve
- c. How the task will be initiated and completed
2. Right Questions can help you understand the process
Asking the right question can help fill the gap between developer’s understanding of the business process and real requirements of the clients. In general, questionnaires are techniques of asking the right questions.
Let’s understand it with a case: Suppose a school owner approaches a software development agency with the requirement of a Learning Management System or a software for schools but he does not know about how it will be done, what techniques will be used and how it will fulfil and map his requirements. To ask the right questions you should have an understanding of the required business model like in case of school you should know the process of student’s admission, how they teach, how they mark attendance, how they evaluate the performance of students, how teachers get appointed and way of evaluating teaching skills etc..
Here under are few popular methods of questionnaires:
- a. Telephonic
- b. Survey
- c. Email questionnaires
- d. Interviewing the stakeholders
When interviewing the stakeholders, Email questionnaires are the most suitable tool for software agencies and developers.
- a. Time limit
- b. Evaluation criteria
- c. Avoid criticism and office politics