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

The Business Change Lifecycle encompasses multiple stages, including alignment, analysis, design, implementation, and realisation. The role of a business analyst (BA) is versatile and can span across all these stages, depending on the project ' s needs.

Key Considerations:

Involvement Across All Stages: A business analyst can contribute to every stage of the lifecycle, from identifying business needs during alignment to ensuring benefits realization post-implementation.

Implementation Focus: While BAs are often heavily involved in implementation, their role is not limited to this stage.

Realisation Stage: BAs may also be involved in the realisation stage to validate that the intended benefits have been achieved.

Alignment Stage: Business analysis plays a critical role in aligning project objectives with organizational goals.

Evaluation of Each Option:

A. A business analyst can be involved at every stage in the lifecycle: This is true; BAs can contribute across all stages of the lifecycle. Conclusion: This is correct .

B. The business analyst is involved more heavily during the implementation stage of the lifecycle than any other stage: While BAs are often active during implementation, their involvement is not restricted to this stage. Conclusion: This is not correct .

C. The business analyst would not be involved in the realisation stage of the lifecycle: BAs can play a role in validating benefits realization, so this statement is false. Conclusion: This is not correct .

D. Business analysis does not take place in the alignment stage of a business change: Alignment involves understanding business needs and objectives, which is a core BA responsibility. Conclusion: This is not correct .

MoSCoW prioritisation categorises requirements into Must have, Should have, Could have, and Won’t have for now. Must-have requirements are essential; without them, the solution would fail or be unacceptable. Should-have requirements are important but may be deferred if necessary. Could-have requirements are desirable and would add value, but they are not essential to business success or core solution viability. “Want to have” is not a standard MoSCoW category, although it sounds similar to informal prioritisation language. The wording “desirable but not essential” points directly to Could-have requirements. These are typically delivered only if time, budget, and capacity remain after higher-priority requirements are addressed. Therefore, option A is the correct MoSCoW category.

To identify the categories of costs and benefits described in the extract, we need to analyze the content carefully:

Extract Analysis:

" New business policies and processes will be introduced, which may temporarily reduce productivity " :

This refers to a cost associated with implementing new policies and processes.

Productivity is an intangible factor because it cannot be directly measured in monetary terms.

Category: Intangible costs .

" It will ensure our products remain in the marketplace and be the first to receive compliance certification, which will enhance our reputation as the market leader " :

This refers to a benefit related to maintaining market presence, achieving compliance, and enhancing reputation.

Reputation and market leadership are intangible factors because they are qualitative and not directly quantifiable in monetary terms.

Category: Intangible benefits .

Evaluation of Each Option:

A. Tangible costs: Tangible costs are measurable financial expenses (e.g., equipment, labor). The extract does not mention any specific financial costs. Conclusion: This is not relevant .

B. Intangible costs: The temporary reduction in productivity is an intangible cost. Conclusion: This is relevant .

C. Tangible benefits: Tangible benefits are measurable financial gains (e.g., increased revenue). The extract does not mention any specific financial benefits. Conclusion: This is not relevant .

D. Intangible benefits: Enhanced reputation and market leadership are intangible benefits. Conclusion: This is relevant .

E. Irregular costs: Irregular costs refer to one-time or infrequent expenses. The extract does not describe such costs. Conclusion: This is not relevant .

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 .

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)

The Requirements Engineering (RE) Framework is a structured approach used by business analysts to define, document, and manage requirements. It consists of five iterative stages: Investigate Situation, Consider Perspectives, Analyze Needs, Evaluate Options, and Define Requirements .

Key Considerations:

Suitability for Waterfall Projects Only: The RE Framework is flexible and can be adapted to both waterfall and Agile methodologies.

Iterative Stages: The framework emphasizes iteration and refinement, making it suitable for evolving requirements.

Defining Requirements: The framework explicitly supports the definition and management of requirements.

Sequential Steps: While the stages are presented in a sequence, they are iterative and not strictly linear.

Evaluation of Each Option:

A. It is only suitable for use with waterfall projects: The RE Framework can be applied to both waterfall and Agile projects. Conclusion: This is not correct .

B. It shows five iterative stages that a business analyst needs to carry out to establish the requirements: This accurately describes the RE Framework ' s structure and purpose. Conclusion: This is correct .

C. Using the Requirements Engineering Framework does not help to define requirements: The framework is specifically designed to define and manage requirements. Conclusion: This is not correct .

D. It shows steps in the requirements engineering process that a business analyst must follow sequentially: While the stages are presented in a sequence, they are iterative and not strictly sequential. Conclusion: This is not correct .

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.

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.