Become a Professional Business Analyst.
Learn business analysis, Agile, Scrum, SQL, UML and stakeholder management.
The interactive map needs JavaScript. Here is the full list.
Defines what a business analyst is accountable for across the project lifecycle, and how the role is distinct from a project manager, product owner or systems analyst even though the four often overlap in small teams.
Interviewers almost always open with some version of this question, and getting the boundaries wrong signals a lack of professional grounding.
Explain the BA role clearly in an interview and map day to day BA activities against the correct BABOK knowledge area.
Write a one page explanation of the BA role aimed at a non technical CEO.
Interview importance: High, common opening interview question.
Provides the base business literacy every BA needs, including how organisations are structured, how common business models work, and how to read core financial statements.
BAs are frequently asked to justify a project with a business case, and that requires basic comfort with revenue, cost and margin concepts.
Interpret a company's financial summary and describe its business model in plain language.
Analyse the executive summary of a public company's annual report and summarise its business model in half a page.
Interview importance: Medium, tested through case style questions.
Covers reading and interpreting the core financial documents that underpin any business case a BA builds.
BAs are expected to calculate a simple ROI or payback period when proposing a new solution, and cannot do this without understanding these statements.
Calculate a basic ROI for a proposed initiative and explain it to a non finance stakeholder.
Analyse a public company annual report executive summary and calculate its gross margin.
Interview importance: Medium, often tested through a short numerical exercise.
Covers identifying, analysing, and engaging the people and groups whose interests are affected by a project or whose support a BA needs.
Most project failures trace back to poor stakeholder alignment rather than a technical gap, which is why this is one of the most tested BA skills.
Build a stakeholder map for a real or hypothetical project and design a communication cadence for each group.
Map the stakeholders for a hypothetical Implement Cloud ERP project and assign each one to a quadrant of the power interest grid.
Interview importance: High, frequently tested through scenario questions.
Develops the interpersonal and workshop facilitation skills a BA relies on daily, including active listening, structured meeting facilitation, and negotiation basics.
Requirements work is fundamentally a conversation, and a BA who cannot facilitate a productive workshop will struggle to extract accurate information from stakeholders.
Plan and run a structured requirements workshop with a clear agenda and defined outcomes.
Design and role play a 30 minute requirements workshop agenda for a new mobile app feature.
Interview importance: High, communication skills are assessed in almost every BA interview.
Covers the hands on methods used to extract requirements from stakeholders, including interviews, surveys, workshops, observation and document analysis.
Choosing the wrong elicitation method for a given context wastes stakeholder time and often produces incomplete or misleading requirements.
Select the correct elicitation method for a given context and draft effective interview and survey questions.
Design an elicitation plan combining interviews and a workshop for a new customer portal project.
Interview importance: Very high, tested through scenario based questions.
Textual and diagrammatic representation of functional requirements, describing how an actor interacts with a system to achieve a goal.
Use cases are the industry standard for describing complex system interactions in healthcare, government and large enterprise IT, and frequently appear in technical interviews.
Create a complete use case diagram and narrative for a moderately complex feature.
Model the Place Order and Process Return use cases for an e-commerce application, including full narratives.
Interview importance: Very high, a classic whiteboard interview exercise.
The Agile format for defining product increments in a short, testable statement of value, paired with clear acceptance criteria that define done.
This is the standard requirements format at nearly every modern tech and product organisation, making it one of the most frequently tested BA skills.
Write well formed user stories with clear, testable acceptance criteria for a complex feature.
Write fifteen user stories for a Library Management System using Gherkin syntax for acceptance criteria.
Interview importance: Extremely high, near guaranteed in Agile BA interviews.
Covers the formal artefacts a BA produces to record requirements, including BRDs, FRDs and SRS documents, and how to structure them for different audiences.
Regulated industries such as finance and healthcare require formally documented and auditable requirements, and this documentation is the artefact that development teams build against.
Draft a well structured BRD outline and know when an SRS is required instead.
Draft a BRD outline for a website redesign, clearly separating business needs from proposed solution features.
Interview importance: High, especially the BRD versus SRS distinction.
The practice of linking each requirement to its originating business need, its design element and its test case, so nothing is lost between planning and delivery.
Mandatory in regulated industries like finance and healthcare where auditors need to prove every requirement was implemented and tested.
Build a working requirements traceability matrix in a tool such as Excel or Jira.
Build an RTM connecting three business goals to ten functional requirements and five test cases.
Interview importance: Medium, common in audit heavy industry interviews.
Covers structured techniques for deciding what to build first when time, budget or team capacity is limited, including MoSCoW and the Kano model.
Stakeholders rarely agree on priority naturally, and a BA who can facilitate an objective prioritisation exercise prevents scope disputes later in the project.
Run a prioritisation workshop and produce a defensible, ranked backlog.
Prioritise a backlog of twenty product backlog items using MoSCoW for a hypothetical mobile banking app.
Interview importance: High, frequently tested with a practical exercise.
Business Process Model and Notation is the global standard for documenting business processes using a consistent visual language.
It is often described as the SQL of process mapping, and is required knowledge in ERP implementations and automation initiatives at companies like SAP and Oracle customers.
Model a moderately complex business process in Camunda Modeler or Draw.io using correct BPMN notation.
Model the Order-to-Cash process for a telecom company using proper BPMN 2.0 notation.
Interview importance: High, modelling tests are common in interviews.
SIPOC diagrams and value stream maps give a high level view of a process, its suppliers, inputs, outputs and customers, before diving into detailed flowcharting.
These tools are used at the start of a process improvement engagement to scope the boundaries of what will be analysed in detail.
Build a SIPOC diagram and a basic value stream map for a real or hypothetical process.
Create a SIPOC diagram for a university admissions process, then identify non value-add steps.
Interview importance: Medium, often used as a scoping exercise question.
The practice of bridging the difference between a current state and a desired future state, and is often the core justification for project investment.
Business cases and transformation proposals almost always open with a gap analysis to prove why change is needed.
Create a gap analysis matrix that clearly separates people, process and system gaps.
Perform a gap analysis on a manual expense reporting process moving to an automated Concur or SAP flow.
Interview importance: High, common in transformation and M&A style interview questions.
Structured techniques such as the Five Whys and the fishbone diagram used to find the true underlying cause of a business problem instead of treating symptoms.
Recommending a solution before identifying the real root cause is one of the fastest ways a BA loses stakeholder trust.
Facilitate a root cause analysis session and produce a validated fishbone diagram.
Perform a fishbone root cause analysis for high cart abandonment on an e-commerce checkout page.
Interview importance: High, frequently used as a live problem solving exercise.
Covers how BAs identify processes that are good candidates for robotic process automation, and how to build a business case for automation investment.
Automation and digital transformation programmes rely heavily on BAs to correctly separate processes that are truly rule based and repetitive from those that need human judgement.
Assess a manual process and produce a justified recommendation on whether it is a good RPA candidate.
Identify RPA candidate processes for a shared services finance team and build a one page business case for one of them.
Interview importance: Medium, growing in importance as automation adoption increases.
Covers the roles, events and artefacts defined in the official Scrum Guide, and how a BA participates within that structure.
Scrum is the most widely adopted Agile framework, and understanding its exact terminology is essential to work effectively on any Agile team.
Explain each Scrum event and artefact accurately and describe how a BA supports each one.
Draft a one page Scrum cheat sheet mapping each event and artefact to the BA's specific contribution.
Interview importance: High, foundational Agile knowledge check.
Covers the Kanban method for visualising and limiting work in progress, and core Lean principles for eliminating waste in a workflow.
Many operations and support focused BA roles use Kanban rather than Scrum, making this a common alternative framework in interviews.
Design a Kanban board with sensible work in progress limits for a support or operations team.
Design a Kanban board for a customer support team handling three ticket types, with WIP limits justified by data.
Interview importance: Medium, common in operations focused BA roles.
Defines the specific activities a BA performs on an Agile team, including backlog management, sprint planning support and refinement facilitation.
A BA who cannot articulate their specific value on a Scrum team risks being seen as redundant next to the Product Owner.
Facilitate a backlog refinement session that leaves the team with clear, estimable, well written stories.
Facilitate a mock refinement session for five backlog items, producing estimates and acceptance criteria for each.
Interview importance: Very high, a core differentiator question in Agile BA interviews.
Covers structuring, ordering and maintaining a healthy product backlog so the development team always has a clear, prioritised set of work.
A messy or unrefined backlog is one of the fastest ways an Agile team loses velocity and stakeholder trust.
Take a messy list of feature requests and restructure it into a clean, ordered backlog in a tool like Jira.
Restructure a flat list of twenty five feature requests into an epic and story hierarchy with a justified priority order.
Interview importance: High, practical Jira based exercises are common.
Covers traditional sequential delivery approaches including Waterfall and the V-Model, and how PMBOK and PRINCE2 concepts apply in hybrid delivery environments.
Many industries such as government, banking and construction still run heavily governed waterfall or hybrid projects, and a BA who only knows Agile will be limited in those environments.
Explain when a waterfall or hybrid approach is more appropriate than pure Agile, and justify the choice.
Write a one page comparison of Waterfall, Agile and hybrid approaches for a regulated banking system upgrade.
Interview importance: Medium, tested in enterprise or government focused interviews.
Covers foundational data concepts including data types, relational versus NoSQL databases, data warehousing and basic data governance.
Every dashboard or SQL query a BA writes rests on understanding how the underlying data is structured and governed.
Explain the difference between a relational database and a NoSQL store, and describe basic data quality checks.
Write a one page explainer comparing a relational database and a document store for a non technical stakeholder.
Interview importance: Medium, foundational knowledge check.
Covers writing SQL queries to extract and summarise business data, from basic SELECT statements through joins, aggregation and window functions.
SQL is now one of the single most requested BA technical skills, since it lets a BA answer data questions directly instead of waiting on a data team.
Write a moderately complex SQL query independently to answer a real business question, such as customer retention.
Write a SQL query to find the second highest salary in an employee table, then a second query calculating month over month customer retention.
Interview importance: Extremely high, live SQL exercises are near universal in technical interviews.
Covers the principles of designing dashboards that communicate a clear decision ready story, rather than simply displaying every available metric.
A cluttered dashboard actively slows down decision making, so knowing how to prioritise and lay out metrics is a distinct skill from just knowing a BI tool.
Design a one page executive dashboard that clearly answers a specific business question.
Design a one page dashboard mockup showing quarterly sales performance for an executive audience.
Interview importance: Medium, often tested through a design critique exercise.
Hands on skill in the two most widely used business intelligence tools, used to connect to data sources and build interactive reports and dashboards.
These are the two most requested BI tools in BA and analyst job postings, and are often tested with a take home dashboard exercise.
Build and publish an interactive dashboard from a raw dataset in either Tableau Public or Power BI Desktop.
Build an interactive Power BI or Tableau dashboard for supply chain visibility using a public sample dataset.
Interview importance: High, take home dashboard exercises are common.
Covers advanced Excel features such as PivotTables and Power Query that let a BA clean, reshape and summarise data quickly without needing a database.
Excel remains the fastest tool for quick ad hoc analysis, and Power Query in particular saves enormous time compared to manual data cleaning.
Clean a messy raw dataset with Power Query and summarise it with a PivotTable in under thirty minutes.
Build an Excel dashboard from a sample sales dataset using PivotTables and at least one Power Query transformation step.
Interview importance: Medium, still commonly tested in practical Excel exercises.
Covers how systems exchange data through APIs, and how a BA reads, tests and writes requirements against them.
Most modern product requirements involve at least one system integration, and BAs who cannot read an API contract struggle to write accurate integration requirements.
Read a Swagger or OpenAPI specification and translate it into plain language integration requirements.
Review the OpenAPI specification for a sample public API and write a short requirements document describing three of its endpoints.
Interview importance: Medium to high, increasingly common in technical BA interviews.
Covers the REST architectural style and the JSON data format used by most modern web APIs.
Almost every integration requirement a BA writes today involves REST endpoints exchanging JSON, making this baseline literacy essential.
Read a JSON API response and identify the specific fields relevant to a business requirement.
Given a sample JSON API response, write out the business meaning of each field in plain English.
Interview importance: Medium, basic technical literacy check.
Covers the basics of AWS, Azure and GCP, the differences between IaaS, PaaS and SaaS, and how CI/CD pipelines fit into modern software delivery.
Cloud migration and modernisation projects are among the most common BA engagements today, and require the BA to speak the same basic vocabulary as the engineering team.
Explain the difference between IaaS, PaaS and SaaS with a concrete example of each, and describe how CI/CD reduces release risk.
Write a one page comparison of hosting a sample application on IaaS versus PaaS, including a rough cost and effort tradeoff.
Interview importance: Medium, increasingly asked in transformation focused interviews.
Covers the basic concepts of AI and machine learning, blockchain and IoT that BAs increasingly need to scope requirements for, without needing to build these systems themselves.
Business analysts are being asked to write requirements for AI features, chatbots and recommendation engines, and need enough conceptual grounding to ask engineers the right questions.
Write a requirements document for a simple AI feature, such as a chatbot, that reflects realistic AI capabilities and limitations.
Write a one page business case and requirements outline for an AI powered customer service chatbot, including expected accuracy limitations.
Interview importance: Medium, a growing area of interview interest.
Covers core banking systems, payment rails, lending workflows and the major regulatory frameworks that shape requirements in financial services.
Banking is one of the largest employers of business analysts, and regulatory requirements like Basel and PSD2 directly shape what a BA can and cannot propose.
Explain how a regulatory requirement such as PSD2 changes a specific product requirement in a payments project.
Write a compliance impact analysis for a EU payment gateway needing to meet PSD2 requirements.
Interview importance: High for banking sector interviews specifically.
Covers healthcare specific standards such as HIPAA, HL7 and FHIR, along with claims, enrollment and provider system concepts.
Healthcare BAs must understand both clinical workflow concepts and strict regulatory privacy requirements before writing any requirement involving patient data.
Write a requirement for a patient facing feature that correctly accounts for HIPAA constraints.
Draft HIPAA compliant requirements for a patient portal feature allowing appointment booking.
Interview importance: High for healthcare sector interviews specifically.
Covers the core systems that power online retail, including order management, content management, product information management and CRM, plus supply chain basics.
E-commerce BAs need to understand how these systems interact to correctly scope requirements for checkout, fulfillment and personalisation projects.
Map the system flow for a customer order from checkout through to fulfilment across the relevant retail systems.
Re-engineer the checkout process for an e-commerce site, producing a to-be BPMN diagram that reduces cart abandonment.
Interview importance: Medium to high for retail and e-commerce sector interviews.
Covers business support systems and operations support systems, plus emerging areas like 5G, IoT and smart grid technology relevant to telecom and utility BAs.
Telecom transformation projects are large, long running and heavily systems dependent, making BSS/OSS literacy essential for BAs entering this sector.
Explain the difference between BSS and OSS systems and where a specific requirement would sit in that landscape.
Draft a transformation plan outline for a telecom operator's OSS/BSS modernisation ahead of 5G rollout.
Interview importance: Medium for telecom and utilities sector interviews.
Covers strategic planning, capability based planning and enterprise architecture frameworks like TOGAF that connect BA work to overall organisational strategy.
Business architects and senior BAs are expected to translate high level strategy into concrete capability roadmaps that guide multi year investment decisions.
Build a capability map for an organisation and connect it to a proposed investment roadmap.
Produce a capability based planning map for a retail bank, prioritising three capabilities for investment over the next two years.
Interview importance: High for business architect and senior BA interviews.
Covers product vision setting, roadmapping, customer journey mapping and experimentation, the core toolkit of a Product Owner or Product Manager.
Many BAs progress into Product Owner or Product Manager roles, and these skills mark that transition from purely eliciting requirements to owning product direction.
Draft a one page product vision and a quarterly roadmap for a new feature area.
Create a product vision box and a two quarter roadmap for a HealthTech startup's patient engagement feature.
Interview importance: High for Product Owner and Product Manager track interviews.
Covers structured problem solving, executive communication and proposal writing skills used by BAs working in a consulting or advisory capacity.
Consulting style problem structuring, such as MECE and issue trees, is one of the most transferable senior BA skills across every industry.
Structure an ambiguous business problem into a MECE issue tree and present the resulting recommendation in ten slides or fewer.
Build an issue tree for the ambiguous problem, how would you improve Gmail, and present a top line recommendation.
Interview importance: High, product sense and structuring questions are common at senior levels.
Covers coaching junior BAs, building internal communities of practice, and contributing thought leadership back to the profession.
Senior BAs are increasingly evaluated on how well they grow the people and practice around them, not just their individual delivery.
Design a lightweight mentoring plan for onboarding a junior BA over their first ninety days.
Draft a ninety day onboarding and mentoring plan for a new junior business analyst joining your team.
Interview importance: Medium, assessed mainly at lead and principal BA levels.
An entry level role that supports senior BAs, takes meeting notes, maintains documentation and gradually takes on small pieces of independent analysis.
This is the standard first step into the profession and the role most graduates or career changers target first.
Support senior BAs on documentation and note taking while building toward independent requirements work.
Build a portfolio BRD and a BPMN process map for a hypothetical project to use in job applications.
Interview importance: N/A, this is a career stage rather than an interview topic.
An independent contributor role owning end to end requirements for one or more projects, from elicitation through to delivery support.
This is the core BA role most professionals spend the majority of their career in, and the target for most learners completing this roadmap.
Own the full requirements lifecycle for a project independently, from stakeholder interviews to delivery validation.
Complete three end to end sample projects and one data dashboard to demonstrate readiness for this level.
Defines product vision, manages the backlog and represents the customer's voice to the development team on an Agile project.
A common next step for BAs who want to move closer to product strategy and customer facing decision making.
Own a product backlog end to end, balancing stakeholder demands against a clear product vision.
Build a product vision box and a fully prioritised backlog for a sample HealthTech feature area.
A strategic advisor role leading large, complex transformation initiatives, often specialising in a specific industry domain.
This role marks the shift from execution focused BA work toward strategic advisory and executive facing responsibility.
Lead a complex, multi stakeholder transformation initiative from business case through to delivery oversight.
Write a full business case, BRD and executive summary for a complex system replacement project in a chosen industry.
Connects organisational strategy to execution through capability models and enterprise architecture, guiding multi year transformation roadmaps.
This role suits BAs who enjoy the strategic, systems thinking side of the profession more than day to day requirements delivery.
Translate high level company strategy into a capability roadmap that guides multi year investment decisions.
Produce a capability model and three year transformation roadmap for a chosen industry vertical.
Owns the full product lifecycle and often P&L responsibility, combining product sense, analytics and experimentation to drive business outcomes.
A common long term destination for BAs and Product Owners who want full end to end ownership of a product's success.
Lead a product from vision through launch, using experimentation and analytics to validate decisions along the way.
Write a product launch case study for a hypothetical feature, including the experiment design used to validate it.
This is the entry point of the business analysis discipline. It establishes what a business analyst actually does, how the role fits alongside project managers, product owners and system analysts, and the base level of business and communication literacy every BA needs before touching requirements work.
Every later subdomain in this roadmap assumes the learner already understands the BA identity, can read basic financial statements, and can run a stakeholder conversation. Skipping this stage is the single biggest reason junior BAs struggle in their first role.
A learner finishing this stage can explain the BA role to a non technical executive, read a company annual report, and run a basic stakeholder mapping exercise for a new initiative.
Write a one page brief explaining business analysis to a non technical CEO, then build a stakeholder power interest grid for a hypothetical cloud ERP rollout.
Interview importance: High, this is where most introductory interview questions come from.
The systematic process of discovering, analysing, documenting and validating what the business and its stakeholders actually need from a solution. This is the primary deliverable of the BA profession and the single most heavily tested competency in interviews.
Almost every downstream artefact a BA produces, from a BRD to a backlog item, traces back to how well requirements were elicited and modelled here. Weak requirements work is the most common root cause of project failure across industries.
A learner finishing this stage can run a full requirements cycle end to end, from planning elicitation sessions through to producing a validated, prioritised, and traceable requirements document.
Run a complete requirements cycle for a hypothetical Library Management System, from a stakeholder interview through to a validated backlog of user stories with acceptance criteria.
Interview importance: Extremely high, this subdomain generates the majority of technical BA interview questions.
Covers visualising, analysing and improving business workflows using standardised notations, with the aim of increasing efficiency and reducing waste across an organisation.
Nearly every ERP implementation, automation initiative and digital transformation programme starts with an accurate process map, making this a core skill for senior BAs and process analysts.
A learner finishing this stage can produce a BPMN compliant process map, identify waste and bottlenecks in it, and propose a justified improvement or automation plan.
Model the current Order-to-Cash process for a telecom company in BPMN, identify at least three inefficiencies, then design a to-be version with an automation opportunity flagged.
Interview importance: Very high, modelling exercises are common in senior BA interviews.
Covers how a business analyst operates inside iterative, waterfall and hybrid delivery methodologies, including the specific BA responsibilities within a Scrum team.
Most modern product organisations run Agile or a hybrid model, and BAs who cannot translate their requirements skills into a sprint cadence struggle to add value on Agile teams.
A learner finishing this stage can operate effectively as the BA on a Scrum team, from backlog refinement through sprint planning, while still understanding how to work in a traditional waterfall environment when required.
Facilitate a mock backlog refinement session for a five item feature set, including estimation and clearly defined acceptance criteria for each item.
Interview importance: Very high, nearly universal in modern BA job interviews.
Builds the data literacy, SQL skills and dashboard design ability that modern BAs are expected to bring, since most business cases and process improvements now need to be backed by data.
Employers increasingly expect BAs to pull and interpret their own data rather than waiting on an analyst, which makes SQL and basic dashboarding a near mandatory skill set.
A learner finishing this stage can write a moderately complex SQL query to extract business data, and build a clear, decision ready dashboard from it.
Write a SQL query to find the second highest salary in an employee table, then build a one page Power BI or Tableau dashboard visualising department headcount trends.
Interview importance: High, live SQL exercises are common in technical BA interviews.
Covers the baseline technical literacy modern BAs need to work effectively alongside engineering teams, including APIs, cloud fundamentals and emerging technology awareness.
As BAs increasingly work on API driven and cloud native products, being unable to read basic API documentation or understand cloud service models limits how effectively a BA can gather and validate requirements.
A learner finishing this stage can read an API's Swagger documentation, test an endpoint in Postman, and explain the difference between IaaS, PaaS and SaaS to a stakeholder.
Use Postman to test a public REST API, document three of its endpoints in a simple requirements format, and note any gaps found in the official documentation.
Interview importance: Medium to high, increasingly common as BA roles get more technical.
Covers deep, industry specific knowledge that differentiates a generalist BA from one who can speak fluently to domain experts in banking, healthcare, e-commerce or telecom.
Senior BA and consulting roles are almost always tied to a specific industry, and domain expertise is frequently the deciding factor between two otherwise similar candidates.
A learner finishing this stage can hold a credible conversation with a domain expert in at least one industry and understands the regulatory and system landscape specific to it.
Pick one industry, research its core systems and one major regulation, and write a one page domain briefing document as if onboarding a new BA into that team.
Interview importance: High for senior roles, domain questions are common in specialised interviews.
Covers the strategic, consulting and leadership skills that separate senior BAs, product owners and business architects from execution focused junior BAs.
As BAs progress, they are expected to shift from documenting requirements to shaping strategy, influencing without direct authority, and mentoring the next generation of analysts.
A learner finishing this stage can lead a strategic initiative, present confidently to executives, and mentor junior BAs on the profession's core practices.
Prepare and deliver a ten minute executive presentation proposing a new strategic initiative, structured using the MECE principle and issue tree.
Interview importance: High for senior BA, consultant and business architect interviews.
