Business Analyst Interview questions are important for defining the scope, business requirements and functional specifications requirements. Below is a list of interview questions for the business analyst to use during requirements gathering interviews. Pitlitipifec These interview questions are included in the business analyst training and are helpful during the business analyst interviewing. The high level business requirements interview questions listed below are especially useful for legacy software development type projects.
The business analyst will need to determine the business objectives with the business sponsor and primary stakeholders. Below are some questions for defining the business objective:
- Why do you want to redo the system?
- How will the new version of the system help you?
- What are your objectives in having this system?
- Who are the key stakeholders and users? Do their goals differ? If so, how?
- How does the system map to business goals?
- What is the most important business goal of the system?
- Will the system change the way you are doing things now?
- Will the system help you be more efficient? How?
- What are the system deliverables?
- What will the converted system accomplish that the current system cannot accomplish?
- Will the output of the converted system be the same or different than the current system?
- Will the new system have additional functionality? What?
- Will the new system have better performance? To what extent?
- Will the new system help you be more efficient? To what extent?
- Will the screens look different? How?
- What is most important (rank in order of importance):
Application is easier to use
Application has nicer front-end
Application has additional functionality (list)
Application is more efficient
Application is redesigned to better reflect the business
The business analyst will need to determine the future needs, current problems, users, system interfaces and success criteria. Below are some questions that can be used by the business analyst when interviewing the stakeholders and technical project team.
- Is the data and/or functionality shared by other (many) business areas? If so, which?
- If the reports were dynamic, what would they do differently?
- How much historical information is required?
Determine Current Problems
- What are the current problems with your system today?
- Do you have to do things manually that you would like to automate?
- Do you have performance problems that need to change?
- Do you have functional limitations that you’d like to change?
- What is the risk of not converting the system?
- Which reports do you currently use? What data on the report is important? How do you use the information?
- Are there specific bottlenecks to getting at information?
- How do you analyze the information you currently receive? What type of data is used? How do you currently get the data? How often do you get new data?
- What type of ad hoc analysis do you typically perform? Who requests ad hoc information? What do you do with the information?
Determine System Users
- Who will be using the system?
- What are the titles and roles of the people who will use the system?
- What are their levels of expertise?
Determine Criteria for Success
- What do we need to accomplish to make this project successful?
- What do we need to change to make this project successful?
- What buy-in do we need?
- Are we lacking any critical elements such as budget, resource allocation, or support?
- What are the training considerations for developers and users?
- Who are the most important players in terms of – Knowledge – Politics?
- Is there any existing system documentation? If so, where?
- Who else should we talk to?
Assumptions and Issues
- List assumptions
- List open issues, responsible parties, resolution date