PC-BA-FBA-20 BCS Foundation Certificate in Business Analysis V4.0 Question and Answers

The POPITâ„¢ model is a holistic framework used in business analysis to ensure that all aspects of the business system are considered when investigating a situation or implementing a change. The acronym stands for People, Organisation, Processes, Information, and Technology. Therefore, the two 'P' components of the model are People and Processes. 'People' relates to skills, motivation, job roles, and culture. 'Processes' refers to the defined procedures, activities, and tasks carried out to deliver the business service. Ensuring that changes are successful requires addressing all five components, as a change in one area (e.g., a new IT system) invariably impacts the other areas (e.g., the skills of the People, or the Information required).

(Reference: BCS Foundation Certificate in Business Analysis / BCS Business Analysis Practice – Holistic View of the Business System, POPIT Model)

Kaplan and Norton's Balanced Business Scorecard is a strategic framework that evaluates organizational performance across four key perspectives: Financial, Customer, Internal Business Processes, and Learning and Growth . To determine which area has not been considered, we need to map the provided KPIs to these perspectives.

Mapping the KPIs:

The time to deliver orders for products:This relates to operational efficiency and falls under the Internal Business Process perspective.

Consumer satisfaction with products:This directly measures customer experience and falls under the Customer perspective.

Wastage in product production:This also relates to operational efficiency and falls under the Internal Business Process perspective.

The qualifications of production employees:This measures employee capabilities and development, falling under the Learning and Growth perspective.

Evaluating Each Perspective:

Financial:None of the provided KPIs address financial performance, such as revenue, profitability, or cost management.Conclusion: This perspective has not been considered .

Customer:Consumer satisfaction with products is a clear indicator of the Customer perspective.Conclusion: This perspective has been considered.

Internal Business Process:Both "time to deliver orders" and "wastage in production" relate to internal processes.Conclusion: This perspective has been considered.

Learning and Growth:The qualifications of production employees indicate employee development, which aligns with this perspective.Conclusion: This perspective has been considered.

Final Recommendation:

The Financial perspective has not been considered in the company’s KPIs.

When developing options for a business change, the business analyst must consider a range of solution types, which often fall into categories to ensure all possibilities are explored. While the exact naming conventions can vary, the following three core types are commonly considered and often named as:

Basic (or "Do Minimum") option: A low-cost, minimal-effort option to address the problem without major change (often including the "Do Nothing" or "Do Nothing Different" option for comparison).

Extended (or "Do Something" option): The preferred or main option, representing the full-scale, major change recommended to achieve the business objectives.

Executive (or "Commercial Off-The-Shelf (COTS)") option: An option based on purchasing an existing system or service, rather than custom-building a solution.Exhaustive option is NOT a standard or recognised category of business change option within the BCS syllabus.

(Reference: BCS Business Analysis Practice – Business Case, Identifying Options)

===========

The Use Case Diagram is a conceptual model that shows the interaction between users (actors) and the required features (use cases) of the system. In an Agile context, use cases provide a high-level view of the system's intended functionality, which can be directly mapped to Epics and subsequently decomposed into lower-level User Stories. The use case diagram helps the team understand the scope and the user's interaction paths, making it an excellent visual tool for managing and breaking down the product backlog (of user stories) into manageable chunks. The other options are too technical (A, D) or focus only on object state (B).

(Reference: BCS Requirements Engineering / BCS Agile – Use Case Modelling and Product Backlog Management)

The Business Analysis Service Framework (BASF) identifies six core services provided by a business analyst. These services span the lifecycle of a business change initiative and focus on analysis and enablement activities. The six services are: Situation Investigation and Problem Analysis, Feasibility Assessment and Business Case Development, Business Process Improvement, Requirements Definition, Requirements Management, and Business Change Deployment. The service Solution design and development (which involves the technical building of the IT system) is a distinct project activity typically performed by solution architects and developers and, while the BA collaborates with them closely, it is not one of the core Business Analysis services as defined in the BASF.

(Reference: BCS Foundation Certificate in Business Analysis / BCS Business Analysis Practice – Business Analysis Service Framework (BASF))

A change strategy outlines how an organization will move from its current state to its desired future state. Its purpose is to ensure a structured and effective transition.

Key Considerations:

Ensuring the simplest way for transition: While simplicity is desirable, it is not the primary purpose of a change strategy.

Ensuring the quickest way for transition: Speed is not the main focus; effectiveness and alignment with goals are more important.

