Free BCS Foundation Certificate in Business Analysis V4.1 PC-BA-FBA-20 Exam Questions

The RACI chart is a technique used to clarify and document the roles and responsibilities for activities, tasks, or deliverables within a project or business process. It is an acronym that defines the four key types of involvement:

Responsible: The person or team who does the work to complete the task.

Accountable: The person who is ultimately answerable for the correct and thorough completion of the deliverable or task, and who approves the work. Only one person can be Accountable.

Consulted: The people whose opinions are sought, and with whom there is two-way communication.

Informed: The people who are kept up-to-date on progress, often only at the completion of the task or deliverable, and with whom there is only one-way communication.

The correct categories are therefore Responsible, Accountable, Consulted, Informed.

(Reference: BCS Business Analysis Practice -- Stakeholder Management, RACI Matrix)

A mission statement defines the organization's purpose and primary objectives, often focusing on what the organization does and how it operates in the present. In contrast, a vision statement outlines the long-term aspirations of the organization---what it aims to become in the future. The mission provided---'To meet or undercut all our competitors' prices'---is focused on price competitiveness, which is a tactical approach rather than a strategic aspiration.

Let's analyze each option:

A . To offer the best value office fitting service: While this aligns somewhat with the mission, it is more of a value proposition or operational goal rather than a visionary statement. It lacks the aspirational and long-term focus that defines a vision.

B . To reduce the cost of office fitting by 5%: This is a specific, measurable objective, but it is too narrow and tactical to qualify as a vision. Visions are broader and not tied to specific metrics.

C . To increase the company's market share: Increasing market share is a strategic goal, but it is still an intermediate step toward achieving something greater. It does not capture the overarching ambition of the company.

D . To be the premier office fitting company: This option reflects a long-term aspiration and aligns with the characteristics of a vision statement. It expresses the desire to achieve leadership and excellence in the industry, which is consistent with the mission of being competitive on price while aiming for a higher status.

According to the BCS Business Analysis Framework , a vision statement should inspire and guide the organization toward its ultimate goal. Therefore, D is the most appropriate choice.

The power/interest grid helps determine the appropriate stakeholder engagement strategy. Stakeholders with high power and high interest need constant active management because they can strongly influence the change and care about the outcome. Stakeholders with high power but low interest should usually be kept satisfied or kept onside. Stakeholders with low power and low interest are normally watched or monitored with minimal effort. ''Keep informed'' applies to stakeholders with low power but high interest. These stakeholders care about the change and may be affected by it, but they do not have strong authority or influence over decisions. They should receive clear communication, updates, and opportunities to understand progress. Therefore, low power/influence and high interest is the correct combination.

In Agile, the Product Backlog is an ordered list of work that may be needed to improve or deliver the product. It normally contains user stories, features, defects, technical work, and other backlog items. It is prioritised so that the highest-value or most urgent items are considered first. It also contains work that may be selected for future sprints. However, once items are selected for the current sprint, they become part of the Sprint Backlog, which is the development team's plan for the sprint. Therefore, the Product Backlog does not specifically represent what the team is working on in the current sprint. That is the purpose of the Sprint Backlog. Option C is therefore the statement that is not true.

A Requirements Catalogue (or Requirements Specification) serves as the central repository for all documented requirements for a solution. BCS guidance categorises requirements hierarchically. At the highest level are the Business Requirements (often called General Requirements (c) and Technical Requirements (d)). These constrain the lower-level Solution Requirements, which consist of Functional Requirements (a) (what the system must do) and Non-functional Requirements (b) (quality attributes like performance, security, and usability). Since the catalogue aims to provide a complete picture of the business need and the proposed solution's capabilities, it must contain all four categories: Functional, Non-functional, General (Business), and Technical requirements.

(Reference: BCS Requirements Engineering -- Requirements Categorisation and Documentation)

To identify the generic business improvement strategy that involves eliminating redundant tasks, we need to analyze each option:

Key Considerations:

Change task sequence: This strategy involves reordering tasks to improve efficiency but does not necessarily eliminate redundancy.

Simplification: This strategy focuses on streamlining processes by removing unnecessary or redundant tasks, making workflows more efficient.

Redefine boundary: This strategy involves changing the scope or boundaries of a process, which may or may not involve eliminating redundant tasks.

