AGILEBA-FOUNDATION Practice Questions

Within a DSDM (Dynamic Systems Development Method) project, the Solution Development Team is

responsible for estimating. This team includes developers, testers, and business representatives who

collaboratively estimate the effort required for each requirement. Their combined expertise ensures

that the estimates are realistic and achievable, facilitating effective planning and delivery of the

project.

Reference:

Business Analysis.pdf, Chapter 11, Documenting and Managing Requirements​

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.

Reference:

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​​.

In addition to preparing for the content of the Workshop, the Facilitator and Workshop Owner must

oversee the preparations for venue and logistics. The Facilitator is responsible for ensuring that the

workshop's objectives are met through effective facilitation, while the Workshop Owner ensures that

all logistical arrangements, such as booking the venue and organizing necessary materials, are in

place. Together, they ensure the workshop runs smoothly and achieves its goals.

Reference:

Business Analysis.pdf, "The success or failure of a workshop session depends in large part upon the

preparatory work done by its facilitator and its business sponsor"​​.

The Agile Business Analyst (BA) role is primarily focused on representing the business view. Agile BAs

work closely with stakeholders to understand their needs, clarify requirements, and ensure that the

development team delivers solutions that align with business objectives. While technical knowledge

is beneficial, the BA's core responsibility is to bridge the gap between business stakeholders and the

development team, ensuring that the final product meets the business requirements and adds value.

Reference:

Business Analysis.pdf, "The role of the business analyst in an Agile environment is explored further in

Chapters 10 and 13"​​.

In Bill Wake's INVEST model, the characteristic of a User Story that requires it to be kept to a few

person-days or at most, a few person weeks is "Small." This characteristic ensures that user stories

are manageable, can be completed within a single iteration, and allows for more accurate estimation

and easier testing and integration.

Reference:

Business Analysis.pdf, "The user story will generally be framed to answer the questions Who? What?

Why?... and be expressed in the format: ‘As a {user role} I want {feature} so that I can {reason}.’"​​.

Porter's Five Forces Analysis is a technique used to analyze the industry or business domain within

which an organization operates. It helps to identify the competitive forces that influence the

profitability and attractiveness of a market. These forces include the threat of new entrants, the

bargaining power of suppliers, the bargaining power of buyers, the threat of substitute products or

services, and the intensity of competitive rivalry. This analysis is essential for understanding the

external business environment and for strategic planning.

Reference:

Business Analysis.pdf, Chapter 3, Strategy Analysis

A good User Story should include Acceptance Criteria. Acceptance Criteria define the conditions that

must be met for the story to be considered complete and ensure that the developed feature meets

the user's needs and expectations. These criteria provide a clear and measurable way to verify that

the functionality works as intended and helps in achieving a shared understanding between the

development team and the stakeholders.

Reference:

Business Analysis.pdf, "The user story will generally be framed to answer the questions Who? What?

Why?...and include acceptance criteria"​​.

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.

Reference:

Business Analysis.pdf, "Prioritisation is extremely important during solution development...The

MoSCoW prioritisation categories are related to the development and delivery of the solution"​​.

A project stakeholder can be categorized into different types, and understanding these categories is

crucial for effective stakeholder management. The primary categories are:

Internal Stakeholders: These are individuals or groups within the organization who are affected by or

can affect the project. This includes employees, managers, and other departments within the

organization.

External Stakeholders: These include entities outside the organization such as customers, suppliers,

investors, regulatory bodies, and the community at large.

Technical Stakeholders: Typically refer to individuals or groups responsible for the technical aspects

of the project, such as IT staff, system architects, and developers.

Strategic Stakeholders: These are stakeholders who have a significant influence over the strategic

direction of the project or organization, such as senior executives and board members.

Among these, the primary stakeholder categories are internal and external, as they encompass the

broadest range of individuals or groups affected by the project. Internal stakeholders are particularly

crucial as they are directly involved in the execution and outcome of the project. Therefore, option A

(Internal) is a correct answer as it represents a primary project stakeholder category.

Reference

Business Analysis.pdf, Section on Stakeholder Analysis and Management ​

In Agile methodologies, the role of a Business Analyst (BA) is pivotal in managing requirements. The

Agile BA is responsible for ensuring that the requirements are clearly communicated, prioritized, and

updated as needed throughout the project lifecycle. Keeping the Prioritised Requirements List (PRL)

current and accessible is crucial because it ensures that all team members and stakeholders are

working with the most up-to-date information, which is essential for the iterative nature of Agile

projects. The BA works closely with stakeholders to gather and refine requirements and collaborates

with the development team to ensure that these requirements are understood and can be

implemented effectively. By maintaining the PRL, the BA helps the team stay focused on delivering

the highest value features first, adapting to changes quickly, and ensuring continuous alignment with

business needs. Reference:

Business Analysis document, sections on Agile methodologies and the role of a Business Analyst in

requirement management.