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

Page: 1 / 14
Total 50 questions
Question 1

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 2

Which core characteristics should the Agile BA consider when planning and implementing change?

1. Culture

2. Communication

3. Contingency

4. Collaboration



Answer : B

When planning and implementing change in Agile projects, the Agile BA should consider core characteristics such as culture, communication, and collaboration.

Culture: Understanding the organizational culture is critical for implementing change successfully. This includes recognizing existing values, beliefs, and behaviors that may support or hinder the change process.

Communication: Effective communication is essential to ensure that all stakeholders are informed and engaged throughout the change process. Clear, consistent, and transparent communication helps to build trust and ensures that everyone understands the objectives and benefits of the change.

Collaboration: Agile methodologies emphasize teamwork and collaboration. Engaging stakeholders, including team members from different disciplines, ensures diverse perspectives and fosters a sense of ownership and commitment to the change initiative.

Contingency, while important, is not typically highlighted as a core characteristic by Agile BAs when planning and implementing change. Instead, Agile frameworks often focus on flexibility and adaptability to manage uncertainties rather than formal contingency planning. Reference: Business Analysis document, sections on change management, Agile principles, and the role of communication and collaboration in Agile projects.


Question 3

Which Stakeholder works with the Agile BA to prepare the users of the solution working within the relevant business area, for each incremental deployment of an Evolving Solution?



Answer : D

The Business Ambassador works with the Agile BA to prepare the users of the solution within the relevant business area for each incremental deployment of an evolving solution. The Business Ambassador acts as a liaison between the development team and the end users, ensuring that the requirements and feedback are effectively communicated and that the users are ready to adopt the new increments of the solution as they are deployed.


Business Analysis.pdf, 'The role of the business analyst in an Agile environment...supporting the business users'.

Question 4

What are the main ingredients of a culture that supports Agile?



Answer : A

The main ingredients of a culture that supports Agile are trust and ownership. Agile methodologies emphasize the importance of empowering teams to make decisions, fostering a culture of mutual respect, and encouraging individuals to take ownership of their work. This environment promotes collaboration, transparency, and accountability, which are essential for the success of Agile projects.


Business Analysis.pdf, 'Individuals and interactions over processes and tools...Customer collaboration over contract negotiation'.

Question 5

Which Facilitated Workshop role may attend a meeting to review the process being adopted and methods used?



Answer : A

In a Facilitated Workshop, the role of an Observer may include attending a meeting to review the process being adopted and methods used. Observers provide an external perspective on the workshop's effectiveness and can offer feedback on the facilitation techniques, group dynamics, and overall process. Their role is crucial in ensuring that the workshop is conducted efficiently and meets its objectives.


Business Analysis.pdf, 'Observers can provide feedback on the workshop process and methods used, helping to improve future sessions'.

Question 6

What technique is used to categorise Stakeholders according to their level of involvement in the project?



Answer : C

The technique used to categorize stakeholders according to their level of involvement in the project is the Power/Interest Grid. This technique is essential for identifying which stakeholders need to be managed closely and which can be monitored with less effort. The grid categorizes stakeholders based on their power to influence the project and their interest in the project's success. This categorization helps in devising appropriate stakeholder management strategies by assessing their power and interest levels and planning interactions accordingly.


Business Analysis.pdf, 'Stakeholder analysis...provides a means of categorising stakeholders in order to identify the most appropriate stakeholder management approach'.

Question 7

In an Agile project, what demonstrates adherence to the Principle of Demonstrate Control?



Answer : C

In an Agile project, adherence to the principle of 'Demonstrate Control' is shown by making plans visible and accessible to all stakeholders. This transparency ensures that everyone involved in the project can see the progress, understand the current status, and be aware of any changes. This is typically achieved by:

Displaying Plans in a Shared Workspace: This could be physical (like a Kanban board) or digital (like a project management tool) where plans, progress, and any changes are visible to the entire team and other stakeholders.

Regular Updates and Reviews: Frequent stand-ups, reviews, and retrospectives ensure that the team maintains control over the project by continuously assessing progress and making adjustments as necessary.

Collaborative Tools: Using collaborative tools that support transparency and open communication helps in maintaining control over the project's direction and progress.

These practices contrast with traditional methods where control might be demonstrated through strict adherence to predefined processes or by delivering all requirements regardless of their prioritization.


Business Analysis.pdf: Emphasizes the importance of transparency and regular communication in Agile projects to demonstrate control and ensure alignment with project goals.

Page:    1 / 14   
Total 50 questions