Business Analysis Practice
The BA Process in Practice
This domain covers how business analysis is conducted within a project or change lifecycle. The Business Analysis Process Model (often depicted as a cycle) includes stages: investigate situation, consider perspectives, analyse needs, evaluate options, and define requirements. You should know the sequence and the activities within each stage.
A key concept is the business case, which justifies investment in a change. It includes costs, benefits, risks, and a recommended option. The BA often contributes to the business case by providing requirements and options analysis. A trap is assuming the BA owns the business case; typically, the sponsor or project board approves it.
Stakeholder engagement is continuous throughout the process. The BA must identify stakeholders, analyse their influence and interest, and plan communication. Requirements engineering (covered in domain 4) is part of this practice.
Modelling business processes is a core BA activity. The BPMN (Business Process Model and Notation) standard is often used, but the exam may test basic concepts like as-is vs to-be processes. A trap is confusing the two: as-is models the current state, to-be models the future state.
Gap analysis identifies the difference between as-is and to-be, and is used to define what needs to change. Solution evaluation involves assessing whether a solution has delivered the expected benefits, often through benefits realisation activities.
Worked example / rule of thumb: In a project, the BA should start by understanding the business situation (investigate), then consider stakeholder perspectives, then analyse needs, then evaluate options, and finally define requirements. Use the mnemonic I-C-A-E-D (Investigate, Consider, Analyse, Evaluate, Define). A common exam question asks what comes after analysing needs: the answer is evaluating options.