1. Who is Business Analyst?
Answer: A business analyst works as a bridge between different stakeholders in an organization. He connects with the different stakeholders of an organization to clarify and finalize the requirements, helps the project team in project planning, designing and finally validating the developed components. He is the person who possesses adequate domain knowledge and can sort the business needs amongst the stakeholders who belong to different domains.
2. Name some of the documents that a business analyst use to handle?
Answer: Following are some of the common documents that a business analyst use to handle:
Project vision document
Use cases
Requirement Management Plan
User stories
Requirement Traceability Matrix (RTM)
Business Requirement Document
System Requirement Specification (SRS)/ System Requirement Document (SRD)
Test case
Functional Requirement Specification (FRS)/ Functional Specification Document (FSD)
3. What, according to you, are the core competencies of a Business Analyst?
It is one of the most common business analyst interview questions. Although every company is different, the core requirements of a business analyst profile are quite similar. Make sure to go over an organization's job description in detail to understand the required core competencies and include them in your answer.
You can answer this by stating that a business analyst must have exceptional communication and negotiation skills. Analytical thinking, problem-solving, and decision making are also vital attributes. A business analyst should have industry knowledge, business process management skills along with technical proficiency.
4. What is a requirement?
Answer: A requirement is a targeted solution to achieve specific business goals or objectives. It is an input to various stages of SDLC. This is a basis of a project which must be validated by the stakeholders and business users before implementation. Besides that, every requirement needs to be properly documented for future reference purpose.
5. What is Use case?
Answer: A use case is a diagrammatic representation of a system which describes how a user uses a system to accomplish a goal. It is an integral part of software engineering and software modelling technique which defines the targeted features and the resolution of any possible errors which a user may encounter.
Must Read: List of 10 Best Business Analysis Tools
6. What are the steps that you need to follow to design a use case?
Answer: The steps in designing use cases are:
Identify the users of the system
Creating a user profile for each category of users. This includes all roles that the users may play and relevant to the system.
Identify essential goals associated with each role. Also, identifying the significant roles.
Creating use cases for every goal associated for a use case template. This also includes maintaining the same abstraction level for the entire use case. Higher level use case steps are considered as goals for the lower level.
Structuring the use cases
Reviewing and validating the users
7. What is Scope creep and how can you avoid scope creep?
Answer: Scope creep, or requirement creep is a term that relates to the uncontrolled changes or deviation in the project’s scope within the same resource range for example within same schedule and budget of the project. It’s an indication of poor project management and a viable risk to a project. Some of the possible causes of scope creep are:
Poor communication between the project’s stakeholders
Improper documentation of the project’s requirements
Scope creep could be avoided by:
Clear documentation about the project scope
Following proper change management
Prior intimation about the effects of the changes to the associated parties
Proper documentation of the new requirements in the project log
Refrain from Gold Plating which means adding extra features to the existing functionalities
8. What is BRD? How is it different from SRS?
Answer: A Business Requirements Document (BRD) is a formal contract between the customer and the organization for a product.
The difference between BRD and SRS are as follows:
BRD SRS
It is a high-level functional specification of the software. It is a high level functional and technical specification of the software
It is a formal document to describe the requirement provided by the client (written, verbal) It describes the functional and non-functional requirements of the software to be developed
The Business Analyst creates it after their direct interaction with the clients The System Architect creates it as it needs technical expertise. Though sometimes Bas too can create it.
It is derived based on the requirements and client interaction It is derived from the BRS
9. What is Gap Analysis?
Answer: Gap Analysis is a technique to analyze the gap between the existing system and functionalities, and the targeted system. Here gap means the amount of task or change that may be required to get the intended result. It’s a performance level comparison between the present and the proposed functionalities.
10. What is requirement prioritization? What are the different techniques used for it?
Answer: Requirements prioritization is the process to allocate requirements based on the business urgency to different phases, schedule, cost, etc.
There are various techniques which are used for requirements prioritization:
MoSCoW Technique
Requirements Ranking Method
100-dollar method
Kano Analysis & More
Five Whys
Also Read: 10 Most Popular Business Analysis Techniques
Best entry level business analyst interview questions
11. What is the requirement elicitation technique?
Answer: Requirement elicitation is the process of requirement gathering from stakeholders, users, and customers by conducting meetings, questionnaires, interviews, brainstorming prototyping, sessions, etc.
12. What is the fundamental difference between a requirement and need in a business analysis perspective?
Answer: Needs are high-level definitions of the future goals of a business. Whereas, Requirements are the representation of the detailed description of that business needs.
13. What are non-functional requirements and how do you capture them?
Answer: Non-functional requirements represent the performance level characteristics like how fast it can respond, how smooth is a user interface, security, etc. of the application under development (AUD).
No functional requirements are captured in the SRS document in its designated section.
14. What are the skills that a business analyst must possess?
Answer: We can broadly categorize the skills of a business analyst in three types:
Fundamental skills
Technical skills
Business Analysis skills
For each of the above categories a business analyst should possess some skills as mentioned below:
Skill category Skills
Fundamental skills
Problem Solving
Communication
Management skills
Research
Technical skills
IT skills like MS Office, Operating systems, Programming languages, Knowledge of database, SDLC knowledge, Domain knowledge
Business Analysis skills
Requirement Elicitation
Documentation
Decision making
Creativity
Analytical skills
15. How can you say that a requirement is good or perfect?
A requirement is said to be perfect if it is Specific, Measurable Attainable Relevant, and Timely or in short SMART. The description of a condition should be specific, and all the parameters required for success should be measurable. All the needed resources should be attainable and relevant to the project. All the conditions/elements should be revealed timely.
16. What is the purpose of the Requirement Traceability Matrix?
It records all the requirements given by a client and ensures that all the necessities are met.
17. What is business modelling?
Business modelling is a step- by -step approach for identifying the value proposition for operating the business.
The key attributes of business modelling to develop a strategic plan for an organization are:
Vision
Mission
Objectives
Strategies
Action plan
18. Define Personas?
Answer: Personas represents User-Centered Design methodologies. To enable an application capable of performing on a demographic basis, fictional characters are conceptualized by the business analysts and based on their possible demographic specific behavior scenarios are created during design.
19. What is an activity diagram and what are the important elements of it?
Answer: An activity diagram is a visual representation of the workflow of a business use case. This diagram shows various activities that take place in an organization in different departments like HR, Sales, Accounts, etc. The activity diagram highlights the differences in the departments.
The important elements in Activity diagram are initial nodes, activities, control flows, decisions, a fork, guard conditions, join and end nodes.
20. What is UML modelling?
Answer: UML stands for Unified Modelling Language. It is a standard that the industry uses for documenting, constructing and visualizing various components of a system. This modelling standard is primarily used for software development. However, it is also used for describing job roles, organizational functions, and business processes. Some of the important diagrams that BAs use as part of UML are the class diagram, state diagrams and use cases.
business analyst interview questions
Must Read: Why is the Certification Required to Grow in the Field of Business Analysis?
Most popular Junior business analyst interview questions
21. What are the best practices to follow while writing a use case?
Answer: Some of the best practices to write a use case are as follows:
To become a valid use case, the use case must provide some value back to the actor or stakeholder.
The functional and non-functional requirements must be captured appropriately in the use case.
The use case must have one or more alternate flow along with the main flow.
The use case should only describe what the system does and not how it is done which means it will not describe the design. It will act as a black box from the viewpoint of an actor.
The use case should not have any, i.e. it should be stand alone.
22. What is the difference between exception flow and alternate flow?
Answer: Alternate flow are the alternative actions that can be performed apart for the main flow and can be considered as an optional flow.
Exception flow is the path traversed in case of any exception or error.
23. Do you think a business analyst should be involved in testing?
Answer: Yes. Because a business analyst understands the overall system requirements and challenges associated with it very well. Hence, he can be instrumental during the testing phase to run it appropriately and resolve any system related query.
24. What does INVEST stand for?
Answer: INVEST stands for –
Independent
Negotiable
Valuable
Estimable
Sized Appropriately
Testable
It can assist project managers and technical team to deliver quality products/services.
25. What is Pareto Analysis?
Answer: Pareto Analysis which is also known as 80/20 rule is a decision-making technique. It is a useful technique for defect resolution and quality control. As per this analysis rule, 20 % causes create 80 % effects in a system, which is why it is named as 80/20 rule.
Do you find yourself fully prepared for PMI-PBA certification exam? Try now how many of these PMI-PBA free questions can you solve?
26. What is BPMN and what are its basic elements?
Answer: BPMN is the Business Process Model and Notation. It is a graphical representation of business processes.
There are five basic elements of BPMN, and they are –
Flow Objects
Data
Connecting Objects
Swimlanes
Artifacts
27. What is Kano analysis?
Answer: Kano Analysis is used to analyze a system regarding its requirements to identify its impact on customers’ satisfaction.
28. What are the different types of actors you know in use case diagram?
Answer: There are mainly two types of actors can be depicted in a Use case-
Primary actors – It starts the process
Secondary actors – It assists the primary actor
Moreover, we can categorized actors into four types :
Human
System
Hardware
Timer
29. What are the different types of the gap that a business analyst can encounter during gap analysis?
Answer: There are mainly four types of gap –
Performance Gap – The difference between expected performance and the actual performance
Product/Market Gap – The gap between budgeted sales and actual sales is termed as product/market gap
Profit Gap – The variance between a targeted and actual profit of the company.
Manpower Gap – The gap between the required number and quality of workforce and actual strength in the organization
30. What is Benchmarking?
Answer: Benchmarking is about measuring the performance of an organization to compete in the industry. In this process, a company may measure its policies, performance, rules and other measures.
Preparing for CBAP certification exam? Check your current level of preparation with CBAP Practice Tests. Start with CBAP free test now!
Most popular Senior business analyst interview questions
31. How do you decide that as a business analyst you have gathered all the requirements?
Answer: We can conclude that all the requirements are gathered only when –
It is validated and approved by the business users.
The requirements are appropriately aligned with the project’s business requirements.
The requirements can be implemented with the available resources.
All the key business stakeholders are aligned with the elicited requirements.
32. How do you perform requirement gathering?
Answer: The requirement gathering process is generally divided into multiple steps which are agnostic to the SDLC cycle. Each step involves:
specific tasks to perform
principles to follow
documents to produce
The steps are as follows:
Step 1: Gather Background Information – This may include collecting background information about the project, analyzing any potential risk associated with the project. Techniques like PESTLE analysis, Porter’s Five forces framework could be used for this purpose.
Step 2: Identify Stakeholders – They are the decision makers of a project and approver for requirements and priorities. Stakeholders may range from project owners to senior managers, end users, and even competitors.
Step 3: Discover Business Objectives – This is to understand the business needs of the project before going deep into the project. SWOT analysis, Benchmarking, analyzing business objectives SMART and listing business objectives are some of the techniques used for this purpose.
Step 4: Evaluate Options – This is to identify the options to achieve business objectives. Impact analysis, Risk analysis, Cost-benefit analysis are some of the methods which are used for this purpose.
Step 5: Scope Definition – A scope is a project development goal which is set based on the business objectives. A scope definition document is used to detail the goals for each phase of a project.
Step 6: Business Analyst Delivery Plan – Based on the project scope, stakeholders availability and project methodology a document called business analyst is created at this step. The document provides information on deliverables with their timeline.
Step 7: Define Project Requirements – In this step, two types of documents are used – Functional requirement document and Non-functional requirement document. Based on the development methodology to be used in the project the business analyst needs to clarify the requirements with the stakeholders by interviewing them on the requirements and get the sign off on the same.
Step 8: Support Implementation through SDLC – This is the technical implementation step of the requirements where a business analyst gets involved with different teams. This includes coordinating with the development team and testing team to ensure requirements are implemented as expected and appropriately tested against all the possible business scenarios. They also need to handle the change request which may arise from the stakeholders at the later point of time.
Step 9: Evaluate Value Added By Project – This is the continuous evaluation of the project to evaluate whether the business objectives implementation correctly meets the business needs outcome and timeline.
33. Why it is necessary for a business analyst to get involved during the implementation of requirements?
Answer: Gaining domain knowledge and providing an analytical solution are the two major criteria of a business analyst. Hence, during actual implementation of a requirement or use case a business analyst can help to resolve many business strategies related problems that may arise during the implementation stage. On the contrary, they can learn from the problems which may help them to provide the solution in similar scenarios and also help to gain their domain knowledge.
34. What are the problems that a business analyst may face?
Answer: From the initiation to post implementation of a project a business analyst may face the following problems –
Employees related issues
Technology related problems
Access related
Business policies related issues
Business model errors
35. Explain requirement elicitation strategy?
Answer: Requirement elicitation is the process to collect all the requirements related to a system from the end users, customers, and stakeholders. As per the BABOK guide, there are nine methods which can be used as part of requirement elicitation process, and these are:
Brainstorming
Interviews
Observation
Document Analysis
Focus Groups
Requirements Workshops
Interface Analysis
Survey or Questionnaire
Prototyping
Preparing for CCBA certification exam? Check your current level of preparation with CCBA Practice Tests. Start with CCBA free test now!
36. What is Business Model Analysis?
Answer: Business Model Analysis is a technique to analyze whether a business is viable and valuable regarding social, economic and other perspectives. The business model analysis provides the foundation for any required business model change and innovation for an organization.
37. Do you think the role of a Business Analyst is a need for a project?
Answer: Yes, because the role of a Business analyst is extremely beneficial from the kick-off to the implementation of a project. Here are the top 5 reasons:
During the project kick-off session, there are high possibilities that some technical queries come up from stakeholder and clients. As we don’t involve the technical project team during this phase and immediate answering is essential, a business analyst may play a pivotal role to answer those queries.
The next phase after the kick-off session essentially involves some gap analysis, business process analysis, documentation, SOW review, project scheduling and of course preparing requirement specification documents.
During the development and testing phase, a business analyst can play a significant role to resolve any requirement related queries from the project teams. Besides that, he can validate whether the requirements are correctly implemented and tested considering different functional and non-functional scenarios.
In a waterfall model, new requirement or modification of requirements can be asked from stakeholder considering changing business needs. In this case business analyst is the person who can handle this change request with proper validation and analysis.
38. What is the difference between Business analysis and Business Analytics?
Answer: The key difference between Business analysis and Business analytics is the first one is more functions and process related whereas the second one is data related.
Business analysis – recognizes business needs and determine the solutions to that problems. Tools and techniques like SWOT, PESTEL, CATWOE, MOST, FIVE WHY, etc. are used for business analysis.
Business analytics – handles data and analyze data to get insights into a business. Finally, it generates reports. Mainly four types of business analytics are used, and they are – descriptive analytics, decisive analytics, prescriptive analytics, and predictive analytics Tools and technologies like Big data, BI is used for this purpose.
39. What is process design?
Answer: Process design is a way that helps a business to analyze the challenges in business and to find an effective solution for those. Through Process design workflows are created to get the best possible outcome in the shortest time.
40. What are the effective skills to solve any problem as a business analyst?
Answer:
Leadership skill
Excellent communication skill
Problem analysis skill
Technical knowledge
Domain knowledge
Planning to start your business analysis career with ECBA certification? Here we bring the complete preparation guide for ECBA certification exam!
Latest Agile business analyst interview questions
41. What is the Agile Manifesto?
Answer: Agile Manifesto is a software guide about the Agile development principles which ensure iterative solutions.
42. What are the essential qualities of an Agile BA?
Answer: An Agile BA must be able to:
The BA is expected work collaborate with product owner and developers to elicit requirements. The BA also must work to develop realistic functional requirements.
The BA must do requirement elicitation in an iterative way
The BA must make requirement specifications, data models and business rules as much lightweight as possible.
The BA must be technically sound so that he can understand how the components of the system interact with each other. Besides that, he must understand the agile terminologies as he acts as the middleman between the customer and the project team.
The BA must concentrate on the just-enough requirement and test criteria to meet the just in time delivery goal of an agile project.
43. When should you use Waterfall model instead of Scrum?
Answer: If the requirement is simple and specific, we should go for Waterfall model instead of Scrum.
44. What are the four key phases of business development?
Answer: The four key phases of business development:
Forming
Storming
Norming
Performing
45. What do you know about Kanban?
Answer: Kanban is a tool which helps the agile team to visually guide and manage the work as it progresses through the process. Besides, it works as a scheduling system in Agile just-in-time production. The Kanban board is used to describe the current development status.
Looking for PMI Professional in Business Analysis (PMI-PBA)® Preparation Options. Here’s the best strategy to prepare for PMI-PBA?
46. Mention about some of the most important agile metrics
Answer: The following are some important agile Matrices
Velocity – This is used to track the progress of a project
The sprint burndown matric – This helps to track the work done with the sprint.
The priority of the work
Work category allocation – This metric helps to get an idea about the priority of the work and work category allocation.
The cumulative flow diagram – the uniform flow of work can be checked thought this diagram of cumulative flow. Here the x-axis represents time and the y-axis stands for the number of effort.
Defect removal awareness – This helps to produce quality products.
Business value delivered – This is used to estimate the work efficiency of the team. It associates 100 points for measurement.
Time coverage – It estimates the amount of time invested in coding during testing. It is the ratio of the number of lines of code called by the test suite to the number of relative lines of codes.
Defect resolution time – This is the turnaround time for detecting and fixing bugs. There processes involved in for this purpose are:
bug fixing
eliminating the bug
Scheduling a fix
Defect fixation
Handover of the resolution report
47. Explain the term ‘increment’?
Answer: Increment refers to the sum of all the product backlog items completed in a sprint. The new increment value also includes the increment of the previous sprints.
48. What are the different types of Agile methodologies?
Answer: Some of the well-known agile methodologies are:
49. What is the Agile Manifesto?
The Agile Manifesto is a set of principles for software development that emphasizes individuals and interactions over processes and tools, customer collaboration over contract negotiation, and responding to change over following a plan.
50. What are the essential qualities of an Agile BA?
An Agile Business Analyst is someone who understands the agile methodology and is able to help a team work within that framework. They need to be able to communicate effectively, be organized, and have a strong attention to detail. They should also be able to work well under pressure and be able to adapt to changes quickly.
51. When should you use the Waterfall model instead of Scrum?
There is no one-size-fits-all answer to this question, as the decision of which software development methodology to use depends on several factors specific to each project. However, in general, the Waterfall model may be more appropriate for projects with well-defined requirements and deliverables, while Scrum may be more suitable for projects that are more flexible and evolving. Ultimately, the decision of which methodology to use should be based on a careful evaluation of the specific needs of each project.
52. What are the four key phases of business development?
The first phase of business development is known as the ideation stage. This is when an entrepreneur has an idea for a new business venture. They will need to research the feasibility of their idea and develop a plan to bring it to market.
The second phase of business development is the implementation stage. This is when the entrepreneur begins to execute their business plan. They will need to secure funding, build a team, and develop their product or service.
The third phase of business development is the growth stage. This is when the business starts to gain traction and grow. The entrepreneur will need to focus on scaling their operations and expanding their customer base.
The fourth and final phase of business development is the exit stage. This is when the entrepreneur decides to sell their business or take it public. They will need to plan for this eventuality and ensure that their business is in a position to be successful.
53. What do you know about Kanban?
Kanban is a popular system for managing workflows, and has been used in a variety of businesses and industries. It is based on the Japanese word for "sign" or "card," and was originally developed as a way to manage assembly line production in manufacturing.
Kanban has since been adapted for use in other industries, and has been found to be helpful in managing workflows in a variety of businesses. In recent years, it has become popular in the software development industry as a way to manage agile software development.
54. Mention some of the most important Agile metrics.
There are a number of metrics that can be used to measure the success of an Agile software development project. These include:
Velocity
This measures the amount of work that is completed in a given time period. It is a good indicator of productivity and can be used to predict how much work can be completed in future sprints.
Lead Time
This measures the time from when a user story is created to when it is delivered. It can be used to identify bottlenecks in the development process and to improve the flow of work.
Cycle Time
This measures the time from when work on a user story starts to when it is completed. It can be used to identify areas where the development process is taking too long and needs to be streamlined.
Defect Density
This measures the number of defects per unit of code. It is a good indicator of the quality of the code and can be used to identify areas where the quality needs to be improved.
Test Coverage
This measures the percentage of code that is covered by tests. It is a good indicator of the quality of the tests and can be used to identify areas where the test coverage needs to be improved.
These are just some of the most important agile metrics. There are many other metrics that can be used to measure the success of an agile project. The important thing is to choose the right metrics for your project and to use them to drive improvements.
55. Explain the term ‘increment'?
The term ‘increment’ is used to describe the process of adding a value to a variable. For example, if we have a variable called ‘counter’, and we want to add one to it, we would say that we are incrementing the counter by one. Similarly, if we have a variable called ‘total’, and we want to add 10 to it, we would say that we are incrementing the total by 10.
56. What are the different types of Agile methodologies?
There are several types of Agile methodologies, each with its own unique approach to software development. The most popular Agile frameworks include Scrum, Kanban, and Extreme Programming (XP).
57. Is there any difference between incremental and iterative development?
Both incremental and iterative development are software development processes that focus on delivering small, frequent updates rather than large, infrequent ones. The main difference between the two approaches is that incremental development delivers functionality in small, discrete chunks, while iterative development focuses on delivering larger pieces of functionality incrementally.
58. Difference between extreme programming and scrum?
There are a few key differences between extreme programming (XP) and scrum. The most notable difference is that XP focuses on code quality and customer satisfaction, while scrum emphasizes delivering working software quickly. Additionally, XP requires developers to work in close collaboration with customers, while scrum relies on input from a product owner. Finally, XP uses a "test-first" approach to development, while scrum employs an "iterative and incremental" approach. Despite these differences, both XP and scrum are agile software development frameworks that emphasize collaboration, customer involvement, and iterative development.
