Home / BA / question to ask during requirement elicitation

question to ask during requirement elicitation

Requirement elicitation is a process of digging out the information from stakeholders the goal of requirement elicitation is to ensure that the software development process is based on clear understanding of customer needs

It is basically collecting requirement from stakeholders’ users and customers by conducting meetings, interviews, questionnaire, brainstorming session and prototyping

Elicitation deals with all the activities required in gathering the requirement  

It is performed at the beginning of the project and is most critical part of SDLC developers and engineers work close coordination with customers and end users to identify more about the problem to be solved and bridge the gap between expectations and understanding.

It can be successfully done only by communicating with clients by face to face, through emails. Requirement gathering is practice to get know from clients what they really want in their project

By asking question is one of the methods to gather the requirement in more effective way it can also be done by 5W 1H rule:

Why, where, when, what, who and how

  • Where does the process start?
  • Why do we need to use this feature?
  • What is the ultimate goal you are trying to use this feature?
  • What is the outcome do you expect?
  • What is the business need or opportunity for this feature?
  • What you would like to hold in hands after using the system?
  • What is the business value?
  • How much benefit will you get after using this feature?
  • What is the purpose of the project?
  • What are the changes we need to do during the existing process?
  • What are the expectations for this process and how can we achieve it?
  • What is the data flow of new process? (AS-IS Vs To – Be)
  • What applications and technology will the project need?
  • How many teams will be involved in this project?
  • What is the major risk to succeed with this project?
  • What problems do you see this project is solving?
  • What happens if the project is not successful or not done?
  • What are the most important problems would avoid to make?
  • Which is the concern most about the project?
  • What are the major obstacles or impediments to the success of this project?
  • What is the suggestion to make up for you team?
  • When we will know that the feature is failed?
  • When can we start the project?
  • Who will be responsible for the feature?
  • Who will give inputs for the project features?

Understanding the expectation of the project stakeholder is absolute way to have knowledge about the project such as how the business should be truly working, how well everyone is interacting. The questions to ask says a lot about what they think they understand and what they don’t actually know. With asking more questions, we can eliminate the assumptions made. And also, we gain clarity on the requirements. We can also avoid misunderstandings about the requirements.

About Serena ward

Check Also

Q1. What is BRD? How it is different from SRS?

BRD BRD stands for Business Requirement Document. It is a formal document that specifies all …

Leave a Reply

Watch Dragon ball super