Bottleneck removal: This strategy targets specific constraints or bottlenecks in a process but does not focus on eliminating redundant tasks.

Evaluation of Each Option:

A . Change task sequence: Changing the order of tasks does not inherently eliminate redundancy. Conclusion: This is not correct .

B . Simplification: Simplification directly involves identifying and removing redundant or unnecessary tasks to streamline processes. Conclusion: This is correct .

C . Redefine boundary: Redefining boundaries changes the scope of a process but does not specifically target redundancy. Conclusion: This is not correct .

D . Bottleneck removal: Removing bottlenecks addresses constraints but does not focus on eliminating redundant tasks. Conclusion: This is not correct .

The Business Analysis Service Framework (BASF) identifies core and auxiliary services that support business analysis activities. Auxiliary services supplement the core services and are essential for delivering value.

Key Considerations:

Strategic Analysis: Focuses on high-level organizational goals and strategies but is not an auxiliary service.

Stakeholder Engagement: Involves identifying, analyzing, and collaborating with stakeholders, which supports all aspects of business analysis.

Project Management: While important, project management is a separate discipline and not part of the BASF.

External Environment Analysis: Examines external factors (e.g., market trends) but is not an auxiliary service.

Evaluation of Each Option:

A . Strategic analysis: Strategic analysis is a core service, not an auxiliary service. Conclusion: This is not correct .

B . Stakeholder engagement: Stakeholder engagement is an auxiliary service that supports all business analysis activities by ensuring stakeholder needs are understood and addressed. Conclusion: This is correct .

C . Project management: Project management is outside the scope of the BASF. Conclusion: This is not correct .

D . External environment analysis: External environment analysis is a core service, not an auxiliary service. Conclusion: This is not correct .

The Business Readiness Assessment is a key activity conducted during the Implementation or Business Change Deployment stage of the project. Its primary purpose is to determine whether the target business areas, including the People, Organisation, and Processes, are sufficiently prepared to accept the business change and begin operating the new solution in the 'To Be' state. This involves checking factors such as whether staff have been trained, new processes are documented, communication has been effective, and necessary resources are in place. This assessment informs the 'Go/No Go' decision for the system's launch, ensuring a smooth transition to the new way of working.

(Reference: BCS Business Analysis Practice -- Business Change Deployment, Business Readiness)

A process model is a visual representation of a business process or workflow, showing how activities are performed and how they relate to one another. It is commonly used in business analysis to understand, analyze, and improve processes.

Key Characteristics of a Process Model:

Graphical Representation: Process models visually depict workflows and subprocesses, making them easier to understand.

Cost Differences: Cost analysis is not the primary purpose of a process model.

Job Descriptions: Process models focus on workflows, not individual job roles.

Software Features: Informal descriptions of software features are unrelated to process modeling.

Evaluation of Each Option:

A. A graphical representation of a business process or workflow and its related sub-processes: This accurately describes the purpose and nature of a process model. Conclusion: This is correct .

B. The cost differences between how a customer currently does something and how they would like to do something: Cost differences are analyzed separately and are not part of process modeling. Conclusion: This is not correct .

C. The detailed job description of the work to be performed by an individual: Job descriptions are documented separately and are not part of process modeling. Conclusion: This is not correct .

D. An informal, detailed, description of a software system feature derived from an end user's perspective: This describes user stories or feature descriptions, not process models. Conclusion: This is not correct .

The MoSCoW prioritization technique categorises requirements based on their importance to the current timebox or delivery. The categories are defined as follows:

MUST Have: Non-negotiable; essential for the solution to be viable. If missed, the project fails.

SHOULD Have: Important but not vital; the solution is still viable if these are deferred, but it will be a loss or require a workaround.

COULD Have: Desirable; can be deferred until the next timebox, with a minor impact on value.

WON'T Have this time (or WANT): Agreed not to be delivered now.

The description 'essential but which may be deferred in the short term' aligns perfectly with SHOULD Have. This category implies high importance, but the risk of non-delivery is managed through a temporary workaround, making them the first requirements considered for deferral if the schedule is threatened.

(Reference: BCS Requirements Engineering -- Prioritisation Techniques, MoSCoW)