Which of these is NOT considered to be a primary role of a Business Analyst?

The primary function of a Business Analyst (BA) is to serve as the liaison between business stakeholders and technical teams. Core responsibilities include understanding business problems, defining needs, and recommending solutions. This encompasses requirements analysis, supporting the implementation of the chosen solution, and participating in testing to ensure the solution delivers the expected value. Programming, the act of writing software code, is a distinct and specialized role performed by developers or software engineers. While a technical understanding is beneficial for a BA, coding is not a primary function of their role.

A. Requirements Analysis: This is a fundamental and core activity for a Business Analyst, involving eliciting, analyzing, documenting, and managing requirements.

B. Testing: Business Analysts are heavily involved in testing, particularly User Acceptance Testing (UAT), to validate that the solution meets the specified business requirements.

C. Implementation: BAs play a crucial supporting role during implementation by facilitating communication, managing change, and ensuring the solution is adopted correctly by the business.

1. International Institute of Business Analysis (IIBA). (2015). A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3. In Chapter 1, Section 1.2, the role of a business analyst is defined as "a practitioner who works with stakeholders to discover, synthesize, and analyze information... to elicit the actual needs of stakeholders." The guide's knowledge areas, such as "Requirements Analysis and Design Definition" and "Solution Evaluation," explicitly cover options A, B, and C, but do not include programming.

2. The University of Texas at Austin, McCombs School of Business. (n.d.). Business Analyst Certificate Program Course Descriptions. The curriculum outlines key BA skills including "Requirements gathering, analysis, and documentation," "Process modeling," and "Stakeholder management." The role is consistently positioned as a bridge to IT, not as a member of the coding/development team.

3. Pohl, K. (2010). Requirements Engineering: Fundamentals, Principles, and Techniques. Springer. DOI: https://doi.org/10.1007/978-3-642-12578-2. Chapter 1, Section 1.1.3, clearly distinguishes between the roles in a development project, separating the requirements engineering (a core BA function) from the design and implementation (programming) phases.