PC-BA-FBA-20 Exam Dumps - BCS Business Analysis Questions and Answers

The concern of consumers about unnecessary packaging is an external factor that influences the organisation. The appropriate technique for systematically analysing these external macro-environmental factors is PESTLE analysis. PESTLE stands for Political, Economic, Sociological, Technological, Legal, and Environmental factors. The increasing consumer concern about packaging falls clearly under the Sociological or Environmental categories of the PESTLE framework. This technique helps the business analyst identify trends and issues arising from outside the organisation that may create a business need or risk, which then drives strategic change. The other options are incorrect: a Power/Interest grid is for stakeholder management; Boston Box (BCG Matrix) is for product portfolio management; and a Resource Audit is for internal analysis of resources.

(Reference: BCS Foundation Certificate in Business Analysis / BCS Business Analysis Practice – Strategic Analysis, External Environment Analysis)

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 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)

===========

The technique described is a Mind map. A Mind Map is a non-linear, visual tool used for structuring information and generating ideas around a central concept. It is characterized by having a central image or topic from which topic-related branches and sub-branches radiate. The structure helps the business analyst (or a group in a workshop) to organize complex, unstructured thoughts, visualize associations, and explore an area holistically. This technique is often used in the initial stages of investigation, such as problem analysis or requirements elicitation, to help gain a broad understanding of the scope and related issues. This is distinct from a Process map (which shows the flow of activities), an Entity relationship diagram (which models data structures), or the Business analysis process model (which models the BA ' s work steps).

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

In a UML (Unified Modeling Language) Activity Diagram, the symbol used to represent a task (or action/activity) is a round-cornered rectangular box. This shape denotes an individual piece of work or step carried out within the process.

The other symbols represent:

A filled in circle (B): The Initial Node (start of the process).

A diamond shaped box (C): A Decision or Merge Node (a point where a choice is made or paths recombine).

A bullseye (D) (a filled circle inside an outer circle): The Activity Final Node (end of the process flow).

(Reference: BCS Modelling Business Processes / BCS Business Analysis Practice – UML Activity Diagrams)

===========

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 .

Functional and non-functional requirements sit within the detailed requirements area and describe what the solution must do and how well it must perform. Functional requirements define required behaviour, services, processing, calculations, or interactions. Non-functional requirements define qualities and constraints such as performance, security, usability, availability, and reliability. In a requirements hierarchy, these requirements are developed from broader business, general, and technical requirement categories. Option B is too narrow because it describes mainly non-functional requirements, not functional requirements. Option D is wrong because the highest level is the business need or business requirement. Option A refers to project principles, not solution requirements. Therefore, functional and non-functional requirements are best described as an elaboration of General and Technical requirements.

An organization chart visually represents the structure of an organization, including roles, responsibilities, and reporting relationships. By reviewing the organization chart, Sara can learn specific details about the sponsor of her project.

Key Considerations:

Position in the company hierarchy: The organization chart clearly shows where the sponsor fits within the company’s structure (e.g., senior leadership, middle management). This helps Sara understand their level of authority and influence.

Span of control: The chart also reveals how many teams or individuals report to the sponsor, providing insight into their scope of responsibility and decision-making power.

Culture within their team: While the chart may hint at team structure, it does not provide qualitative information about team culture, which requires direct observation or interviews.

Scope of their responsibilities: The chart outlines reporting lines but does not explicitly detail the specific responsibilities of the sponsor.

Preferred management style: Management style is a behavioral trait that cannot be inferred from an organization chart alone.

Evaluation of Each Option:

A. Their position in the company hierarchy: The organization chart explicitly shows the sponsor ' s position in the hierarchy, helping Sara understand their level of authority. Conclusion: This is relevant .

B. Their span of control: The chart reveals how many people or teams report to the sponsor, indicating their span of control. Conclusion: This is relevant .

C. The culture within their team: Team culture is not represented in an organization chart. It requires additional qualitative data. Conclusion: This is not relevant .

D. The scope of their responsibilities: While the chart provides structural information, it does not specify the exact responsibilities of the sponsor. Conclusion: This is not relevant .

E. Their preferred management style: Management style cannot be determined from an organization chart. Conclusion: This is not relevant .

The investigation technique best suited to achieve these outcomes is the Interview. A one-on-one interview provides a private and focused setting, which is essential for discussing confidential or politically sensitive issues that a stakeholder would not be comfortable raising in a group or on a written questionnaire. The personal interaction during an interview is the most effective way to build rapport with the stakeholder, leading to more open and honest communication. This deeper level of trust and detailed conversation is what allows the analyst to gain a richer appreciation of the political and cultural landscape of the business. Special purpose records, document analysis, and questionnaires are more impersonal and cannot provide the same level of qualitative insight or trust.

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

When documenting risks in a business case, it is essential to follow structured processes to ensure risks are appropriately identified, analyzed, and managed. Let’s evaluate each option again based on best practices outlined in the BCS Business Analysis Framework and other methodologies:

Key Considerations:

Risk Documentation: Risks must be recorded systematically to ensure they are visible, actionable, and traceable.

Ownership of Risks: Assigning ownership ensures accountability and clarity about who is responsible for monitoring and mitigating each risk.

Risk Management Lifecycle: The process typically involves identification, documentation, assessment, ownership assignment, and response planning.

Evaluation of Each Option:

A. Create a RAID log

A RAID log (Risks, Assumptions, Issues, and Dependencies) is a widely used tool in business analysis and project management for capturing and managing risks systematically.

It provides a centralized repository for tracking risks, assumptions, issues, and dependencies, ensuring that risks are documented comprehensively and transparently.

This aligns with best practices for risk management and is a critical first step in ensuring risks are appropriately recorded.

Conclusion: This is a must-do action.

B. Document the source of each risk

While documenting the source of each risk can provide valuable context, it is not a mandatory or primary step in the initial documentation phase.

Sources of risks are often identified during risk analysis or root cause analysis, which occurs after risks have been recorded.

Although useful, this step is secondary to creating a RAID log and assigning ownership.

Conclusion: This is not the most critical action at this stage.

C. Identify an owner for each risk

Assigning ownership for each risk is a fundamental part of risk management. Without clear ownership, risks may remain unmonitored or unaddressed.

Ownership ensures accountability and helps streamline communication and decision-making regarding risk mitigation strategies.

According to the BCS Business Analysis Framework , identifying risk owners is a key responsibility during the risk documentation process.

Conclusion: This is a must-do action.

D. Provide justification for each countermeasure identified

Justifying countermeasures is part of the risk response planning phase, which occurs after risks have been documented, assessed, and prioritized.

At this stage, John’s focus should be on identifying and recording risks, not on evaluating or justifying solutions.

Conclusion: This is not relevant at the documentation stage.

E. Impact assessment of each countermeasure identified

Similar to option D, impact assessments for countermeasures are conducted during the risk response planning phase, not during the initial documentation phase.

This step is premature and does not align with the immediate need to document risks.

Conclusion: This is not relevant at the documentation stage.

Final Recommendation:

Based on the BCS Business Analysis Framework and industry best practices, the two most appropriate actions for John are:

Create a RAID log (to systematically document risks).

Identify an owner for each risk (to ensure accountability and clarity).

These steps ensure that risks are appropriately recorded and managed, laying the foundation for effective risk management.