PC-BA-FBA-20 Exam Preparation Material | BCS Foundation Certificate in Business Analysis V4.0

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

Explanation:
Gap analysis is a structured process used to identify the differences between the current state (as-is) and the desired future state (to-be). The first step in this process involves understanding the current situation.
Key Steps in Gap Analysis:
Assemble representations of the existing situation: This involves documenting the current state, including processes, systems, and capabilities.
Compare representations of the existing and target situations: After understanding the current state, it is compared with the desired future state to identify gaps.
Identify gaps to be addressed: Once gaps are identified, they are prioritized based on their impact and feasibility.
Consider possible actions to address the gaps: Finally, potential solutions or actions are developed to bridge the identified gaps.
Evaluation of Each Option:
A . Assemble representations of existing situation:
Understanding the current state is the foundational step in gap analysis. Without this, there is no baseline for comparison.
Conclusion: This is correct.
B . Consider possible actions to address the gaps:
This is a later step in the process, not the first.
Conclusion: This is not correct.
C . Compare representations of the existing and target situations:
Comparison occurs after the current state has been documented.
Conclusion: This is not correct.
D . Identify gaps to be addressed:
Identifying gaps follows the documentation and comparison steps.
Conclusion: This is not correct.
Final Recommendation:
The first step in the gap analysis process is: A. Assemble representations of existing situation.

Explanation:
Design thinking is a human-centered, iterative approach used to uncover innovative solutions by focusing on user needs and exploring multiple possibilities. It emphasizes creativity, collaboration, and experimentation.
Key Characteristics of Techniques:
Design Thinking: Uses an iterative process (empathize, define, ideate, prototype, test) to generate innovative options.
Fishbone Diagram: A root cause analysis tool, not focused on innovation.
Rich Pictures: A visual representation of a situation, useful for understanding context but not for generating innovative options.
Mind Maps: A brainstorming tool that organizes ideas hierarchically, but it does not inherently follow an iterative approach.
Evaluation of Each Option:
A . Design thinking:
Design thinking explicitly uses an iterative approach to uncover innovative options.
Conclusion: This is correct.
B . Fishbone diagram:
Fishbone diagrams focus on identifying root causes, not innovation.
Conclusion: This is not correct.
C . Rich pictures:
Rich pictures visualize complex situations but do not inherently foster innovation.
Conclusion: This is not correct.
D . Mind maps:
Mind maps organize ideas but do not follow an iterative, innovative process like design thinking.
Conclusion: This is not correct.
Final Recommendation:
The technique that uses an iterative approach to uncover innovative options is: A. Design thinking.

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

Explanation:
The Stakeholder Wheel (or Stakeholder Interest Groupings) is a model used to categorize stakeholders in the strategic analysis phase, particularly for external environment analysis. This technique groups stakeholders based on their primary relationship to the organisation. The key groups included in the stakeholder wheel are Suppliers, Customers, Competitors, Partners, Owners (Shareholders), Regulators/Government, Media, and Employees/Trade Unions. Based on the options provided, the group that contains three valid, distinct categories from this standard model is Regulators, Auditors, Owners. While 'Auditors' can be considered part of the 'Regulators' or 'Owners' (depending on their role), and 'Owners' are often Shareholders, this option best reflects the high-level external interest groups used for broad strategic categorization compared to the internal focus of B or the mixed categories of A and C. The inclusion of Regulators and Owners is essential for any strategic stakeholder analysis.
(Reference: BCS Business Analysis Practice C Stakeholder Analysis, Stakeholder Wheel)