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

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.

 A stakeholder management strategy is a plan for how to engage and communicate with stakeholders based on their level of interest and influence in the organisation or project. A stakeholder management strategy can vary depending on the stakeholder’s position on the power/interest grid, which has four quadrants: high power, high interest; high power, low interest; low power, high interest; and low power, low interest. Therefore, option C is the correct answer, as it represents appropriate stakeholder management strategies for Harvey based on his position on the grid before and after his role change. Watch means to monitor the stakeholder’s level of interest and influence and keep them informed of relevant developments. This is suitable for when Harvey was in the low power, low interest quadrant, as he had little authority or concern over the project. Constant active management means to involve the stakeholder closely in the project and seek their input and feedback regularly. This is suitable for when Harvey moved to the high power, high interest quadrant, as he became the sponsor and owner of the project. Option A is not a correct answer, as keep informed means to provide the stakeholder with sufficient information and updates to maintain their interest and support. This is more suitable for when Harvey was in the low power, high interest quadrant, not the low power, low interest quadrant. Option B is not a correct answer, as ignore means to disregard the stakeholder’s views and needs and exclude them from communication. This is not a good strategy for any stakeholder, especially one who has some power or influence over the project. Option D is not a correct answer, as constant active management means to involve the stakeholder closely in the project and seek their input and feedback regularly. This is more suitable for when Harvey was in the high power, high interest quadrant, not the low power, low interest quadrant.

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.