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

Design Thinking is an approach for solving complex problems by focusing on human needs and desires. It involves five stages: empathise, define, ideate, prototype and test. Therefore, options B, D and E are correct answers, as they suggest good techniques to help with the different stages of Design Thinking. Empathise is the stage where the problem is explored from the perspective of the users and their emotions, motivations and pain points are understood. A good technique to help with this stage is Customer Journey Map, which is a visual representation of the steps and emotions that a user goes through when interacting with a product or service. It helps to identify the pain points and opportunities for improvement in the user experience. Create is the stage where the users are represented by creating personas, which are fictional characters that embody the characteristics, goals and needs of a typical user group. Personas help to empathise with the users and design solutions that suit their preferences and expectations. Define is the stage where the problem is clearly defined and articulated based on the insights gained from the empathise stage. A good technique to help with this stage is Current user needs or problems, which is a statement that summarises what the users need or want to achieve and what prevents them from doing so. It helps to focus on the core problem and set the direction for ideation. Option A is not a correct answer, as Prototype is not a stage of Design Thinking, but a technique that can be used in the Prototype stage. Prototype is the stage where the ideas are turned into tangible and testable prototypes that can be used to demonstrate and evaluate the solutions. A good technique to help with this stage is Scenario Analysis, which is a technique that explores how different scenarios or situations could affect the outcomes of the solutions. It helps to test the feasibility and desirability of the prototypes. Option C is not a correct answer, as Evaluate is not a stage of Design Thinking, but a technique that can be used in the Test stage. Test is the stage where the prototypes are tested with real users and feedback is collected and analysed to refine and improve the solutions. A good technique to help with this stage is Mind Mapping, which is a technique that organises and visualises information in a hierarchical and associative way. It helps to capture and structure feedback and identify patterns and insights.

The business case guidance states that risk assessment should identify principal risks and—critically—define countermeasures: what can be done to reduce the likelihood of the risk occurring or lessen its impact. It notes that some risks can be transferred (e.g., via insurance), but the key is choosing countermeasures that actually address the cause.

Here, the risk is behavioural: managers may struggle to adopt a new management style required by the change. The book explicitly recognises that business change often requires changes to working practices and sometimes management style, especially where roles and authority shift. The most direct countermeasure is to build capability and readiness in the affected managers—through training, education, coaching, and support—so they understand the new behaviours, can practise them, and can be reinforced through agreed expectations. This reduces both the probability of failure (managers not changing) and the impact (inconsistent adoption harming productivity).

Option A (insurance) does not address behavioural adoption; it might transfer financial impact in some scenarios but won’t make managers change. Option C explicitly avoids change and therefore cannot mitigate the stated risk. Option B could work in extreme cases, but replacing the entire management team is a far more disruptive and costly response than necessary and is not the “most likely” effective countermeasure when the risk is capability/behaviour adoption. Therefore, training and educating the managers is the most appropriate countermeasure.

 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.