Question 1

The team determines that user stories can help them effectively create the desired outcomes because a well written user story:

Accepted Answer

A

Explanation: A well-written user story is intentionally brief and serves as a "promise for a conversation." Its primary purpose is to articulate a user need from their perspective, thereby initiating a collaborative dialogue among the delivery team, product owner, and stakeholders. This conversation is crucial for exploring the context, clarifying details, defining acceptance criteria, and reaching a shared understanding of the work to be done. The story card itself is not the requirement; the requirement is embodied in the combination of the card, the conversation, and the confirmation (the 3 Cs).

Question 2

In a planning workshop the team breaks down the product backlog increment and can assign work to members of the team. This is referred to as:

Accepted Answer

B

Explanation: The activity described is task planning, which is a core part of iteration planning in agile methodologies. During this event, the delivery team selects a set of product backlog items for the upcoming increment. They then decompose these items (such as user stories) into smaller, more granular tasks required to complete the work. Team members then typically self-assign or are assigned these tasks. This process focuses on how the team will accomplish the selected work within the iteration.

Question 3

The delivery team is reviewing information that starts with a broad view of the solution components
and drills down to a level of granularity, including acceptance criteria, that supports solution build
activities. The team is using the following technique:

Accepted Answer

A

Explanation: The scenario describes the technique of Story Elaboration. This is a just-in-time analysis activity where the team decomposes and refines user stories. It begins with a high-level user story (a broad view) and progressively adds details, clarifies scope, and defines acceptance criteria. The goal is to achieve a shared understanding and create a story that is ready for the delivery team to begin implementation (solution build activities). This process of drilling down into granularity is the core of story elaboration.

Question 4

The delivery team discusses how to maintain the integrity of their backlog items. They decide to?

Accepted Answer

C

Explanation: Maintaining the integrity of an agile backlog means ensuring it remains a relevant, prioritized, and valuable source of work. A key practice in backlog management (or refinement) is to regularly review items to ensure they are still aligned with the current product vision and goals. Monitoring for "staleness" involves identifying items that have not been worked on or discussed for a long time and may no longer be relevant or valuable. This proactive cleanup prevents the backlog from becoming bloated with outdated requests, ensuring the team focuses on delivering current value.

Question 5

The team is assessing feedback from the work that’s been completed. After some discussion they
realize this feedback can be used to assess the remaining components that are yet to be built.
Specifically, this feedback can be used to help them determine if the initiative’s remaining solution
components are:

Accepted Answer

D

Explanation: This scenario describes a fundamental agile principle of using feedback from delivered increments to inform future development. The team is engaging in a learning cycle. By analyzing feedback on what has already been built, they can validate or invalidate the assumptions that underpin the entire solution. This process allows them to determine if the planned remaining components are still relevant, valuable, and aligned with the evolving understanding of stakeholder needs. In essence, they are assessing if the remaining work is "still appropriate" to achieve the desired outcome.

Question 6

While working at the strategy level, the team needs to ensure stakeholders actively support an
environment for constructive communication, collaboration, and continuous improvement. They
decide to use the following to achieve this goal?

Accepted Answer

C

