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

A competency is a combination of skills, knowledge and behaviours that enable a person to perform a task or role effectively and efficiently. Therefore, option D is the correct answer, as it describes the competencies required for this role based on the job advert. Business case development is a competency that involves creating and presenting a formal written proposal that details the costs and benefits of a proposed business change or solution. It helps to justify and secure the approval and funding for a proposed business change or solution. This competency is required for this role, as the job advert states that the business analyst will assist in the development of formal written proposals detailing the cost and benefit of proposed business initiatives. Investigation techniques is a competency that involves using a variety of methods to explore and define complex situations or problems within an organisation or project. It helps to elicit, analyse, validate and prioritise the views and needs of stakeholders and identify the root causes and effects of situations or problems. This competency is required for this role, as the job advert states that the business analyst should be able to use a variety of methods to explore and define complex situations. Business architecture is a competency that involves designing and modelling the structure and relationships of an organisation or project at a high level of abstraction. It helps to understand how an organisation or project operates, delivers value and achieves its objectives and outcomes. This competency is required for this role, as the job advert states that the business analyst should have experience of producing blueprints in terms of processes, management structures, culture and people. Option A is not a correct answer, as it does not describe all the competencies required for this role based on the job advert. Subject matter expertise is a competency that involves having in-depth knowledge and understanding of a specific domain or industry within an organisation or project. It helps to provide insights and guidance on the best practices and standards within a specific domain or industry. This competency is not required for this role, as the job advert does not state that the business analyst should have subject matter expertise in any specific domain or industry. Option B is not a correct answer, as it does not describe all the competencies required for this role based on the job advert. Domain knowledge is a competency that involves having general knowledge and understanding of a broad domain or industry within an organisation or project. It helps to provide context and background on the nature and scope of a domain or industry. This competency is not required for this role, as the job advert does not state that the business analyst should have domain knowledge in any broad domain or industry. Gap analysis is a competency that involves comparing current and desired situations or problems and identifying the differences or gaps between them. It helps to determine what changes or improvements are needed to bridge the gaps and achieve desired situations or problems. This competency is not required for this role, as the job advert does not state that the business analyst should have experience of gap analysis. Option C is not a correct answer, as it does not describe all the competencies required for this role based on the job advert. Requirements engineering is a competency that involves eliciting, analysing, specifying, validating and managing requirements for a system or product within an organisation or project. It helps to ensure that requirements are clear, complete, consistent, testable and traceable throughout the system or product lifecycle. This competency is not required for this role, as the job advert does not state that the business analyst should have experience of requirements engineering.

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 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.