APMG-International AgileBA (Agile Business Analysis) Foundation (2015) Exam 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

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.

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.