Free BCS PC-BA-FBA-20 Practice Exam with Questions & Answers

To determine which measures are appropriate Key Performance Indicators (KPIs) for the Critical Success Factor (CSF) " provide excellent customer service, " we must first understand the relationship between CSFs and KPIs:

Critical Success Factors (CSFs): These are the essential areas or activities that an organization must excel at to achieve its goals. In this case, " provide excellent customer service " is a CSF.

Key Performance Indicators (KPIs): These are measurable metrics used to evaluate progress toward achieving a CSF. KPIs should directly align with the CSF and provide actionable insights.

Now, let’s evaluate each option to determine whether it is an appropriate KPI for the CSF " provide excellent customer service " :

A. The number of customers who make use of their in-room mini bar

This measure tracks customer behavior related to a specific hotel amenity (the mini bar). While it may indicate customer satisfaction with the room ' s offerings, it does not directly measure the quality of customer service.

Conclusion: This is not an appropriate KPI for the CSF " provide excellent customer service. "

B. The percentage of customers who use the leisure facilities

This measure tracks how many customers utilize the hotel ' s leisure facilities (e.g., gym, pool, spa). While it may reflect customer engagement with the hotel ' s amenities, it does not directly assess the quality of customer service.

Conclusion: This is not an appropriate KPI for the CSF " provide excellent customer service. "

C. The number of customers who complain

Customer complaints are a direct indicator of dissatisfaction and can highlight areas where customer service needs improvement. A high number of complaints suggests poor customer service, while a low number indicates better service quality.

This measure is closely aligned with the CSF " provide excellent customer service " because it provides actionable feedback on service performance.

Conclusion: This is an appropriate KPI for the CSF.

D. The percentage of customers who join the hotel loyalty scheme

Customers are more likely to join a loyalty scheme if they have had a positive experience with the hotel, including excellent customer service. This measure reflects customer satisfaction and loyalty, which are outcomes of good service.

Conclusion: This is an appropriate KPI for the CSF.

E. The percentage of customers who return

Repeat customers are a strong indicator of customer satisfaction and loyalty, which are directly influenced by the quality of customer service. If customers return to the hotel, it suggests they were satisfied with their previous experience, including the service they received.

Conclusion: This is an appropriate KPI for the CSF.

The investigation technique best suited to achieve these outcomes is the Interview. A one-on-one interview provides a private and focused setting, which is essential for discussing confidential or politically sensitive issues that a stakeholder would not be comfortable raising in a group or on a written questionnaire. The personal interaction during an interview is the most effective way to build rapport with the stakeholder, leading to more open and honest communication. This deeper level of trust and detailed conversation is what allows the analyst to gain a richer appreciation of the political and cultural landscape of the business. Special purpose records, document analysis, and questionnaires are more impersonal and cannot provide the same level of qualitative insight or trust.

(Reference: BCS Foundation Certificate in Business Analysis / BCS Business Analysis Practice – Investigative Techniques, Interviews)

Actor-task level analysis looks at detailed work performed by specific actors, roles, or users. At this level, a task can be broken into smaller steps, inputs and outputs can be identified, and performance measures can be applied to assess efficiency, quality, or timeliness. Therefore, options B, C, and D are valid statements about actor-task analysis. Value chain analysis, however, is not used at this detailed actor-task level. It is an enterprise-level technique used to understand how organisational activities create value for customers. It examines primary and support activities across the business, not the detailed steps performed by a particular actor. Because value chain analysis belongs at a higher level of business process analysis, option A is the false statement.

The digital business analyst role focuses on leveraging technology to drive innovation and transformation. This variant of the business analyst role requires creative thinking, adaptability to rapid change, and the ability to exploit emerging technologies.

Key Characteristics of Business Analyst Roles:

Enterprise Business Analyst: Focuses on aligning business strategies and objectives across the organization.

Digital Business Analyst: Emphasizes innovation, digital transformation, and the adoption of emerging technologies.

Project Business Analyst: Works within project teams to define and deliver specific solutions.

Test Business Analyst: Specializes in ensuring requirements are met through testing and quality assurance.

Evaluation of Each Option:

A. Enterprise business analyst: While enterprise BAs focus on strategic alignment, they do not specifically emphasize innovation or emerging technologies. Conclusion: This is not correct .

B. Digital business analyst: This role explicitly involves thinking innovatively, embracing change, and leveraging emerging technologies. Conclusion: This is correct .

C. Project business analyst: Project BAs focus on delivering specific solutions rather than driving innovation or digital transformation. Conclusion: This is not correct .

D. Test business analyst: Test BAs focus on validation and quality assurance, not innovation or technology adoption. Conclusion: This is not correct .

Final Recommendation:

The variant of the business analyst role that needs to think innovatively and embrace change is:

B. Digital business analyst.

Traceability links requirements to other project artefacts. There are two main types: horizontal and vertical. Horizontal traceability (Option A) links a requirement forward to its design, code, and test cases, and backward to its source (Option D), tracing its lifecycle from inception to delivery. Vertical traceability concerns tracing a requirement up or down the requirements hierarchy (C). This ensures that lower-level requirements (e.g., functional) are aligned with and fully support the higher-level business objectives, policies, and strategy. For example, it traces a solution requirement up to the business requirement it satisfies, validating that every low-level detail is necessary and justified by a high-level business need.

(Reference: BCS Requirements Engineering – Requirements Traceability)

