Business Analyst Top 50 Q&A

A BA acts as a bridge between business stakeholders and the technical team, identifying business needs and finding solutions (often software-based) to business problems.

A BA focuses on the 'what' and 'why' (requirements, solution), while a PM focuses on the 'when' and 'how much' (timeline, budget, resources).

It involves elicitation (interviews, surveys), analysis, documentation (BRD/FRD), and validation with stakeholders.

Functional requirements describe what the system does (e.g., "User can login"). Non-functional requirements describe how it performs (e.g., "The page should load in 2 seconds").

A high-level document that outlines the business goals and the overall needs of the stakeholders for a project.

A more technical document that describes the specific features and behaviors required to meet the business requirements.

Interviews, Workshops, Brainstorming, Observation, Document Analysis, and Surveys.

The process of comparing the current state (As-Is) with the desired future state (To-Be) to identify what needs to be changed.

A simple description of a feature from the user's perspective, following the format: "As a [user], I want [action] so that [benefit]."

The specific conditions that a user story must satisfy to be considered "Done" by the stakeholders.

An iterative approach to software development that focuses on continuous delivery, customer feedback, and small, frequent releases.

A specific framework within Agile that uses Sprints (2-4 week cycles) and specific roles like Product Owner, Scrum Master, and Development Team.

A prioritized list of everything that might be needed in the product. It's the single source of requirements for any changes to be made.

A meeting where the team reviews backlog items to ensure they are well-defined, estimated, and ready for the next sprint.

Independent, Negotiable, Valuable, Estimable, Small, and Testable.

Waterfall is linear and sequential (plan everything at once). Agile is iterative and flexible (plan as you go).

A visual tool for managing work as it moves through a process, focusing on limiting Work In Progress (WIP).

A BA often assists the Product Owner in defining user stories, managing the backlog, and clarifying requirements for the developers during the sprint.

The version of a new product that allows a team to collect the maximum amount of validated learning about customers with the least effort.

The process of Planning, Analysis, Design, Implementation, Testing, and Maintenance of software.

A standardized modeling language used to visualize the design of a system. Common diagrams: Use Case, Activity, Sequence.

Shows the interactions between users (actors) and the system to achieve a specific goal.

A visual representation of a process or workflow, using shapes to represent steps and arrows to represent flow.

A popular project management tool for Agile teams to track tasks, bugs, and user stories.

A documentation tool (often used with Jira) to store project requirements, meeting notes, and knowledge base.

A graphical representation for specifying business processes in a business process model.

Structured Query Language. BAs use it to retrieve and analyze data directly from databases to validate requirements or findings.

Creating a preliminary version of a solution (like a wireframe or mockup) to gather feedback before full development.

A wireframe is a low-fidelity blueprint (skeleton). A mockup is a high-fidelity visual design (skin).

Must have, Should have, Could have, and Won't have. A technique to prioritize requirements.

By actively listening to their concerns, understanding their underlying needs, and using data/logic to reach a consensus.

A tool to categorize stakeholders based on their power and interest to determine how to manage them effectively.

In Agile, we embrace change through the backlog. I would assess the impact, discuss it with the PO, and reprioritize the work.

The final phase of testing where the actual users test the system to ensure it meets their business needs.

By having clearly defined requirements, a strict change control process, and continuous communication with stakeholders.

I facilitate a meeting to find common ground and focus on the project's primary objectives.

It ensures you fully understand the stakeholder's problem before jumping to a solution.

By asking probing questions, showing examples/prototypes, or researching existing documentation.

Verification: "Are we building the product right?" (matches specs). Validation: "Are we building the right product?" (meets needs).

An assessment of the practicality of a proposed plan or method (Technical, Economic, Legal, Operational, Schedule).

Use the STAR method. Focus on the analysis you did and the specific benefit to the business.

By avoiding technical jargon, using diagrams, and getting feedback from both business and tech teams.

Mention Jira, Visio, or even Excel, and explain how it helps your specific workflow.

By communicating as early as possible, explaining the reason, and providing a revised plan to minimize impact.

Problem-solving, critical thinking, and the ability to ask the "Why" behind every requirement.

Following IIBA, attending webinars, and learning new tools like AI for requirement analysis.

Connect your experience to their specific industry or product challenges.

I would discuss it with the tech team to understand the limitation and then present alternative solutions to the business.

By breaking it down into smaller, researchable pieces and validating my assumptions with stakeholders.

Ask about their project methodology, their biggest BA challenge, or the team structure.