Important APMG-International AgileBA-Foundation Exam Questions

Answer: B

Explanation:

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.

Answer: C

Explanation:

The primary purpose of a business case is to justify the investment in a project. This justification involves providing a rationale for why the project should be undertaken, detailing the benefits that are expected to be realized, and explaining how these benefits align with organizational goals and strategies. The business case will typically include:

Executive Summary: A brief overview of the project and its strategic importance.

Problem Statement: Explanation of the issue or opportunity that the project addresses.

Options Considered: Different approaches to solving the problem or seizing the opportunity, including a preferred option.

Cost-Benefit Analysis: Detailed financial analysis showing the costs and benefits associated with the project.

Risk Assessment: Identification and evaluation of risks, with plans for mitigating them.

Implementation Timeline: A high-level schedule for the project's execution.

The business case does not focus on confirming delivery, describing accrued benefits post-implementation, or capturing learning points from project increments, as these are aspects related to project execution and post-implementation review.

Business Analysis.pdf: Detailed sections on what constitutes a business case, emphasizing justification of investment through cost-benefit analysis and alignment with business strategy.

Answer: C

Explanation:

In Agile methodologies, a Theme is a collection of related User Stories and/or Epics. Themes help to organize and manage work at a higher level, grouping related stories and epics together to ensure that the development efforts are aligned with broader business objectives or goals. This hierarchical structuring allows teams to see how individual user stories fit into larger business initiatives and ensures that the work is aligned with the overall strategy. By using Themes, teams can manage complex projects more effectively, ensuring that related functionalities are developed in a coordinated manner. Reference: Business Analysis document, sections on the hierarchy of user stories and Agile planning.

Answer: D

Explanation:

The main focus of Impact Mapping is on benefits and goals. This technique helps to visualize the connections between the high-level goals of an organization and the specific actions that will help achieve those goals. It involves identifying the key stakeholders, the changes needed to meet their needs, and the specific deliverables that will contribute to the overall objectives. Impact Mapping ensures that all activities are aligned with the strategic goals of the organization.

Reference: Business Analysis.pdf, Chapter 14, Delivering the Business Solution

Answer: D

Explanation:

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.

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