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

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.

In an iterative or Agile lifecycle, requirements are not defined entirely upfront but are explored and refined just-in-time, immediately prior to implementation. The stage where the detailed solution requirements (functional and non-functional) are elaborated, modeled, and defined—ready for construction—is the Develop solution stage (often referred to as the Implementation or Construction phase of an iteration/sprint). The detailed work of defining, modelling, and validating the specific requirements happens as a preparatory step for the actual build, distinguishing it from the preceding planning phase (C) or the upstream strategic work (A, B).

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

The true statements about workshops are b and c. Workshops are collaborative, structured meetings involving multiple stakeholders. Statement (b) is true because having multiple stakeholders present allows the facilitator (often the BA) to immediately cross-check and resolve conflicting information or assumptions in real-time. Statement (c) is true because the group environment, led by a skilled facilitator, is highly effective for discussing differing viewpoints and working towards a consensus or agreed-upon outcome. Statement (a) is false as this describes formal observation, not a workshop. Statement (d) is false; workshops are primarily used to gather qualitative information (opinions, requirements, process logic), not to collect accurate quantitative data (e.g., process timings or volumes), which is usually obtained from documents or system logs.

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

Business processes are typically organised into a three-level hierarchy to manage complexity and provide a clear line of sight from strategy to execution. The standard levels, moving from the highest to the lowest level of detail, are:

Enterprise (or Value Chain): The highest level, showing the core business functions (e.g., " Sell Product, " " Develop Product " ).

Event-Response (or End-to-End): The mid-level, showing the process triggered by a business event and concluding with an outcome (e.g., " Handle Customer Order " ).

Actor-Task (or Detailed/Procedure): The lowest level, showing the individual steps and actions taken by the actors to complete a process (e.g., " Check stock availability, " " Package item " ).

Therefore, the three key levels that define this breakdown are Enterprise, event-response, actor-task.

(Reference: BCS Modelling Business Processes / BCS Business Analysis Practice – Business Process Hierarchy)

===========

Business analyst competencies are commonly grouped into personal qualities, business knowledge, and professional techniques. Personal qualities include communication, analytical thinking, facilitation, influencing, and relationship-building. Business knowledge covers understanding the organisation, industry, strategy, finance, processes, and business context. Professional techniques include modelling, requirements engineering, stakeholder analysis, investigation techniques, and business case development. IT skills may be useful for some business analysts, especially those working on digital or software-enabled change, but IT skills are not one of the three main competency groups. Treating IT skills as a core group would narrow the business analyst role too much, because business analysis is concerned with business change, not only technology delivery. Therefore, option D is not one of the three competency groups.

In a UML Use Case Diagram, the entities that interact with the system being modeled (the System Boundary) are called Actors. An Actor represents a role played by a user, piece of hardware, or another system. External systems that exchange information with the system being defined are always represented as an actor outside the system boundary, just like human users. This clearly separates the responsibilities of the system under study from all entities and systems that lie outside its scope.

(Reference: BCS Requirements Engineering – Use Case Modelling)