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

The business analysis guidance makes it clear that a business case is not a “one-and-done” document that stops being useful at implementation. Instead, it is revisited at multiple decision gates through the lifecycle, including points after development estimates are known, before deployment, and later during operation when benefits realisation is checked. This directly contradicts statement A, because the business case remains relevant beyond implementation to confirm assumptions and verify whether expected benefits were actually achieved.

Statement B is also incorrect. The guidance explicitly states that the “do nothing / maintain the status quo” option should always be considered and will usually appear in the business case. It may sometimes be rejected due to unacceptable consequences, but it should still be included so decision-makers understand the risks of inaction.

Statement C is correct because the business case should consider both tangible and intangible benefits. The documentation explains that many benefits (for example improved customer satisfaction or staff morale) can be intangible, meaning they cannot be credibly valued in advance. While organisations vary in how they treat intangibles, the framework recognises them as legitimate benefits (with the caution not to overstate them or assign “spurious” values).

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 documentation defines gap analysis as exploring the differences between a current state (“as is”) and a desired future state (“to be”). The emphasis is on understanding where the organisation wants to be and, by comparing with the current situation, identifying what needs to change to reach that target state. It also states that the outcome of gap analysis is a list of business requirements to be delivered—typically phrased at the “what” level rather than prescribing detailed solutions.

In this scenario, the retailer’s desired future state includes a more capable online experience and integration with inventory and other applications—this is fundamentally a change in capability. Therefore, identifying new and improved business capabilities (and capturing them in a target view such as a Target Operating Model) is exactly the kind of work performed in gap analysis: it clarifies what the future business system must be able to do, so gaps against the current capabilities can be identified and addressed.

By contrast, a Gantt chart (A/B) is delivery planning, not gap analysis; a RACI matrix (C) is a responsibilities definition; and brainstorming (D) is an idea-generation technique that may help option creation but is not the core “compare as-is to to-be and identify gaps” activity.