PC-BA-FBA-20 Exam Questions & Answers

A formal Requirements Validation Review (or walkthrough/inspection) is conducted to ensure the requirements are correct, complete, and meet the business need before sign-off. The review group typically includes the Business Owner (A) to ensure correctness, the Solution Architect (C) and Developers to check technical feasibility, and the Tester (D) to ensure testability. The Project Manager (B) is usually the facilitator or organiser of the review process and is responsible for project delivery, but they are NOT usually a technical reviewer of the document content itself, as their direct involvement could compromise the impartiality of the review, which is focused on quality assurance, not project schedule.

(Reference: BCS Requirements Engineering -- Requirements Validation Techniques)

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.

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.

The RACI chart is a technique used to clarify and document the roles and responsibilities for activities, tasks, or deliverables within a project or business process. It is an acronym that defines the four key types of involvement:

Responsible: The person or team who does the work to complete the task.

Accountable: The person who is ultimately answerable for the correct and thorough completion of the deliverable or task, and who approves the work. Only one person can be Accountable.

Consulted: The people whose opinions are sought, and with whom there is two-way communication.

Informed: The people who are kept up-to-date on progress, often only at the completion of the task or deliverable, and with whom there is only one-way communication.

The correct categories are therefore Responsible, Accountable, Consulted, Informed.

(Reference: BCS Business Analysis Practice -- Stakeholder Management, RACI Matrix)

===========

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.