The Iterative (or Agile) lifecycle model is specifically designed to deal with changing requirements and a rapid pace of change. Unlike linear models like Waterfall or the V model, which expect requirements to be fixed early, the iterative model delivers the solution in a series of repeated cycles (iterations/sprints). This approach embraces the reality that requirements will change as stakeholders learn more about the evolving product and the business environment shifts. It explicitly incorporates frequent feedback loops and allows for the adaptation of requirements throughout the project, making it the most flexible and suitable model for unstable or complex environments.

(Reference: BCS Requirements Engineering – Lifecycle Models, Agile/Iterative)

The power/interest grid is a tool used in stakeholder analysis to categorize stakeholders based on their level of power (influence) and interest in the project. The position of stakeholders on the grid reflects their current status.

Key Considerations:

Where the Stakeholders Will Be After the Proposed Change: The grid represents the current state, not future projections.

Where the Stakeholders Should Be: The grid does not prescribe ideal positions but reflects actual positions.

Where the Stakeholders Actually Are at a Point in Time: The grid is a snapshot of stakeholders ' current power and interest levels.

Where the Stakeholders Believe They Should Be: The grid is based on objective analysis, not subjective beliefs.

Evaluation of Each Option:

A. Where the stakeholders will be after the proposed change: The grid reflects the present, not future states. Conclusion: This is not correct .

B. Where the stakeholders should be: The grid does not prescribe ideal positions but reflects actual positions. Conclusion: This is not correct .

C. Where the stakeholders actually are at a point in time: This accurately describes the purpose of the power/interest grid. Conclusion: This is correct .

D. Where the stakeholders believe they should be: The grid is based on objective analysis, not subjective beliefs. Conclusion: This is not correct .

Final Recommendation:

The position of stakeholders on a power/interest grid represents:

C. Where the stakeholders actually are at a point in time.

Prototyping is a technique used to create a working model of a system or product to validate requirements and gather feedback. Let’s evaluate each statement to determine which are false :

Evaluation of Each Statement:

A. Suitable for waterfall requirements elicitation: Prototyping is generally not suitable for traditional waterfall methodologies because waterfall follows a linear, sequential approach where requirements are defined upfront before development begins. Prototyping, on the other hand, involves iterative feedback loops, which are more aligned with Agile methodologies. Conclusion: This statement is false .

B. Allows an analyst to confirm their understanding of requirements: Prototyping enables analysts to validate their understanding of requirements by creating a tangible representation of the system for stakeholders to review and provide feedback. Conclusion: This statement is true .

C. Only suitable for Agile project environments: While prototyping is commonly used in Agile environments due to its iterative nature, it is not limited to Agile. Prototyping can also be used in hybrid or iterative waterfall projects to clarify requirements and reduce ambiguity. Conclusion: This statement is false .

D. Enables the elicitation of usability requirements: Prototyping is particularly effective for gathering usability requirements because it allows stakeholders to interact with a mock-up or early version of the system, providing insights into user experience and interface design. Conclusion: This statement is true .

The T-shaped professional model is used in business analysis to describe the ideal mix of skills and knowledge. The ' T ' shape consists of a vertical bar and a horizontal bar. The vertical bar represents the deep and specific domain knowledge or core expertise (e.g., business analysis techniques, specific industry knowledge). The horizontal bar (the top of the ' T ' ) represents the multi-disciplinary breadth of skill and knowledge that an individual can apply to various situations. This breadth includes soft skills like communication, facilitation, leadership, and a broad understanding of different business areas (like finance, operations, IT, and strategy). It is this breadth that allows the business analyst to collaborate effectively across different teams and disciplines, understand the context of the change, and recommend truly holistic solutions.

(Reference: BCS Foundation Certificate in Business Analysis / BCS Business Analysis Practice – Competencies of a Business Analyst)

To determine the best way to present the changes to the scheduling team, we need to consider the nature of the information being communicated and the audience (the scheduling team). The extract describes changes to processes, roles, and systems, which are best represented visually to ensure clarity and understanding.

Key Considerations:

Business Process Model (BPM): A BPM is a visual representation of the steps in a process. It is particularly useful for communicating changes to workflows, roles, and responsibilities. Since the extract discusses splitting the scheduling team into two groups and introducing new software and processes, a BPM would effectively illustrate how these changes impact the workflow.

Business Activity Model (BAM): A BAM focuses on high-level activities and their logical dependencies, often used in strategic planning. However, it is less detailed than a BPM and may not adequately capture the specific changes to scheduling processes.

POPIT (People, Organization, Process, Information, Technology): POPIT is a framework for analyzing business change across multiple dimensions. While it provides a holistic view, it is not a presentation tool and would not be the best choice for directly communicating the changes to the scheduling team.

Prototype: A prototype is typically used to demonstrate the functionality of a system or software. While the introduction of telephony software and an online booking system could involve prototyping, this option does not address the need to communicate process and role changes.

Evaluation of Each Option:

A. Business Process Model: A BPM is ideal for illustrating the changes to the scheduling process, including the split into inpatient and outpatient teams and the integration of new software. It provides a clear, step-by-step visual representation that the scheduling team can easily understand. Conclusion: This is the best option .

B. Business Activity Model: While a BAM could provide a high-level overview of the changes, it lacks the detail needed to explain specific process adjustments. Conclusion: This is not the best option .

C. POPIT: POPIT is a framework for analysis, not a communication tool. It would not effectively convey the changes to the scheduling team. Conclusion: This is not the best option .

D. Prototype: Prototyping is relevant for demonstrating software functionality but does not address the need to communicate process and role changes. Conclusion: This is not the best option .

Final Recommendation:

The changes should be presented using a Business Process Model , as it effectively communicates the revised workflows and roles to the scheduling team.