Ở phần 01: Những câu hỏi phỏng vấn “open-ended (cảm tính)” dành cho Business Analyst, BAC đã cùng các bạn tìm hiểu về nhóm các câu hỏi cảm tính (là loại câu hỏi được hỏi dựa trên cảm tính của người hỏi: dựa vào thực tế dự án, và kinh nghiệm của người hỏi, và câu trả lời cũng dựa trên khả năng xử lý tình huống và giải quyết), được tổng hợp bằng tiếng Anh.
- Nhóm câu hỏi cảm tính: là loại câu hỏi được hỏi dựa trên cảm tính của người hỏi: dựa vào thực tế dự án, và kinh nghiệm của người hỏi, và câu trả lời cũng dựa trên khả năng xử lý tình huống và giải quyết.
- Và nhóm câu hỏi có câu hỏi kiến thức chuyên môn có đáp án: Là nhóm câu hỏi có đáp án rõ ràng, đúng sai dựa trên lý thuyết và kiến thức.
Tiếp tục chuỗi bài viết về kỹ năng phỏng vấn dành cho Business Analyst, ở bài này, các bạn hãy cùng BAC “vượt qua” nhóm câu hỏi có câu hỏi kiến thức chuyên môn có đáp án (tức nhóm câu hỏi có đáp án rõ ràng, đúng sai dựa trên lý thuyết và kiến thức, được tổng hợp bằng tiếng Anh nhé! (BAC sẽ tổng hợp bằng cả ngôn ngữ tiếng Anh và tiếng Việt, nhằm phục vụ theo đúng từng nhu cầu tìm kiếm của các bạn BAs.)
Question 1: “Who is a 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.”
Question 2: “Name some of the documents that a business analyst uses 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)”
Tham khảo các loại tài liệu ở đây.
Question 3: “What is SRS what are its key elements?”
Answer: “A System Requirements Specification (SRS) or a Software Requirements Specification is a document or set of documents that describe the features of a system or software application. It includes a variety of elements that define the intended functionality required by the stakeholders and customers to satisfy the end-users.
In addition to that, an SRS provides a high-level idea of the system and its behavior, the main supported business processes, the assumptions, and the key performance parameters for the system. The key elements of an SRS are:
Scope of Work
Functional Requirements
Non-Functional Requirements
Dependencie
Data Model
Assumptions
Constraints
Acceptance Criteria”
Question 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 purposes.”
Question 5: “What is a use case?”
Question 6: “What are the steps that you need to follow to design a use case?”
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 are relevant to the system.
Identify essential goals associated with each role. Also, identifying the significant roles.
Creating use cases for every goal associated with 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”
Question 7: “What is a scope creep?”
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.”
Question 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:
- It is a high-level functional specification of the software;
- It is a formal document to describe the requirement provided by the client (written, verbal);
- The Business Analyst creates it after their direct interaction with the clients;
- It is derived based on the requirements and client interaction.
- SRS:
- It is a high level functional and technical specification of the software;
- It describes the functional and non-functional requirements of the software to be developed;
- The System Architect creates it as it needs technical expertise. Though sometimes Bas too can create it;
- It is derived from the BRS.”
Question 9: “What is Gap Analysis?”
Question 10: “What is requirement prioritization? What are the different techniques used for it?”
There are various techniques that are used for requirements prioritization:
MoSCoW Technique
Requirements Ranking Method
100-dollar method
Kano Analysis & More
Five Whys”
Question 11: “What is the required elicitation technique?”
Question 12: “What is the fundamental difference between a requirement and need in a business analysis perspective?”
Question 13: “What are non functional requirements and how do you capture them?”
Question 14: “What are the skills that a business analyst must possess?”
Fundamental skills
Technical skills
Business Analysis skills”
Question 15: “How will you define a good quality requirement as business analyst?”
Specific: The requirement should be specific and could be documented properly
Measurable: Different parameters can measure the success criteria of the requirement
Attainable: The requirement should be feasible within the scope of the given resources
Relevant: The requirement must be in line with the project’s business case
Timely: The requirement should be communicated early in the project lifecycle”
Question 16: “Which documents are used to capture non-functional requirements?”
SDD (System Design Document)
FRD (Functional Requirement Document)”
Question 17: “What is an alternate flow in a use case diagram?”
Question 18: “Define Personas?”
Question 19: “What is an activity diagram and what are the important elements of it?”
The important elements in the Activity diagram are initial nodes, activities, control flows, decisions, a fork, guard conditions, join and end nodes.”
Question 20: “What is UML modeling?”
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 modeling 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.”
Question 21: “What are the best practices to follow while writing a use case?”
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.”
Question 22: “What is the difference between exception flow and alternate flow?”
Exception flow is the path traversed in case of any exception or error.”
Question 23: “Do you think a business analyst should be involved in testing?”
Question 24: “What does INVEST stand for?”
Independent
Negotiable
Valuable
Estimable
Sized Appropriately
Testable”
Question 25: “What is Pareto Analysis?”
Question 26: “What is BPMN and what are its basic elements?”
There are five basic elements of BPMN, and they are –
Flow Objects
Data
Connecting Objects
Swimlanes
Artifacts”
Question 27: “What is Kano analysis?”
Question 28: “What are the different types of actors you know in use case diagrams?”
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”
Question 29: “What are the different types of gaps that a business analyst can encounter during gap analysis ?”
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 the 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”
Question 30: “What is Benchmarking?”
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.”
Question 32: “How do you perform requirement gathering?”
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 approvers 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 that 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 a later point in 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.”
Question 33: “Why it is necessary for a business analyst to get involved during the implementation of requirements ?”
Question 34: “What are the problems that a business analyst may face?”
Employees related issues
Technology-related problems
Access related
Business policies related issues
Business model errors”
Question 35: “Explain the requirement elicitation strategy”
Brainstorming
Interviews
Observation
Document Analysis
Focus Groups
Requirements Workshops
Interface Analysis
Survey or Questionnaire
Prototyping”
Question 36: “What is Business Model Analysis?”
Question 37: “Do you think the role of a Business Analyst is a need for a project?”
During the project kick-off session, there are high possibilities that some technical queries come up from stakeholders 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 requirements or modifications of requirements can be asked from stakeholders considering changing business needs. In this case business analyst is the person who can handle this change request with proper validation and analysis.”
Question 38: “What is the difference between Business analysis and Business analytics?”
Business analysis – recognizes business needs and determines the solutions to those problems. Tools and techniques like SWOT, PESTLE, CATWOE, MOST, FIVE WHY, etc. are used for business analysis.
Business analytics – handles data and analyzes 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.”
Question 39: “What is process design?”
Question 40: “What are the effective skills to solve any problems as a business analyst?”
Leadership skill
Excellent communication skill
Problem analysis skill
Technical knowledge
Domain knowledge”
Question 42: “What are the essential qualities of an Agile BA ?”
The BA has expected to work to collaborate with product owners and developers to elicit requirements. The BA also must work to develop real 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.”
Question 43: “When should you use the Waterfall model instead of Scrum?”
Question 44: “What are the four key phases of business development?”
Forming
Storming
Norming
Performing”
Question 45: “What do you know about Kanban?”
Question 46: “Mention about some of the most important agile metrics?”
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 through this diagram of cumulative flow. Here the x-axis represents time and the y-axis stands for the number of efforts.
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 for this purpose are:
bug fixing
eliminating the bug
Scheduling a fix
Defect fixation
Handover of the resolution report”
Question 47: “Explain the term ‘increment’?”
Question 48: “What are the different types of Agile methodologies?”
Scrum
Lean software development and Extreme Programming (XP)
Feature-driven development (FDD)
Crystal Methodology
DSDM (Dynamic Software Development Method)”
Question 49: “Is there any difference between incremental and iterative development?”
Question 50: “Difference between extreme programming and scrum?”
Though we have categorized the above business analyst interview questions based on the experience levels, however, it could be a mix and match for any career level depending on the organization and their requirement.”
Question 52: “Who uses the output produced by business analysts?”
Question 53: “Why are excellent communication skills essential for a Business Analysyt?”
Question 54: “What is the difference between a Data Model and an Entity Relationship Diagram?”
Structural part: how data is structured.
Integrity part: rules governing structure.
Manipulation part: operators used to select, update, query data, e.g. select, update, delete commands in SQL.”
Question 55: “What is the educational qualification required for a Business Analyst ?”
Question 56: “What is UML? Mention the components of UML?”
For Structure: Actor, Attribute, Class, Component, Interface, Object, Package.
For Behavior: Activity, Event, Message, Method, Operation, State, use case.
For Relationships: Aggregation, Association, Composition, Depends, Generalization (or Inheritance).
Other Concepts: Stereotype. It qualifies the symbol it is attached to.”
Question 57: “Mention some of the important points a Business Analyst must take care of while preparing a business plan?”
Question 58: “Why are Business Analysts vital in an organization?”
Question 59: “What are the quality procedures followed normally by a Business Analyst?”
Question 60: “How is requirement analysis done by Business Analysts?”
Question 62: “What are the problems that Business Analysts could face during gathering business requirements?”
Question 63: “What is the relationship between use case and test case?”
- Cách làm CV chuẩn cho Business Analyst
Những câu hỏi phỏng vấn hay & phổ biến nhất dành cho Senior & Technical Business Analyst
Những câu hỏi phỏng vấn hay & phổ biến nhất dành cho Junior & Behavioral Business Analyst
Những câu hỏi phỏng vấn hay & phổ biến nhất dành cho Business Analyst
Những câu hỏi phỏng vấn “Open-Ended (Cảm tính)” dành cho Business Analyst (Tiếng Anh)
Nhu cầu đào tạo doanh nghiệp
CÁC KHOÁ HỌC BUSINESS ANALYST BACs.VN DÀNH CHO BẠN
Khoá học Online:
Khoá học Offline:
Tại Tp.HCM:
Tại Hà Nội:
Tham khảo lịch khai giảng TẤT CẢ các khóa học mới nhất
Ban biên tập nội dung – BAC