Business Analysis Fundamentals
The BA Role and the Business Analysis Ecosystem
Business analysis is the set of activities that enable change in an enterprise by identifying needs and recommending solutions that deliver value. The BCS BA Foundation syllabus frames this around the Business Analysis Process Model and the competencies of a business analyst. Candidates must know the difference between a business analyst (who may be internal or external, and who may hold various job titles) and the business analysis discipline itself. The BA is not a project manager, though the roles may overlap; the BA focuses on understanding the business problem and defining requirements, while the PM focuses on delivery.
Key concepts include the three areas of business analysis as defined by BCS: business change, requirements engineering, and business analysis practice. You should understand the Business Analysis Maturity Model and the SFIA framework at a high level, but the exam tests understanding of the underlying competencies such as analytical thinking, communication, and stakeholder engagement. Another core concept is the solution - not just software, but any change to business processes, roles, or technology that addresses a need.
A common trap is confusing outputs with outcomes. Outputs are deliverables (e.g., a requirements document); outcomes are the measurable business benefits. Questions often ask which is which. Another trap is the BA's role in Agile - the BA does not disappear; they may act as product owner or facilitate backlog refinement. Also, be clear that business analysis can be performed by anyone, not only by someone with the BA title.
Worked example / rule of thumb: If a question asks whether a BA should define a solution before understanding the problem, the answer is always no. The BA first investigates the business situation and stakeholder perspectives, then defines requirements for a solution. Use the rule: Understand the need, then define the solution.