Explanation: Behavior Driven Development (BDD) is a collaborative approach that unites technical and non-technical stakeholders. It uses a shared, natural language format (like Gherkin's Given/When/Then syntax) to create a common understanding of desired system behaviors before development begins. This process inherently fosters an environment of constructive communication and collaboration. By defining acceptance criteria in this clear, unambiguous way, teams can continuously validate that the solution meets the strategic intent, thereby supporting continuous improvement.

Question 7

The team decides a story is too big to do in one iteration. The correct technique to apply at this point is:

Accepted Answer

B

Explanation: When a user story is too large to be completed within a single iteration, the correct agile technique is story decomposition. This process involves breaking down a large story (often called a compound story or an epic) into smaller, more manageable stories. Each resulting smaller story should still be independent, negotiable, valuable, estimable, small, and testable (INVEST). This allows the team to deliver value incrementally, improve estimation accuracy, and reduce the risk associated with large, complex work items.

Question 8

In the past, a team has been unable to deliver solutions in a timely manner and they feel this is due
to the customer being unable to decide what they want. The team has decided to ask the customer
to “sign-off” on their requirements. This violates the following value statement:

Accepted Answer

D

Explanation: The team's decision to enforce a "sign-off" on requirements is a direct shift from a collaborative, partnership-based approach to a more rigid, contractual one. This action is taken to lock down scope and create a formal agreement that can be used to resist future changes, which is characteristic of contract negotiation. It fundamentally undermines the agile value of working closely and continuously with the customer to discover and refine their needs throughout the delivery lifecycle. Instead of collaborating to manage change, the team is creating a process to prevent it, which is the essence of an adversarial, contract-based relationship.

Question 9

Backlog items that are dependent on other backlog items compromise and limit rapid decision making, fast delivery and strategic alignment by not leveraging:

Accepted Answer

A

Explanation: Dependencies in a backlog force work to be done in a specific sequence, often creating large, interconnected batches. This prevents the delivery of small, independent increments of value. The core agile principle of learning and adapting through rapid feedback is compromised because feedback can only be gathered after the entire chain of dependent items is complete. This delay in learning hinders rapid decision-making, slows down overall delivery cadence, and risks misalignment with evolving strategic goals, as adjustments cannot be made based on timely stakeholder input.

Question 10

While quality checking the written user stories, the team ensures one of the components included in the attributes of a user story is:

Accepted Answer

C

Explanation: A well-formed user story traditionally follows the "As a , I want , so that " template. The third component, the "so that" clause, is crucial as it explicitly defines the benefit or business value the user gains upon the story's implementation. This element provides the context and rationale ("the why") for the development team, which is essential for making correct implementation decisions and for prioritizing the story against others. Quality checking ensures this value proposition is clear, as delivering value is a core principle of agile development.

Question 11

At the Initiative Horizon, we see the concept of adaptive planning expressed when a solution owner:

Accepted Answer

C

Explanation: Adaptive planning is a continuous process of adjusting plans based on new information and feedback. At the Initiative Horizon, the focus is on a specific solution or undertaking. The solution owner is responsible for maximizing the value delivered by this initiative. Therefore, the core expression of adaptive planning at this level is using feedback from delivered increments and stakeholder interactions to make informed decisions about the remaining work. This includes prioritizing, modifying, or even discontinuing solution components to ensure the initiative continues to align with organizational goals and deliver maximum value.

Question 12

Planning horizons are important because they allow an organization to:

Accepted Answer

B

Explanation: Planning horizons (Strategy, Initiative, and Delivery) provide a framework that enables an organization to continuously learn and adapt. The Strategy Horizon focuses on understanding the broader business environment to sense opportunities, risks, and necessary changes. The Initiative and Delivery Horizons focus on how to respond to these factors by defining and delivering valuable solutions incrementally. This multi-layered approach to planning allows the organization to adjust its course based on feedback and changing conditions at different cadences, which is the essence of business agility.

Question 13

Agile business analysis focuses on producing something, showing it to stakeholders, and eliciting immediate feedback. This demonstrates the following characteristic of working in an agile context:

Accepted Answer

C

Explanation: The process described—producing an increment, showing it to stakeholders, and eliciting immediate feedback—is the essence of an empirical process. Agile approaches are founded on empiricism, meaning knowledge is gained from experience and decisions are based on what is observed. This iterative loop of "build-measure-learn" or "inspect and adapt" allows teams to test hypotheses, validate their work against real user needs, and adjust their plans based on tangible evidence rather than relying solely on initial assumptions.

Question 14

A product owner has selected a particular workflow, and needs to identify potential epics and
initiatives to learn more about it. They gather a group together to visually identify activities and
themes of possible interest. What technique is typical for this purpose?

Accepted Answer

C

Explanation: Story Mapping is a collaborative technique specifically designed to visualize a user's workflow or journey. A team organizes user activities chronologically to create a narrative flow, often called the "backbone." Underneath these activities, they place detailed user stories. This two-dimensional map provides a holistic view of the product from the user's perspective. It is highly effective for identifying themes, seeing the big picture, and grouping related stories into larger functional blocks like epics and initiatives, which directly addresses the product owner's goal in the scenario.

Question 15

The team demonstrates they value customer collaboration over contract negotiation by:

Accepted Answer

A

Explanation: The Agile Manifesto value "Customer Collaboration over Contract Negotiation" emphasizes creating a continuous partnership with the customer throughout the development process. Constantly refining the team's understanding of the need based on stakeholder feedback is the practical application of this value. This collaborative approach ensures the solution evolves to meet the customer's actual needs, rather than being rigidly confined to initial contractual specifications. It prioritizes the ongoing conversation and feedback loop to deliver maximum value.

Free IIBA IIBA-AAC Actual Exam Questions