Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

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

Exam Name: AgileBA (Agile Business Analysis) Foundation (2015)
Exam Code: AgileBA (Agile Business Analysis) Foundation (2015)
Related Certification(s): APMG-International Agile Business Analysis AgileBA Certification
Certification Provider: APMG-International
Number of AgileBA (Agile Business Analysis) Foundation (2015) practice questions in our database: 50 (updated: Jun. 05, 2024)
Expected AgileBA (Agile Business Analysis) Foundation (2015) Exam Topics, as suggested by APMG-International :
  • Topic 1: Agile Fundamentals and the Agile BA: This topic covers fundamental Agile principles and values. Additionally, it explores the influence of Agile on the Business Analyst's role.
  • Topic 2: The Agile Business Case: You'll learn about crafting a business case suited for Agile projects, considering factors like value delivery and continuous improvement.
  • Topic 3: Stakeholders in an Agile Project: It addresses stakeholder identification and their roles. Additionally, it focuses on effective communication management with stakeholders.
  • Topic 4: Requirements and User Stories: A crucial topic for BAs, this section covers user story creation, management, and techniques for effective requirement gathering in Agile.
  • Topic 5: Prioritization: You'll learn various prioritization techniques like MoSCoW used in Agile to determine the most important requirements. This section covers prioritization methods.
  • Topic 6: Workshops: This section focuses on conducting workshops in Agile environments to gather requirements and facilitate communication. It includes methods for running workshops in Agile.
  • Topic 7: Modeling: It covers various modeling techniques. Additionally, it includes visualizing workflows and user journeys.
Disscuss APMG-International AgileBA (Agile Business Analysis) Foundation (2015) Topics, Questions or Ask Anything Related

Currently there are no comments in this discussion, be the first to comment!

Free APMG-International AgileBA (Agile Business Analysis) Foundation (2015) Exam Actual Questions

Note: Premium Questions for AgileBA (Agile Business Analysis) Foundation (2015) were last updated On Jun. 05, 2024 (see below)

Question #1

During the Foundations phase, how is the Prioritised Requirements List used for Requirements Planning?

Reveal Solution Hide Solution
Correct Answer: D

During the Foundations phase, the Prioritised Requirements List is used for Requirements Planning by negotiating requirements and priorities to allow the first increment to be planned. This negotiation ensures that the highest priority requirements are addressed first and that the development team can focus on delivering the most valuable features in the initial increments. This approach aligns with Agile principles of iterative development and delivering value early.


Business Analysis.pdf, 'Prioritisation is extremely important during solution development...The MoSCoW prioritisation categories are related to the development and delivery of the solution'.

Question #2

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

Reveal Solution Hide Solution
Correct 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 #3

What is the process of Requirements Engineering designed to do?

Reveal Solution Hide Solution
Correct 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 #4

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

Reveal Solution Hide Solution
Correct 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 #5

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

Reveal Solution Hide Solution
Correct 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.


Unlock Premium AgileBA (Agile Business Analysis) Foundation (2015) Exam Questions with Advanced Practice Test Features:
  • Select Question Types you want
  • Set your Desired Pass Percentage
  • Allocate Time (Hours : Minutes)
  • Create Multiple Practice tests with Limited Questions
  • Customer Support
Get Full Access Now

Save Cancel