APMG-International AgileBA-Foundation AgileBA (Agile Business Analysis) Foundation (2015) Exam Practice Test

Page: 1 / 14
Total 50 questions
Question 1

Which of the following is NOT shown in a Business Domain Model?



Answer : B

A Business Domain Model typically shows the following elements:

Classes: Represent the entities or objects in the business domain.

Associations: Describe the relationships between classes.

Multiplicities: Indicate the number of instances in a relationship between classes.

Actors, which represent roles played by users or other systems that interact with the system, are not typically shown in a Business Domain Model. They are usually depicted in Use Case Diagrams.


The Business Domain Model focuses on Classes, Associations, and Multiplicities to describe the structure and relationships within the business domain.

Question 2

In the KANO Model, what is NOT one of the three distinct types of customer need?



Answer : D

In the KANO Model, the three distinct types of customer needs are:

Expected (Basic Needs): These are the fundamental requirements that customers expect to be met. If these needs are not fulfilled, customers will be dissatisfied.

Normal (Performance Needs): These are the needs that customers explicitly state and expect to be fulfilled. The better these needs are met, the more satisfied the customers will be.

Exciters (Delight Needs): These are the features that go beyond customer expectations and provide delight when fulfilled.

'Teasers (When)' is not a type of customer need in the KANO Model.


The KANO Model focuses on Expected, Normal, and Exciters needs to categorize customer requirements and satisfaction levels.

Question 3

According to the MoSCoW technique, what is a Must Have requirement?



Answer : A

According to the MoSCoW technique, a 'Must Have' requirement is something that the project will fail without. These requirements are absolutely essential for the system to function and meet the business needs. If even one 'Must Have' requirement is not met, the project would be considered a failure. This prioritization ensures that critical functionality is delivered in the first increment and forms the basis of the minimum viable product (MVP).


The MoSCoW technique defines 'Must Have' requirements as mandatory and essential for the project's success, without which the system has no value.

Question 4

What is the process of Requirements Engineering designed to do?



Answer : B

The process of Requirements Engineering is designed to ensure that requirements are carefully elicited, analyzed, and validated in a structured and rigorous manner. It involves evolving requirements from high-level business objectives down to low-level detailed specifications. This ensures that the final requirements are aligned with business needs and can be effectively implemented in the solution. The process typically includes several stages:

Requirements Elicitation: Gathering requirements from stakeholders through various techniques such as interviews, workshops, and observations.

Requirements Analysis: Refining and prioritizing the elicited requirements to ensure they are clear, complete, and feasible.

Requirements Validation: Confirming that the requirements accurately represent the stakeholders' needs and are feasible for implementation.

Requirements Documentation: Recording the requirements in a formal document to ensure they are communicated clearly to all stakeholders.

Requirements Management: Managing changes to the requirements as the project progresses.


The comprehensive process of Requirements Engineering ensures that requirements evolve from high-level objectives down to low-level detail, aligning with the needs and expectations of the business.

Question 5

What phase in the DSDM process is used to review the success of the deployed solution in the operational environment?



Answer : D

The phase in the DSDM process used to review the success of the deployed solution in the operational environment is the Post-Project phase. This phase involves evaluating whether the deployed solution has met its business objectives and delivered the expected benefits. It includes a benefits review to determine the extent to which the anticipated benefits have been realized and to identify any further actions needed to achieve these benefits fully.


The Post-Project phase focuses on reviewing the success of the deployed solution in the operational environment, assessing whether it has met the business objectives, and conducting a benefits review to evaluate the realization of the predicted benefits.

Question 6

Which role in the DSDM Team Model owns the Deployed Solution and is responsible for the realisation of any benefits associated with it?



Answer : B

In the Dynamic Systems Development Method (DSDM) Team Model, the role that owns the deployed solution and is responsible for realizing any benefits associated with it is the Business Visionary. The Business Visionary is typically a senior project stakeholder with a clear understanding of the business objectives and the strategic direction of the organization. They ensure that the project remains aligned with business goals and that the benefits of the deployed solution are realized.


The Business Visionary is crucial in the DSDM framework as they own the deployed solution and are accountable for the realization of the associated benefits. This role is responsible for ensuring that the project's outcomes meet the strategic business needs and deliver the expected value.

In the DSDM (Dynamic Systems Development Method) team model, the role that owns the Deployed Solution and is responsible for the realization of any benefits associated with it is the Business Visionary. This role is pivotal in ensuring that the project delivers the expected benefits to the business.

Business Sponsor: This role provides the overall funding and champions the project at the highest level but does not directly own the deployed solution.

Business Visionary: This role is responsible for defining the business vision for the project and ensuring that the solution delivered meets this vision. They work closely with the team throughout the project lifecycle to ensure the project remains aligned with business goals. The Business Visionary is the key figure in realizing the benefits as they have the strategic oversight and authority to ensure the solution delivers value.

Agile BA: While the Agile Business Analyst plays a crucial role in facilitating communication and ensuring requirements are met, they do not own the deployed solution.

Business Ambassador(s): These stakeholders represent the end-users and ensure their needs are communicated, but they do not hold ownership of the deployed solution.

Thus, the correct answer is B. Business Visionary, as this role is integral to owning the deployed solution and ensuring the realization of associated benefits.

Question 7

Which statement about Requirements Activities during Feasibility is true?

1. The Project objective can be defined as a high-level Epic Story

2. Epic Stories may be classified into Themes



Answer : C

During the feasibility stage of an Agile project, the requirements activities can indeed include defining the project objective as a high-level Epic Story. This is a common practice as it provides a broad understanding of the project scope and goals. Additionally, Epic Stories are often classified into Themes. Themes are groups of related Epics that align with larger organizational goals or strategic objectives. This classification helps in organizing and prioritizing work more effectively during the project lifecycle.


The feasibility study stage involves identifying broad requirements and considering various options to address these requirements. This includes defining the project objective as a high-level Epic Story and organizing Epic Stories into Themes for better management and alignment with strategic goals .

Page:    1 / 14   
Total 50 questions