Pass the BCS Business Analysis PC-BA-FBA-20 Questions and answers with CertsForce

The Waterfall methodology is a linear approach where requirements are defined upfront, and changes are difficult to accommodate once the project begins. Agile methodology , on the other hand, emphasizes flexibility and adaptability to changing requirements.

Key Considerations:

Inherent Uncertainty in Cost: While cost uncertainty exists in both methodologies, Agile does not specifically address this drawback of Waterfall.

Inflexibility to Changing Requirements: Waterfall ' s rigid structure makes it difficult to incorporate changes once the project starts. Agile addresses this by allowing iterative development and continuous feedback.

Capturing All Requirements Upfront: Agile does not aim to capture all requirements upfront; instead, it embraces evolving requirements throughout the project.

Stakeholder Agreement on Scope Before Work Begins: Agile encourages ongoing collaboration with stakeholders rather than requiring scope agreement upfront.

Evaluation of Each Option:

A. The agile methodology addresses the inherent uncertainty in cost associated with waterfall: Agile does not specifically address cost uncertainty. Conclusion: This is not correct .

B. Agile development addresses the inflexibility of waterfall as it pertains to changing requirements: This is the primary drawback of Waterfall that Agile addresses through its iterative and flexible approach. Conclusion: This is correct .

C. The agile methodology captures all requirements at the start of a project to reduce risks typically experienced in waterfall: Agile does not capture all requirements upfront; it embraces evolving requirements. Conclusion: This is not correct .

D. Agile development requires stakeholders to agree to the scope of the project before the work begins, reducing uncertainty in the design: Agile does not require upfront scope agreement; it promotes adaptive planning. Conclusion: This is not correct .

Final Recommendation:

The drawback of Waterfall addressed in Agile is:

B. Agile development addresses the inflexibility of waterfall as it pertains to changing requirements.

When documenting risks in a business case, it is essential to follow structured processes to ensure risks are appropriately identified, analyzed, and managed. Let’s evaluate each option again based on best practices outlined in the BCS Business Analysis Framework and other methodologies:

Key Considerations:

Risk Documentation: Risks must be recorded systematically to ensure they are visible, actionable, and traceable.

Ownership of Risks: Assigning ownership ensures accountability and clarity about who is responsible for monitoring and mitigating each risk.

Risk Management Lifecycle: The process typically involves identification, documentation, assessment, ownership assignment, and response planning.

Evaluation of Each Option:

A. Create a RAID log

A RAID log (Risks, Assumptions, Issues, and Dependencies) is a widely used tool in business analysis and project management for capturing and managing risks systematically.

It provides a centralized repository for tracking risks, assumptions, issues, and dependencies, ensuring that risks are documented comprehensively and transparently.

This aligns with best practices for risk management and is a critical first step in ensuring risks are appropriately recorded.

Conclusion: This is a must-do action.

B. Document the source of each risk

While documenting the source of each risk can provide valuable context, it is not a mandatory or primary step in the initial documentation phase.

Sources of risks are often identified during risk analysis or root cause analysis, which occurs after risks have been recorded.

Although useful, this step is secondary to creating a RAID log and assigning ownership.

Conclusion: This is not the most critical action at this stage.

C. Identify an owner for each risk

Assigning ownership for each risk is a fundamental part of risk management. Without clear ownership, risks may remain unmonitored or unaddressed.

Ownership ensures accountability and helps streamline communication and decision-making regarding risk mitigation strategies.

According to the BCS Business Analysis Framework , identifying risk owners is a key responsibility during the risk documentation process.

Conclusion: This is a must-do action.

D. Provide justification for each countermeasure identified

Justifying countermeasures is part of the risk response planning phase, which occurs after risks have been documented, assessed, and prioritized.

At this stage, John’s focus should be on identifying and recording risks, not on evaluating or justifying solutions.

Conclusion: This is not relevant at the documentation stage.

E. Impact assessment of each countermeasure identified

Similar to option D, impact assessments for countermeasures are conducted during the risk response planning phase, not during the initial documentation phase.

This step is premature and does not align with the immediate need to document risks.

Conclusion: This is not relevant at the documentation stage.

Final Recommendation:

Based on the BCS Business Analysis Framework and industry best practices, the two most appropriate actions for John are:

Create a RAID log (to systematically document risks).

Identify an owner for each risk (to ensure accountability and clarity).

These steps ensure that risks are appropriately recorded and managed, laying the foundation for effective risk management.

A business analyst is responsible for understanding business needs, analysing problems, eliciting requirements, exploring options, and helping stakeholders define valuable change. Options A, B, and D are all normal business analysis responsibilities. The analyst investigates the business situation, identifies needs, supports option development, and uses elicitation techniques such as interviews, workshops, observation, and document analysis to understand requirements. Ensuring that projects are delivered within budget constraints is primarily a project management responsibility. A project manager controls project delivery, manages schedule, cost, resources, risks, and progress against the approved plan. The business analyst may contribute estimates or impact analysis, but they do not normally own budget delivery. Therefore, option C is least likely to be a business analyst responsibility.

