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 consensus BAM is a conceptual model that depicts the agreed view of what the organisation does or should do. It shows the high-level activities and the logical dependencies between them. By comparing the consensus BAM with the current situation, a gap analysis can identify where the organisation is not performing as desired or where there are opportunities for improvement. Therefore, option A is the correct answer.

The guidance on prior research for business analysis work states that analysts should first study relevant background material to gain an “entry point” into the domain before undertaking deeper investigation. For projects focused on specific processes (such as re-engineering a customer-facing process with excessive handoffs), the documentation explicitly recommends studying procedure manuals and current system documentation to understand what the process is supposed to be and how it is documented. It also recommends studying the organisation chart to understand reporting lines, functional groupings, and where responsibilities and handoffs may occur—particularly important here because the goal is to reduce handoffs and support remote working practices.

Financial statements and annual reports can be useful for strategic or corporate-level analysis, but the scenario is operational and process-focused (re-engineering a process linked to declining customer satisfaction). The most direct “initial analysis” sources, aligned with the prescribed prior-research approach for process-oriented work, are therefore procedure manuals/documentation and organisation charts.

Crucially, the guidance cautions that documentation may become out of date and can reflect “what we thought it ought to have been,” so these sources support orientation and preparation, but they must be followed by proper investigation techniques (e.g., interviews, observation, workshops, and quantitative methods) to confirm what actually happens in practice.