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

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.

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.

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.

A requirement in the context of Agile Business Analysis is understood as a service, function, or feature that a user needs. This definition encompasses the broad spectrum of what a requirement can entail, focusing on what the system or product must provide to meet the user's needs. By defining requirements this way, it ensures that the focus remains on the capabilities and functionalities that are necessary to deliver value to the user, rather than on specific solutions or objects which might limit the scope of what can be developed. Reference: Business Analysis document, sections on requirement definitions and user needs.

evel end-to-end prototype of the solution to be

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