Achieving the transition between current state and future state: This accurately describes the purpose of a change strategy, which is to bridge the gap between where the organization is now and where it wants to be.

Mapping the alternative options: While mapping options may be part of the planning process, it is not the ultimate purpose of the change strategy.

Evaluation of Each Option:

A. Ensuring the simplest way for transition:Simplicity is a consideration but not the primary purpose of a change strategy.Conclusion: This is not correct .

B. Ensuring the quickest way for transition:Speed is secondary to achieving an effective and sustainable transition.Conclusion: This is not correct .

C. Achieving the transition between current state and future state:This is the core purpose of a change strategy, ensuring the organization moves effectively toward its goals.Conclusion: This is correct .

D. Mapping the alternative options:Mapping options is part of the analysis phase, not the overarching purpose of the strategy.Conclusion: This is not correct .

Final Recommendation:

The best description of the purpose of a change strategy is:

C. Achieving the transition between current state and future state.

The development of a Business Case is often an iterative process. Before significant investment is made in creating the detailed Initial Business Case (often called the Outline Business Case or OBC), a preliminary assessment is required to ensure the proposed change is viable. This assessment is the Feasibility study (or Feasibility Assessment). A feasibility study quickly evaluates the proposed initiative to confirm it is technically possible, financially justifiable, and strategically aligned (Business Feasibility). The outcomes of this study determine whether it is worthwhile to proceed to the more detailed, full business case development. The other options (A, B, D) occur after the initial business case is approved and investment is committed.

(Reference: BCS Business Analysis Practice – Business Case Lifecycle)

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)

The stakeholder wheel is a framework used to categorize stakeholders based on their relationship to the organization or project. It typically includes categories such as customers, partners, suppliers, regulators, and competitors , among others.

Key Considerations:

Regulators, Compliance, Owners: While regulators and owners are valid stakeholders, "compliance" is not a stakeholder category but rather a function or responsibility.

Competitors, Customers, Partners: These are all valid stakeholder categories commonly found on the stakeholder wheel.

Competitors, Consumers, Providers: While competitors and consumers (a synonym for customers) are valid, "providers" is not a standard term used in the stakeholder wheel.

Contractors, Partners, Suppliers: Contractors are not typically included as a primary stakeholder category on the stakeholder wheel, though partners and suppliers are.

Evaluation of Each Option:

A. Regulators, Compliance, Owners:"Compliance" is not a stakeholder category; it refers to adherence to rules or regulations.Conclusion: This is not correct .

B. Competitors, Customers, Partners:These are all valid stakeholder categories found on the stakeholder wheel.Conclusion: This is correct .

C. Competitors, Consumers, Providers:While competitors and consumers (customers) are valid, "providers" is not a standard stakeholder category.Conclusion: This is not correct .

D. Contractors, Partners, Suppliers:Contractors are not typically included as a primary stakeholder category on the stakeholder wheel.Conclusion: This is not correct .

Final Recommendation:

The list that only includes stakeholders shown on the stakeholder wheel is:

B. Competitors, Customers, Partners

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.

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â„¢.

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)

Traceability links requirements to other project artefacts. There are two main types: horizontal and vertical. Horizontal traceability (Option A) links a requirement forward to its design, code, and test cases, and backward to its source (Option D), tracing its lifecycle from inception to delivery. Vertical traceability concerns tracing a requirement up or down the requirements hierarchy (C). This ensures that lower-level requirements (e.g., functional) are aligned with and fully support the higher-level business objectives, policies, and strategy. For example, it traces a solution requirement up to the business requirement it satisfies, validating that every low-level detail is necessary and justified by a high-level business need.

(Reference: BCS Requirements Engineering – Requirements Traceability)

The Iterative (or Agile) lifecycle model is specifically designed to deal with changing requirements and a rapid pace of change. Unlike linear models like Waterfall or the V model, which expect requirements to be fixed early, the iterative model delivers the solution in a series of repeated cycles (iterations/sprints). This approach embraces the reality that requirements will change as stakeholders learn more about the evolving product and the business environment shifts. It explicitly incorporates frequent feedback loops and allows for the adaptation of requirements throughout the project, making it the most flexible and suitable model for unstable or complex environments.

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

To determine the best source of information for Natasha to understand how Halliday Holdings' brand is perceived, we need to evaluate the options based on their relevance and objectivity.

Evaluation of Each Option:

A. Independent industry websites:Independent industry websites often provide unbiased insights into how a company's brand is perceived by customers, competitors, and the market. These sources aggregate reviews, ratings, and expert opinions, making them a valuable resource for understanding external perceptions.Conclusion: This is the best source .

