The Business Analysis Doctor, LLC

10/19/2026

BA Interview Questions - Part 2

I’m sharing my list of the 35 essential business analyst interview questions and answers.

10/16/2026

BA Interview Questions

I’m sharing my list of the 35 essential business analyst interview questions and answers.

Get the answers to these questions here: https://youtu.be/0HVwLAG2EXA

10/12/2026

Top Difficult Conversations Business Analyst Will Face

Successful business analysts approach difficult conversations with preparation, empathy, evidence, and a focus on business outcomes. The goal is not to win an argument but to help stakeholders make informed decisions and work collaboratively toward solutions.

Below are some of the most common difficult conversations you are likely to have as a Business Analyst.

- Telling a Stakeholder Their Request Is Out of Scope
- Managing Unrealistic Stakeholder Expectations
- Resolving Conflicting Requirements Between Stakeholders
- Challenging a Stakeholder's Proposed Solution
- Telling Stakeholders Their Requirements Are Unclear
- Stakeholder Who Changes Requirements Excessively
- Telling a Stakeholder Their Request Is Not Feasible
- Stakeholders Preferred Approach Creates Business Risk
- Challenging a Senior Stakeholder or Executive
- Addressing Limited Stakeholder Availability or Engagement
- Stakeholders Requested Feature Will Not Be Delivered
- Addressing Disagreements About Decision-Making Authority
- Reporting the Solution Is Not Delivering Expected Value

Below are some tips to approach these conversations.

P.S.
Learn more about navigating difficult conversations at your upcoming IIBA Certification (CBAP, CCBA, ECBA) Prep here: https://thebadoc.com/iiba-certification

10/11/2026

10/09/2026

Key Project Roles Business Analysts Work With

Successful projects are built through collaboration, clear communication, and shared goals. Business Analysts (BAs) play a vital role in connecting business needs with technical solutions, helping everyone stay aligned throughout the project lifecycle.

Here are 13 key project roles BAs commonly work with and how they contribute to project success:

1. Subject Matter Expert (SME): Provides specialized knowledge, answers questions, and validates business rules and processes.

2. Developer: Builds the solution and translates technical requirements into working functionality.

3. QA Analyst: Tests the solution, identifies defects, and verifies that requirements are met.

4. Data Analyst: Analyzes data, identifies trends, and supports data-driven decisions.

5. Project Manager (PM): Manages timelines, resources, planning, and overall project delivery.

6. Scrum Master/Team Coach: Facilitates Agile practices, removes obstacles, and supports team effectiveness.

7. Product Owner (PO): Defines product vision, prioritizes the backlog, and maximizes business value.

8. Solution Architect: Designs the overall solution and ensures technical direction, integration, and scalability.

9. Project Sponsor: Provides strategic direction, secures funding, removes organizational barriers, and champions the project.

10. Database Engineer: Designs and maintains database infrastructure, ensuring data availability, performance, and security.

11. Security Analyst: Identifies security requirements, assesses risks, and helps ensure compliance with security standards.

12. Regulatory SME: Provides regulatory guidance and helps ensure that requirements meet legal and compliance standards.

13. Change Manager: Supports adoption, manages organizational change, and helps minimize resistance through communication, documentation, and training.

Strong collaboration between project roles helps reduce misunderstandings, manage risks, improve solution quality, and deliver outcomes that meet business needs.

10/08/2026

It's THEORY THURSDAY!!!!! The difference between business analysis, business intelligence, and business analytics can seem subtle, yet they are distinct from one another for several reasons. Check out the focus areas of these three disciplines here: https://thebadoc.com/ba-quotes

10/08/2026

Pass the Agile Analysis Certification (IIBA-AAC) exam on your first attempt!

I'm showing you how to prepare for the IIBA-AAC (Agile Analysis Certification) exam, create an effective study plan, improve your retention, and focus your preparation on the areas that matter most.