Regulators are stakeholders who define, monitor, or enforce rules, standards, legislation, and compliance obligations that affect an organisation. In business analysis, regulators may influence what changes are possible, acceptable, or mandatory. For example, financial, data protection, safety, or industry regulators may require proposed changes to comply with legal or professional standards. Partners may collaborate with the organisation, but they do not normally enforce rules. Managers control internal resources and operations, but they are not the external rule-enforcing stakeholder category. Owners have financial or strategic interest in the organisation, but they do not normally monitor regulatory compliance unless they also hold a governance role. Since the question asks who monitors whether proposed changes fall within enforced rules, the correct stakeholder category is Regulators.

A customer journey is used to understand the experience from the customer’s point of view as they interact with an organisation, product, service, or process. It helps identify customer touchpoints, expectations, frustrations, emotions, and pain points across the end-to-end journey. Although customer journey analysis may later highlight process improvements, its most direct purpose is not internal process redesign. Value chain analysis is used to understand organisational activities that create value, not customer experience. Balancing employee and customer interactions may be a secondary consideration, but it is not the core purpose. The customer journey technique is especially useful in service improvement, digital transformation, and customer experience work because it exposes what the customer sees and feels, rather than only what the organisation’s internal process model shows.

Gap analysis identifies the differences between the current state and the desired future state. To ensure a holistic view, a comprehensive framework like POPIT™ (People, Organization, Process, Information, Technology) is useful.

Key Considerations:

Payback Analysis: Focuses on financial returns and does not provide a holistic view.

POPIT™: Analyzes gaps across multiple dimensions (people, organization, process, information, technology), ensuring a comprehensive perspective.

Boston Box: Evaluates market positioning of products or services, not gaps in organizational capabilities.

PESTLE: Analyzes external environmental factors but does not focus on internal gaps.

Evaluation of Each Option:

A. Payback analysis: Payback analysis focuses on financial metrics and does not address holistic gap analysis. Conclusion: This is not correct .

B. POPIT™: POPIT™ ensures a holistic view by analyzing gaps across people, organization, process, information, and technology. Conclusion: This is correct .

C. Boston box: The Boston box evaluates product portfolios, not organizational gaps. Conclusion: This is not correct .

D. PESTLE: PESTLE analyzes external factors and does not focus on internal gaps. Conclusion: This is not correct .

Final Recommendation:

The technique useful for ensuring a holistic view in gap analysis is:

B. POPIT™.

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.

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)

Agile requirements validation ensures that requirements are clear, feasible, and actionable before they are implemented in an iteration. This aligns with Agile principles of delivering value incrementally and avoiding waste.

Key Considerations:

Accurate Estimation for Sprint Planning: While estimation is important, it is not the primary purpose of requirements validation.

Correctness of Backlog Items: Ensuring correctness is part of validation but applies to all backlog items, not just those allocated to an iteration.

Testing Requirements: Testing occurs during or after development, not as part of validation.

Readiness for Development: Validation ensures that requirements are well-defined, understood, and feasible before they are developed.

Evaluation of Each Option:

A. To ensure estimation for sprint planning is accurate: Estimation accuracy is important but not the primary purpose of validation. Conclusion: This is not correct .

B. To ensure any requirements added to the backlog are correct: Correctness applies to all backlog items, not just those allocated to an iteration. Conclusion: This is not correct .

C. To ensure that requirements allocated to an iteration have been tested: Testing occurs after development, not during validation. Conclusion: This is not correct .

D. To ensure any requirements allocated to an iteration are ready to be developed: This is the primary purpose of Agile requirements validation—to ensure requirements are clear, actionable, and feasible before development begins. Conclusion: This is correct .

Final Recommendation:

The purpose of Agile requirements validation is:

D. To ensure any requirements allocated to an iteration are ready to be developed.

A RACI chart (Responsible, Accountable, Consulted, Informed) is a tool used to clarify roles and responsibilities in a project or process. Each role in the chart has a specific meaning:

Key Definitions:

Responsible: The person or role responsible for performing the task or completing the work.

Accountable: The person ultimately answerable for the task ' s completion and outcomes.

Consulted: Individuals or roles who provide input or expertise before decisions are made or tasks are completed.

Informed: Individuals or roles who need to be kept updated on progress or outcomes.

Evaluation of Each Option:

A. Responsible: The " Responsible " role is assigned to the person or team performing the task. Conclusion: This is correct .

B. Accountable: The " Accountable " role ensures the task is completed but does not necessarily perform the task. Conclusion: This is not correct .

C. Consulted: The " Consulted " role provides input or advice but does not perform the task. Conclusion: This is not correct .

D. Informed: The " Informed " role receives updates but is not involved in task execution. Conclusion: This is not correct .

Final Recommendation:

The category assigned to the role or person performing the task is:

A. Responsible.