B. The company website:The company website reflects the organization's internal perspective and branding efforts. While useful for understanding how the company presents itself, it does not provide an external view of brand perception.Conclusion: This is not the best source .

C. The company's organizational structure:The organizational structure provides insights into the company's internal hierarchy and operations but does not relate to external brand perception.Conclusion: This is not relevant .

D. The company's complaints procedures:Complaints procedures reflect internal processes for handling customer issues but do not provide a comprehensive view of overall brand perception.Conclusion: This is not the best source .

The Business Readiness Assessment is a key activity conducted during the Implementation or Business Change Deployment stage of the project. Its primary purpose is to determine whether the target business areas, including the People, Organisation, and Processes, are sufficiently prepared to accept the business change and begin operating the new solution in the 'To Be' state. This involves checking factors such as whether staff have been trained, new processes are documented, communication has been effective, and necessary resources are in place. This assessment informs the 'Go/No Go' decision for the system's launch, ensuring a smooth transition to the new way of working.

(Reference: BCS Business Analysis Practice – Business Change Deployment, Business Readiness)

The hierarchy of requirements organizes requirements into levels (e.g., business needs, stakeholder requirements, solution requirements) to ensure alignment and traceability. Let’s evaluate each statement to determine which is false .

Key Characteristics of the Requirements Hierarchy:

Linking Requirements: The hierarchy ensures that detailed requirements are connected to higher-level business needs and objectives.

Order of Development: The hierarchy does not dictate the sequence in which requirements should be developed; it focuses on relationships and dependencies.

Driven by Strategy: Requirements are derived from the organization's values, strategy, and objectives.

Traceability: The hierarchy links different types of requirements to ensure consistency and alignment.

Evaluation of Each Statement:

A. The requirements hierarchy enables detailed requirements to be linked to the business need:This is true; the hierarchy ensures traceability between high-level and detailed requirements.Conclusion: This is true .

B. The requirements hierarchy shows the order in which requirements should be developed:The hierarchy does not specify the development order; it focuses on relationships and dependencies.Conclusion: This is false .

C. Requirements are driven by the organisation's values, strategy and objectives:This is true; requirements must align with organizational goals.Conclusion: This is true .

D. The requirements hierarchy links different requirements to each other:This is true; the hierarchy ensures traceability and alignment across levels.Conclusion: This is true .

Final Recommendation:

The false statement is:

B. The requirements hierarchy shows the order in which requirements should be developed.

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.

Requirements documentation generally follows two main styles: text-based and diagrammatic (or model-based).

Data model (A), Use case model (C), and Business process models (D - e.g., UML Activity Diagrams or BPMN) are all forms of diagrammatic documentation, using standardised graphical notation to express requirements.

A User story (B) is a short, simple, text-based statement written in the format: "As a [role], I want [goal] so that [benefit]". It is a form of text-based requirement documentation used primarily in Agile environments, not a diagrammatic style.

(Reference: BCS Requirements Engineering – Documentation Styles)

===========

  To determine the appropriate stakeholder management strategies for Harvey, we need to analyze his role and level of interest at two points in time:

When the project started: Harvey was the Director of Operations and had little interest in the HR project because his focus was on operational projects.

Now that his role has changed: As the Director of HR, Harvey has inherited sponsorship of the HR project, making him a key stakeholder with high interest and influence.

Stakeholder Management Strategies:

Watch: This strategy is used for stakeholders with low interest and low influence. It involves monitoring their behavior without actively engaging them.

Constant active management: This strategy is used for stakeholders with high interest and high influence. It involves frequent communication and collaboration to ensure their needs and expectations are met.

Evaluation of Each Option:

A. Keep informed; Constant active management:"Keep informed" is appropriate for stakeholders with moderate interest but does not align with Harvey's initial lack of interest.Conclusion: This is not correct .

B. Ignore, Constant active management:Ignoring a stakeholder is inappropriate, especially for someone in a senior leadership role like Harvey.Conclusion: This is not correct .

C. Watch, Constant active management:

Initially, Harvey had low interest and low influence on the HR project, making "watch" an appropriate strategy.

After becoming the Director of HR and inheriting sponsorship, Harvey now requires "constant active management" due to his high interest and influence.Conclusion: This is the correct answer .

D. Constant active management, keep informed:This reverses the order of strategies and does not align with Harvey's initial lack of interest.Conclusion: This is not correct .