The IIBA-AAC exam can be challenging if you approach it as simply a memorization exercise. Successful preparation requires you to understand Agile Analysis concepts, apply Agile practices, and know how to approach scenario-based exam questions.

In this presentation, I cover:

- Key areas of the Agile Extension to the BABOK Guide you need to understand
- How to create an effective IIBA-AAC study plan
- Strategies for improving retention and recall while studying
- What you need to know about the IIBA-AAC exam format and questions
- How to focus your study time on the most important Agile Analysis concepts
- Common mistakes candidates make when preparing for the AAC exam
- Practical tips to help you approach the exam with greater confidence
- How to prepare to pass the IIBA AAC exam on your first attempt

Check out the session here: https://youtu.be/QZvF51mFBxM

10/06/2026

Requirements Workshops and JAD Sessions

These are amongst the most widely used requirements gathering and elicitation techniques for business analysts across the globe. JAD is an acronym for Joint Application Development.

JAD sessions are increasing in popularity to execute requirements workshops as many organizations have an increased focus on collaborative methods.

Check out the full tutorial here: https://youtu.be/s25hs8YazTo
See less

09/30/2026

Which BA Specialization Is Right for You?

Business Analysis is much broader than a single job title. As organizations adopt new technologies, methodologies, and business models, BAs can develop specialized expertise in areas that align with their interests and career goals.

Here are some of the top Business Analyst specializations:

Agile Business Analyst - Requirements and analysis within Agile/Scrum environments, including user stories, backlog refinement, and product collaboration.

Technical Business Analyst - APIs, integrations, databases, system architecture, and technical requirements.

Business Systems Analyst - Analyzing and specifying how software systems should work, including functional and technical requirements.

Digital Business Analyst - Digital products, customer experiences, websites, mobile apps, digital transformation, and emerging technologies.

Data Business Analyst - Data requirements, data analysis, reporting, data quality, KPIs, and business intelligence.

Business Intelligence Analyst - Dashboards, reporting, analytics, data visualization, and decision support.

Cybersecurity Business Analyst - Translating business needs and risks into cybersecurity requirements, controls, processes, and solutions.

RPA Business Analyst - Identifying processes suitable for Robotic Process Automation and defining automation requirements.

AI Business Analyst - Identifying AI opportunities, defining AI-related business requirements, evaluating AI use cases, and supporting AI implementation.

Process Business Analyst - Process analysis, process improvement, optimization, redesign, and automation.

Enterprise Business Analyst - Cross-functional analysis involving enterprise strategy, capabilities, processes, systems, and organizational change.

ERP Business Analyst - Business processes and requirements surrounding ERP platforms such as SAP, Oracle, or Microsoft Dynamics.

CRM Business Analyst - Customer relationship processes and platforms such as Salesforce, Dynamics, and other CRM systems.

HR Business Analyst - HR processes, workforce data, talent management, payroll, benefits, and HR technology.

P.S.

The upcoming Agile Analysis Certification (IIBA-AAC) starts on October 17th. Check out the details via the website in bio.

09/27/2026

One of the most common questions I get during the Agile Analysis Certification Prep Program is how to document non-functional requirements (NFRs) in Agile. So here are a few tips to capture NFRs effectively.

- NFRs as part of the Definition of Done -
In many cases, non-functional requirements such as security, accessibility, and reliability, are low-effort and apply to the entire solution instead of specific functionality. Here, it may be appropriate to include the NFRs as part of the team's "definition of done," which is the list of conditions that must be true for all backlog items to be considered done.

- NFRs as Acceptance Criteria -
For cases where the non-functional requirement is low-effort and applies to a specific functionality, such as a response time performance or accuracy, the NFR may be included in the acceptance criteria for a specific user story.

- NFRs as Backlog Items -
In situations where the non-functional requirements are larger or more complex, it may be best to create an independent backlog item so that the effort is visible but doesn't hold up the completion of other backlog items. If this NFR is related to a specific user functionality, it may be documented as a user story. If it applies to the entire solution and is more architectural, it may be documented as an enabler.