BAPv5 Exam Dumps : BCS Practitioner Certificate in Business Analysis Practice v5.2

The business case guidance states that risk assessment should identify principal risks and—critically—define countermeasures: what can be done to reduce the likelihood of the risk occurring or lessen its impact. It notes that some risks can be transferred (e.g., via insurance), but the key is choosing countermeasures that actually address the cause.

Here, the risk is behavioural: managers may struggle to adopt a new management style required by the change. The book explicitly recognises that business change often requires changes to working practices and sometimes management style, especially where roles and authority shift. The most direct countermeasure is to build capability and readiness in the affected managers—through training, education, coaching, and support—so they understand the new behaviours, can practise them, and can be reinforced through agreed expectations. This reduces both the probability of failure (managers not changing) and the impact (inconsistent adoption harming productivity).

Option A (insurance) does not address behavioural adoption; it might transfer financial impact in some scenarios but won’t make managers change. Option C explicitly avoids change and therefore cannot mitigate the stated risk. Option B could work in extreme cases, but replacing the entire management team is a far more disruptive and costly response than necessary and is not the “most likely” effective countermeasure when the risk is capability/behaviour adoption. Therefore, training and educating the managers is the most appropriate countermeasure.

The documentation is explicit about how BAMs should be used when multiple stakeholder perspectives exist. It states that initially there will be one BAM for each distinct perspective, and later these models are examined to identify where there is agreement or conflict. The ultimate aim is to combine them and, through discussion with stakeholders, achieve a consensus BAM.

This is important because different stakeholders can hold different (yet valid) “world views” about the same organisation—what the book describes as “duck-rabbit” perspectives—so the analyst must understand and reconcile them to avoid building change based on a single partial view. Once the separate BAMs exist (Finance, Marketing, Logistics, Stores), the next logical step is therefore to facilitate negotiation and collaboration to create one agreed model that represents the idealised way forward and that stakeholders will “buy in” to.

Option A is unnecessary at this point because CATWOE is used to help derive activities and perspectives; the BAMs already exist. Option C (asking the Managing Director to pick) is specifically described as a fallback only if stakeholders cannot agree; it is less desirable than securing shared agreement because it risks lack of acceptance and weaker commitment to the final model.

The Business Change Lifecycle in the documentation comprises five stages (shown in the lifecycle figure and described as the “key areas of activity” needed for successful business change). Business case work is not confined to a single moment; instead, it is revisited through the change effort at multiple decision points. The guidance illustrates this with “decision gates” where the business case is: produced initially, then confirmed after detailed requirements, confirmed once development costs are estimated, revisited before deployment, and later used to check benefits realisation once the new processes/systems are operating.

That pattern means business-case-related activity normally touches every stage of the lifecycle. Early on (Alignment and Definition), the business case is shaped and refined as understanding of problems, scope, and requirements improves. During Design and Implementation, the business case is validated and updated as costs, feasibility, and delivery plans become clearer and as the organisation prepares for change. In Realisation, the business case is used as the baseline for benefits review and to identify follow-up actions where benefits are not yet achieved. Therefore, “5” is the best answer.