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

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.

A stakeholder management strategy is a plan for engaging and communicating with stakeholders based on their level of power and interest in an organisation or project. It helps to ensure that stakeholders are appropriately involved and informed throughout the organisation’s or project’s lifecycle. Therefore, option A is the correct answer, as keep satisfied is the further strategy that is required for one of the three stakeholders in this scenario. Keep satisfied is the strategy for managing stakeholders who have high power but low interest in an organisation or project. It involves meeting their needs and expectations without over-communicating or over-involving them. The stakeholder who requires this strategy in this scenario is the financial accountant assigned to the project to monitor the financial benefits of the new system. This stakeholder has high power, as he is essential to the project and can influence its outcome. However, he has low interest, as he is not interested in the detail of the project. Option B is not a correct answer, as watch is not the further strategy that is required for any of the three stakeholders in this scenario. Watch is the strategy for managing stakeholders who have low power and low interest in an organisation or project. It involves monitoring their behaviour and attitude without engaging or communicating with them too much. None of the stakeholders in this scenario have low power and low interest, as they are all involved or affected by the project in some way. Option C is not a correct answer, as ignore is not a valid strategy for managing any stakeholder in an organisation or project. Ignore is the strategy of disregarding or neglecting stakeholders who have no power or interest in an organisation or project. It involves excluding them from any engagement or communication activities. This strategy is not advisable, as it may lead to stakeholder dissatisfaction, resentment or resistance. Option D is not a correct answer, as keep informed is not the further strategy that is required for any of the three stakeholders in this scenario. Keep informed is the strategy for managing stakeholders who have low power but high interest in an organisation or project. It involves providing them with regular and sufficient information and updates without overloading them with details. None of the stakeholders in this scenario have low power but high interest, as they are all involved or affected by the project in some way.

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.