AAC Practice Exam — AAC：Agile Analyst

The product roadmap is a core agile analysis artifact defined in the IIBA Agile Analysis Certification (AAC) body of knowledge, which outlines the sequential delivery of product increments over time to deliver on long-term product outcomes. The primary value of the roadmap for delivery teams is that it creates a clear line of sight between each discrete delivery increment and the overarching product vision, ensuring the team’s work consistently contributes to intended product goals rather than focusing on siloed, disconnected tasks. This aligns directly with the agile emphasis on outcome-driven delivery rather than rigid adherence to scope or timelines. Option Analysis: A. Incorrect. Aligning strategy to goals is a function of upper-level business and product strategy activities that occur before the product roadmap is developed. The roadmap assumes strategy and goals are already agreed upon, so it does not serve to align these two elements. B. Incorrect. Agile product roadmaps are intentionally adaptive and evolve as stakeholder feedback and market conditions change, so they are not designed to lock in or maintain a fixed, defined scope. Maintaining fixed scope is a practice associated with predictive, not agile, delivery approaches. C. Incorrect. Product roadmaps are high-level planning artifacts that do not contain granular task-level scheduling details required to keep a delivery team on day-to-day or iteration-level schedules. That function is served by lower-level artifacts such as sprint backlogs and iteration plans. D. Correct. Per IIBA AAC guidance, the core purpose of an agile product roadmap is to sequence planned delivery increments in a way that directly maps to the product vision. This ensures every increment the team delivers moves the product closer to its intended long-term state, eliminating misalignment between delivery work and core product objectives. Key Concepts: 1. Agile Product Roadmap: An adaptive, high-level artifact in agile analysis that communicates planned product progression, balancing near-term delivery details with long-term outcome alignment to support stakeholder alignment and delivery team direction. 2. Product Vision Alignment: A foundational agile analysis responsibility to ensure all delivery activities and outputs contribute to the agreed-upon long-term product purpose, a goal directly supported by the product roadmap. 3. Outcome-Driven Planning: An agile core principle that prioritizes delivery of measurable business and user outcomes over adherence to fixed scope or timelines, which the product roadmap enables by linking increments to vision rather than fixed requirements. References: IIBA Agile Extension to the BABOK® Guide (v3), IIBA Agile Analysis Certification (AAC) Official Page

This scenario aligns with core IIBA Agile Analysis Certification (AAC) principles centered on iterative value delivery and feedback integration. The team has been delivering incremental solution components over 4 months, and the solution owner is explicitly using direct customer reactions to delivered components (feedback) and accumulated learning about what customers value to prioritize upcoming work. This practice is a foundational element of agile analysis, where decisions about subsequent work are rooted in empirical evidence from delivered value rather than static upfront plans, making the suggested answer B the correct choice. Option Analysis: A. Adaptation to revised strategy: Incorrect. The scenario does not reference any change to the overarching organizational or solution strategy; the team is still working toward the same original goal, just adjusting the order of component delivery. There is no evidence of a strategy revision to trigger this adaptation, so this option does not match the scenario. B. Change in response to feedback and learning: Correct. Per IIBA AAC domain knowledge, agile analysis relies on continuous feedback from stakeholders and customers on delivered increments to build learning about value delivery. The solution owner’s decision to select next work items based directly on customer reactions to already delivered components is a clear example of adjusting work priorities in response to collected feedback and the team’s accumulated learning about customer needs, exactly matching this option. C. Action in response to activity: Incorrect. This option is overly vague and does not capture the specific driver of the solution owner’s action. The action is not a response to generic work activity, but a deliberate choice rooted in targeted customer feedback. The IIBA AAC framework emphasizes intentional, feedback-driven decision making rather than generic response to activity, so this option is not appropriate. D. Maintenance of solution alignment: Incorrect. Maintenance of solution alignment refers to ongoing checks to ensure work remains aligned to the pre-defined solution vision and business objectives. The scenario does not mention addressing misalignment to an existing vision, nor is the solution owner’s action focused on confirming alignment. Instead, the action is focused on evolving priorities based on new customer input, so this option does not fit. Key Concepts: 1. Continuous Stakeholder Feedback: A core AAC knowledge area principle that requires frequent, iterative collection of input from customers and end users on delivered solution increments to ensure the solution remains focused on delivering maximum user value. The scenario explicitly uses customer feedback on delivered components to drive next steps, which directly applies this concept. 2. Adaptive Priority Setting: An agile analysis practice defined in the AAC body of knowledge where work priorities are adjusted on an ongoing basis based on new empirical evidence, rather than following a static upfront project plan. The solution owner’s choice of next components based on recent customer input is a direct implementation of this practice. 3. Empirical Value Determination: A foundational AAC principle that holds that the actual value of solution components can only be confirmed after delivery to users, and this observed value should be the primary input for prioritizing future work. This scenario relies on observed customer reaction (empirical evidence of value) to select upcoming work, aligning with this concept. References: Agile Extension to the BABOK® Guide (Version 3), IIBA Agile Analysis Certification (AAC) Official Page

