PC-BA-FBA-20 Exam Dumps and Practice Questions

A benefits dependency network shows how business objectives, expected benefits, enabling business changes, and supporting outputs are connected. It helps analysts and stakeholders understand how a proposed change is expected to create value. The technique is useful because benefits are rarely achieved simply by delivering a system or product; they depend on business changes such as process redesign, behaviour change, training, new roles, or organisational adoption. Option B is too narrow because a benefits dependency network is not merely a stakeholder-benefit list. Option C describes cost breakdown, not benefit dependency. Option D describes requirements traceability, which is a different requirements management technique. The correct description is an overall representation linking objectives, benefits, and the business changes needed to realise those benefits.

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.

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 .

Personas are fictional but evidence-based representations of typical users or customer groups. They help business analysts and design teams understand user goals, behaviours, needs, frustrations, and motivations. Personas are often developed from user research and can be based on generic user roles, then enriched with characteristics that make them realistic and useful for analysis. They are not equivalent to a RACI chart because RACI defines responsibility, accountability, consultation, and information responsibilities for tasks. A single real user may also perform multiple roles, so option B is too restrictive. Personas are useful in user-centred design and requirements analysis, but they are not mandatory for decision analysis. Therefore, the true statement is that personas are taken from generic user roles.

Gap analysis is a technique for comparing the current state of the business ('As Is') with the desired future state ('To Be') to identify what is missing and what needs to change. The logical first step is to establish the current starting point. Therefore, the process begins by:

Assemble representations of existing situation (The 'As Is' model). This involves investigating and documenting the current processes, organisation, people, information, and technology (POPIT).

Assemble representations of target or desired situation (The 'To Be' model).

Identify gaps to be addressed (The difference between As Is and To Be).

Consider possible actions to address the gaps (Developing the recommendations).

(Reference: BCS Business Analysis Practice -- Gap Analysis)