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

A key performance indicator (KPI) is a measurable value that demonstrates how effectively an organisation is achieving a key business objective or critical success factor (CSF). A KPI should be relevant, specific, measurable, achievable, realistic and time-bound (SMART). Therefore, options C, D and E are appropriate KPIs for the CSF ‘provide excellent customer service’, as they measure aspects of customer satisfaction and loyalty that are directly related to the quality of service provided by the hotel chain. Option A is not an appropriate KPI, as it does not measure customer service, but rather customer consumption. Option B is not an appropriate KPI, as it does not measure customer service, but rather customer preference.

The stakeholder management strategy for senior managers should be constant active management. Senior managers have high power and high interest in the project, as they are responsible for overseeing its implementation and ensuring its alignment with organizational goals. They also have influence over other stakeholders, such as end users and employees. Therefore, they need to be regularly engaged, consulted, informed, and involved in decision making throughout the project lifecycle. Option B is the correct answer.

The bullet points describe taking candidate solutions and testing them, then collecting feedback to learn and decide what to do next. In design and change approaches, that is the essence of evaluation: trialling options (pilots) and assessing their suitability using stakeholder input and evidence.

The business analysis guidance places this kind of work in the “evaluate options / evaluate solution” part of the lifecycle: after a need is understood and options are generated, the next step is to assess them by considering feasibility, benefits, impacts, and risks, using structured stakeholder engagement such as workshops. Workshops are explicitly identified as an investigation technique used to gather and validate information collaboratively, which fits “workshops to capture feedback” from pilots.

Within a Double Diamond–style design process, developing multiple pilot solutions aligns with exploring the solution space, and then running pilots and gathering feedback aligns with converging by evaluating what works in practice and what should be refined, scaled, or discarded. That activity is best represented by Evaluate rather than Empathise (understanding users), Define (clarifying the problem), or Create (generating ideas without yet testing them).

Therefore, the stage present in the bullet points is Evaluate (Option C).

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.

A Business Activity Model (BAM) is a high-level view of the business activities that take place within an organisation. It shows how activities are related to each other and how they contribute to achieving business objectives. A BAM consists of five types of high-level activities: directing, enabling, doing, monitoring and controlling. A BAM can also show dependencies between activities using arrows to indicate which activity depends on another activity to start or finish. Therefore, option A is the correct answer, as it shows the dependencies between the four activities on the BAM correctly. Activity c (define lending policies) is a directing activity that sets the rules and guidelines for lending e-books to customers. It depends on no other activity and precedes all other activities. Activity b (establish licensing arrangements with publishers) is an enabling activity that secures the rights and permissions to lend e-books from different publishers. It depends on activity c and precedes activity a. Activity a (lend books) is a doing activity that provides e-books to customers according to their requests and preferences. It depends on activity b and precedes activity d. Activity d (monitor lending usage) is a monitoring activity that tracks and records how customers use and return e-books. It depends on activity a and follows all other activities.

To identify underlying causes, the analyst needs a technique that helps them explore what is happening in practice and uncover where breakdowns or inefficiencies might be occurring. The documentation describes scenario analysis as “telling the story of a task or transaction,” and explains it is useful when analysing or redesigning processes because it helps staff and analysts work through the steps required, visualise them clearly, and understand what triggers the work and what actions must be completed to achieve a successful outcome.

In a retail setting, declining sales can result from failures or friction in key customer-facing scenarios (e.g., browsing, ordering, returns, stock availability, customer service escalation). By building and walking through scenarios end-to-end, the analyst can pinpoint where delays, handoffs, rework, unclear decision points, or system constraints occur—each of which can contribute to poorer customer outcomes and, ultimately, sales decline. Scenario work also creates a concrete basis for validating hypotheses with stakeholders and for identifying what evidence and data should be gathered next.

The other options are less directly “cause-finding” for the stated problem. A customer journey map focuses on experience and touchpoints (useful, but it may not expose operational root causes in enough detail). Use case diagrams define system interactions for requirements, not root cause diagnosis. A business activity model gives a conceptual “what activities exist” overview; it is valuable for gaps, but scenario analysis is the technique explicitly positioned to walk through transactions to reveal where problems arise.

A time based event is one that occurs at a regular or predetermined interval, such as monthly or quarterly. In this scenario, the printing of the monthly payslips is a time based event, as it happens every month. The notification from senior management is not an external or internal event, as it is not triggered by an external or internal stakeholder or situation. Therefore, option D is the correct answer.

The documentation describes the power/interest grid as a technique for analysing stakeholders, then using the analysis to plan management actions. It states that it is important to plot stakeholders where they actually are (not where you would like them to be), and then to explore strategies for managing them in their current positions or for moving them to more advantageous positions. It also emphasises that stakeholder analysis must be a continuing activity throughout the project, with the team watching for changes and re-evaluating strategies accordingly—this supports regular review of the grid.

Where option D differs is that it describes implementation of engagement strateggement actions is part of stakeholder management execution, which follows from the analysis rather than being a step “in conducting the analysis” itself. The text makes this separation clear: after plotting positions, up for managing stakeholders and the approach to take; the subsequent engagement is what the team then does based on that plan.

So A and B are explicitly in the technique guidance, and C aligns with the “continuing activity” requirement. D is the step that moves beyond the analysis activity into carrying out the management actions, making it the best choice for “not typically involved in conducting the analysis.” ION NO: 65

A business case has been developed for the introduction of a new customer service platform. In the “Impact Assessment” section, which key factor should the business analyst highlight to communicate the potential organisational changes resulting from the platform’s implementation?iomer service efficiency and employee workflow.

B. Discuss the usability of the recommended application and software requirements.

C. Review potential vendors including past experience in the industry and their financial stability.

D. Detail the operating system and solution architecture of the new platform.

Answer: A

The business case “Impact assessment” section is used to explain what will happen to the organisation if the proposed option is adopted—not just the financial costs and benefits. The documentation states that, in addition to costs and benefits, the business case should explore organisational impacts, some of which may have costs attached and some of which are simply consequences of change. It gives concrete examples such as changes to organisation structure (e.g., reorganising departments, creating new roles like a single customer point of contact, or moving from specialist to generalist roles) and the effects on interdepartmental relationships and working patterns.

Option A best mause “customer service efficiency and employee workflow” directly communicates the operational and people/process impacts that typically accompany a new customer service platform—how work will be performed, how staff will interact, and what the service outcomes may be. This is exactly the kihange decision-makers need surfaced in an impact assessment so they can plan mitigation and change management (e.g., handling disruption, new responsibilities, revised collaboration).

Options B and D focus on technical solution detail, and C focuses on vendor evaluation—none of these are the core purpose of an “impact assessment” section as defined in the business case guidance.