The scenario describes a common backlog refinement use case in agile analysis where a user story is assessed as too large to be completed within a single iteration. Per IIBA Agile Analysis Certification (AAC) core domain knowledge, the standard technique applied in this scenario is story decomposition, which involves breaking the oversize story into multiple smaller, independent user stories that each meet the INVEST criteria, deliver tangible incremental business value, and are sized to fit within the team's iteration capacity. This practice aligns with the AAC's focus on adaptive planning, iterative value delivery, and maintaining a backlog of actionable, iteration-ready work items. Option Analysis: A. The MoSCoW approach is a prioritization framework used to categorize backlog items by business criticality (Must have, Should have, Could have, Won't have) for a given release or iteration. It does not address the issue of a story being too large for an iteration, so this option is incorrect. B. Story decomposition is the formal agile analysis technique defined in the IIBA Agile Extension to the BABOK Guide for breaking overly large user stories into smaller, iteration-sized, value-bearing work items that each meet INVEST criteria. This directly resolves the core issue presented in the scenario, so this option is correct. C. Epic analysis is the practice of defining high-level scope, business outcomes, and success criteria for very large bodies of work (epics) that typically span multiple releases or cross-functional teams. It is applied to far larger work items than a single oversize user story and does not focus on splitting a story to fit a single iteration, so this option is incorrect. D. Story partitioning is not a formally recognized technique in IIBA AAC domain knowledge for addressing oversize user stories. While the term may be used informally to describe separating stories by functional or user segments, it is not the standard accepted practice for the scenario provided, so this option is incorrect. Key Concepts: 1. Backlog Refinement: An ongoing core agile activity where agile analysis practitioners and cross-functional teams review backlog items, adjust sizing estimates, prioritize work, and decompose oversize items to ensure the backlog contains ready, actionable work for upcoming iterations. 2. INVEST Criteria: A standard set of attributes for well-formed user stories, where the "S" (Small) explicitly requires stories to be small enough to complete within a single iteration. Stories that do not meet this requirement must be decomposed to be usable for iteration planning. 3. Iteration Capacity Planning: The practice of aligning backlog item size with the team's proven capacity to complete work within a single iteration, which drives the need to identify and decompose oversize stories during backlog refinement. References: Agile Extension to the BABOK Guide (v2), IIBA Agile Analysis Certification (AAC) Official Page

The IIBA Agile Analysis Certification (AAC) validates core agile analysis competencies that prioritize value delivery and adaptive decision-making in agile environments. In the presented scenario, the team uses real-time feedback confirming their scheduled deliverables are not driving progress towards their intended business goal. Instead of rigidly executing their pre-planned work schedule that would deliver minimal ongoing value, they immediately pivot their delivery focus to a higher-impact initiative while evaluating improvements to the underperforming work. This behavior directly aligns with the core agile value emphasized in the AAC body of knowledge of adapting to emerging information rather than adhering to outdated plans that no longer deliver meaningful business outcomes. Option Analysis: A. Documenting solution outcomes: This option is incorrect. The scenario does not reference any activity related to capturing, formalizing, or storing records of solution performance outcomes. The team’s primary action is adjusting their delivery plan rather than completing documentation tasks, so this is not their highest valued priority in the described situation. B. Developing new processes: This option is incorrect. There is no mention of the team creating, revising, testing, or implementing new work processes in the scenario. Their action centers on shifting existing work priorities, not modifying operational processes, so this is irrelevant to the described behavior. C. Improving collaboration: This option is incorrect. The scenario does not include any details related to enhancing cross-team communication, stakeholder alignment, or collaborative workflows as part of the team’s decision. Collaboration is not the focus of the action taken, so this is not the correct choice. D. Responding to change: This option is correct. The team’s decision to abandon pre-planned low-value work and pivot to higher impact delivery based on real-time performance feedback is a direct demonstration of prioritizing response to change, a core agile value and key competency tested in the IIBA-AAC certification. The team prioritizes adapting to new information about their work’s impact over following a static, unproductive work plan. Key Concepts: 1. Agile Manifesto Core Value: Responding to Change Over Following a Plan. This is one of the four foundational values of agile, heavily tested in the AAC certification, which states that teams should prioritize adapting to emerging feedback and requirement changes rather than rigidly adhering to pre-defined plans even when they no longer deliver value. 2. Adaptive Analysis: A core AAC competency that describes the practice of continuously adjusting analysis and delivery activities based on ongoing feedback about solution performance, business value, and goal alignment, to ensure work consistently drives desired business outcomes. 3. Outcome-Focused Delivery: A key AAC principle that directs teams to prioritize delivery of measurable business outcomes over completion of arbitrary deliverables, which guided the team in this scenario to abandon work that was not driving their stated goal. References: Agile Extension to the BABOK Guide (v3), Manifesto for Agile Software Development, https://agilemanifesto.org/

The IIBA-AAC body of knowledge defines the Delivery Horizon as the set of iterative, time-boxed work cycles focused on delivering incremental, usable value to stakeholders. For this horizon, team communication norms prioritize predictability to minimize disruptive context switching, ensure all team members and relevant stakeholders can plan to attend required updates, and maintain consistent alignment on delivery progress, blockers, and feedback. The suggested answer D aligns with this requirement, as consistent, scheduled communication matches standard agile delivery practices including fixed-cadence daily standups, iteration planning sessions, review meetings, and retrospectives that are standard for the Delivery Horizon. These scheduled, consistent events eliminate unplanned interruptions to delivery work while ensuring all parties receive timely, relevant information. Option Analysis: A. Incorrect. While clarity is a general positive trait for all business analysis communication, "clear or reviewed" is a generic communication standard, not a specific norm defined for Delivery Horizon communication in the IIBA-AAC framework. The phrase "or reviewed" is also irrelevant to Delivery Horizon team norms, as formal review of all communication is not a required practice for this horizon. B. Incorrect. "Appropriate and planned" is a broad communication requirement that applies across all three IIBA-AAC horizons (Strategy, Initiative, Delivery), not a specific norm unique to Delivery Horizon team agreements. This option is too vague and does not capture the key priority of consistent, recurring cadence that defines Delivery Horizon communication. C. Incorrect. Casual, as-needed communication leads to unplanned interruptions that disrupt delivery work, risks misalignment if key stakeholders are not available for impromptu conversations, and fails to ensure consistent updates across the full team. This type of communication may be used for minor, one-off ad-hoc queries but is not the established norm for formal team communication in the Delivery Horizon per IIBA-AAC guidelines. D. Correct. As outlined in the IIBA-AAC body of knowledge, Delivery Horizon work is structured around fixed, consistent iteration cadences. All core team communication events are scheduled in advance and held at consistent intervals to create predictable information flow, reduce context switching for delivery team members, and ensure all required participants can plan to attend updates. This directly matches the "consistent or scheduled" requirement defined for Delivery Horizon team communication norms. Key Concepts: 1. Delivery Horizon: One of three core horizons in the IIBA-AAC framework, focused on iterative, time-boxed delivery of incremental value, with process and communication norms designed to support steady, uninterrupted delivery and regular stakeholder alignment. 2. Agile Team Norms: Formal, team-agreed rules that govern interaction and communication to reduce friction, improve alignment, and increase productivity. For delivery teams, these norms explicitly define communication cadence to avoid disruptive ad-hoc requests. 3. Iteration Cadence: The fixed, consistent length of delivery cycles (e.g. 1 or 2 week sprints) that serves as the basis for scheduling all core Delivery Horizon communication events, ensuring consistent, predictable updates for all stakeholders. References: Agile Extension to the BABOK Guide (v3), IIBA Agile Analysis Certification (AAC) Handbook