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.

The statement commits to two outcomes: good quality accommodation and repairs addressed in a timely manner. The documentation emphasises that performance targets and measures must be chosen carefully and should reflect not only internal views but also customer expectations; otherwise performance may look “fine” internally while failing customers. It also stresses that KPIs/targets should be SMART and monitored regularly.

Option A provides a clear, measurable proxy for property condition: if emergency repairs are needed in a high proportion of properties, that indicates poor underlying condition and reactive maintenance. Setting a target like “no more than 5%” directly measures progress toward “good quality accommodation.”

Option C translates tenant experience into a clear target: limiting complaints about condition/repairs to a defined maximum per month is specific and measurable, and it reflects the customer perspective that the press statement is trying to reassure.

Option B is a valid measure but it is not defined as a target (it has no threshold), so it is less aligned to the question asking for “targets to measure performance against.” Option D measures media coverage, which is indirect and can be influenced by factors outside operational performance; it is not a reliable operational KPI for accommodation quality or repair timeliness. Therefore, A and C are the best targets.

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.