IIBA-AAC Questions and Answers

Applying the principle of Avoid Waste at the Strategy Horizon involves ensuring that only the most impactful initiatives are selected for development. By using analysis techniques to deeply understand value propositions for different customer segments, the team can streamline its portfolio, removing or de-prioritizing initiatives that do not clearly contribute to satisfying customer needs. This prevents the organization from investing time and resources into building products or features that customers do not actually want or need. In the agile context, waste is defined as anything that does not add value to the end customer. Streamlining initiatives based on clear value propositions ensures that the delivery pipeline remains focused on high-value work, thereby increasing the overall efficiency and effectiveness of the organization ' s strategic execution.

========= Analysis at the Initiative Horizon is focused on selecting the best path forward to achieve a strategic goal. This requires a rigorous evaluation of potential solution options where assumptions are validated and the projected impact of each solution is carefully assessed. Validating assumptions—often through spikes, prototypes, or user research—reduces the risk of failure by ensuring the solution is based on facts rather than conjecture. Simultaneously, assessing the projected impact helps the team understand how a solution will influence the organization, its customers, and other ongoing initiatives. This dual-focus ensures that the recommended solution is not only feasible but also provides the highest possible value toward the desired outcome, allowing the organization to make informed investment decisions.

===================================

========= Using real-world examples is a cornerstone of the " Get Real Using Examples " principle, which emphasizes the use of tangible scenarios to drive analysis. This approach is particularly effective for gathering feedback on potential solution options because it moves the conversation from the abstract to the concrete. When stakeholders see how a solution would handle a specific, familiar scenario, they are much more likely to provide accurate and insightful feedback regarding its viability and value. This technique helps to validate assumptions and identify risks early in the process. In an agile context, these examples serve as a bridge between elicitation and validation, ensuring that the team doesn ' t just build what was " asked for, " but what is actually needed to solve the problem in a real-world setting.

===================================

In the Business Analysis Core Concept Model (BACCM) , the principle of " Stimulate Collaboration and Continuous Improvement " is most directly aligned with the Stakeholder concept. Stakeholders are the individuals or groups who have a relationship with the change, the need, or the solution. Agile analysis recognizes that value is co-created through the interactions of these people. By stimulating collaboration, the practitioner ensures that diverse perspectives are integrated, which leads to better outcomes and a shared understanding of the goal. Continuous improvement involves stakeholders reflecting on their processes and results to find better ways of working. This human-centric approach prioritizes the " Individuals and Interactions " aspect of the agile mindset, ensuring that the people involved are engaged, informed, and empowered to contribute to the success of the initiative.

===================================

========= At the Initiative Horizon , the goal of effective analysis is to identify solution options that deliver the maximum outcome with the minimum output . This means focusing on the smallest set of features or changes (output) that will satisfy the business need and achieve the desired result (outcome). This concept is central to the agile principle of " maximizing the work not done. " By choosing the most efficient path to value, the team avoids the common pitfall of building unnecessary functionality that adds complexity but not meaningful benefit. This lean approach to solution design ensures that the organization achieves its strategic goals more quickly and with less risk, as each unit of effort is directly linked to a high-impact outcome.

===================================

The agile mindset prioritizes working solutions, but it does not suggest that documentation should be eliminated. Instead, it promotes the idea that documentation should be produced only when it provides clear value and serves a specific, intended person or purpose. In an agile context, any documentation that is not useful for current delivery or future maintenance is considered waste. Practitioners focus on creating " just enough " documentation to facilitate communication, capture critical decisions, or comply with regulatory requirements. By ensuring documentation serves an intended person, the team avoids the trap of creating extensive, unread manuals, thereby maximizing the time spent on activities that directly contribute to the working solution and meet customer needs. This approach maintains a human-centric focus on effective communication over rigid paperwork.

===================================

https://vancouver.iiba.org/sites/vancouver/files/archive/Media/Downloads/CBAP-CCBA%20Study%20Group%202017/Session%208-Chapter%2011_Perspectives.pdf

========= Agile business analysis at the Strategy Horizon focuses on the long-term vision and the continuous evolution of the organization. Practitioners must continually assess the impact of internal and external changes to ensure that the organizational strategy remains relevant. This evolution requires defining multiple potential future states at different time horizons rather than committing to a single, rigid long-term plan. By identifying these various states, the organization can better prepare for different market scenarios and technical shifts. This practice supports organizational agility by allowing leadership to pivot based on which potential future becomes most likely as new information emerges. Ultimately, this high-level modeling ensures that the portfolio of initiatives is always aligned with a viable and valuable future direction.

===================================

Writing detailed user stories and diagrams for an initiative that is six months away is a classic example of creating waste in an agile environment. Agile analysis follows the principle of " just-in-time " elaboration, meaning that detailed work should only be performed when the team is ready to act on it. Requirements and priorities can shift significantly over a six-month period based on market changes, stakeholder feedback from other initiatives, or technological advancements. By documenting everything upfront, the analyst risks producing artifacts that will become obsolete before they are used, leading to wasted effort and " analysis paralysis " . Instead, the analyst should focus on high-level goals at the Strategy or Initiative Horizons, leaving granular details for the Delivery Horizon when the work is imminent and the information is most accurate.

===================================

========= When evaluating multiple solution options, specifically at the Initiative Horizon , it is critical that the team maintains a shared understanding of the need to be satisfied . This shared understanding acts as the baseline for evaluating which option is the most viable and likely to achieve the desired outcome. Without a common view of the problem or opportunity, the assessment of solution paths becomes subjective and inconsistent. By grounding the evaluation in a unified perspective of the business need, the team can objectively compare different architectures, processes, or software components. This ensures that the selected path is not just technically feasible, but is the most effective means of delivering value and satisfying the stakeholder requirements defined at the strategic level.

===================================

========= The principle of Avoid Waste is applied during delivery by ensuring that only the most necessary and valuable stories are refined for upcoming iterations. By evaluating user stories against needs, outcomes, constraints, and risks, the team can identify which items are truly essential and which should be discarded or de-prioritized. Refining stories to a high level of detail too early in the process—especially those that may never be built—is a significant source of waste. Instead, the team focuses their analysis effort on items that have a high probability of providing value and are feasible within the current constraints. This " just-in-time " refinement ensures that the team’s analysis capacity is utilized effectively, focusing only on work that is actionable and directly supports the successful delivery of the solution.

===================================

========= During the Delivery Horizon , the principle of " Analyze to Determine What is Valuable " is operationalized through continuous backlog maintenance and the refinement of user stories. This ensures that the team’s immediate efforts are always directed toward the most high-value items currently identified. As the team completes work and receives feedback, they must constantly reassess the remaining items to ensure they still represent the best way to satisfy the customer ' s needs. This ongoing refinement prevents the team from working on features that have lost their relevance or value, effectively minimizing waste. By keeping the backlog " healthy " and focused on value, the delivery team maintains a high velocity of value delivery and ensures that the solution evolves in a way that provides the maximum benefit to the organization.

===================================

When a team satisfies its current goals early and needs to identify the next set of outcomes to drive, they must consult the Initiative Horizon . The Initiative Horizon is responsible for analyzing and prioritizing various solution options and features that align with the organization ' s strategic goals. It maintains a view of the upcoming " next best " work that has already been evaluated for its potential value and impact. By looking to this horizon, the team can seamlessly transition to a new set of priorities that have been vetted for strategic alignment. This ensures that the team ' s velocity is maintained and that they are always working on the most valuable tasks available, embodying the agile principles of " Avoid Waste " and " Continuous Value Delivery " .

===================================

At the completion of a delivery release, the team engages in a critical assessment of the outcomes achieved to inform the future change strategy . The primary goal is to elicit feedback from stakeholders and end-users to determine if the increments delivered actually satisfied the underlying business need and solved the original problem. This process is not just about verifying that the software " works " technically, but rather validating that it provides the intended value. This feedback loop is essential for the Strategy Horizon and Initiative Horizon to adjust their plans and backlogs. If the released product does not meet the need, the team must learn from this result and adjust their approach for subsequent releases, embodying the agile principle of continuous learning and adaptation.

========= Agile business analysis does not eliminate documentation; rather, it shifts the focus to creating documentation that provides genuine value. Following the value of working solutions over comprehensive documentation , a team should produce artifacts that have an intended purpose, such as supporting current discussions or facilitating necessary future change. This approach ensures that documentation acts as a tool for communication and shared understanding rather than a bureaucratic burden. If a document helps a stakeholder make an informed decision or assists the delivery team in understanding a complex technical requirement, it is considered valuable. By prioritizing purpose-driven documentation, the team avoids waste while ensuring that critical information is preserved and shared effectively across the organization.

===================================

========= Feedback obtained at the end of a delivery cycle is actionable data used to maintain a healthy and relevant backlog. Based on immediate results from testing and customer evaluation, the team may need to create new stories to address gaps, alter existing ones to reflect refined needs, re-prioritize the order of delivery, or remove items that are no longer considered valuable. This process is central to the agile principle of responding to change over following a plan. By updating the backlog frequently based on real performance data, the team ensures that their work remains strictly aligned with the user ' s needs. This iterative refinement prevents the accumulation of waste and ensures that the delivery team is always working on the most accurate and valuable set of requirements available.

===================================

In the Delivery Horizon , analysis work is not just about building the solution but also about continuous learning. While the team handles immediate tasks like clarifying stories or clearing obstacles, they must also focus on learning from this work to avoid similar issues in the future . This is a core part of the " Continuous Improvement " mindset. By reflecting on the challenges faced during a delivery cycle, the team can identify patterns of technical debt, communication gaps, or misunderstood requirements. This learning is then fed back into the team ' s processes (often via retrospectives) to improve velocity and quality in subsequent iterations. This proactive approach to learning ensures that the team becomes more efficient over time, reducing waste and increasing their ability to deliver high-value solution increments with fewer impediments.

===================================

========= The team is utilizing the Real Options technique, which focuses on identifying the best time to make a decision to maximize value and minimize risk. Real Options help practitioners recognize that not every decision needs to be made immediately; some are more valuable if delayed until more information is available. This technique defines " options " that have an expiration date, encouraging the team to commit to a path only when they must or when they have sufficient evidence to do so. By discussing the value of different alternatives and the " last responsible moment " for decision-making, the team avoids premature commitment to a single solution, maintaining flexibility and allowing for more adaptive planning in a complex or uncertain environment.

===================================

=========

Visioning is a technique used to create a shared understanding of the desired future state of a product or initiative. By using a combination of images and words, the team can communicate the goal and scope in a way that is easily understood by all stakeholders. This visual and descriptive representation helps to align the delivery team with the organizational strategy and ensures everyone is working toward the same objective. In an agile environment, a strong vision acts as a " North Star " for decision-making, helping the team evaluate whether new requests or features contribute to the intended outcome. Effective visioning sessions encourage collaboration and creativity, allowing the team to move beyond technical details to focus on the human-centric value the solution is intended to provide.

===================================

========= In agile business analysis, Waste is defined as any activity or output that does not directly contribute to satisfying the current business need or achieving the desired outcome. When faced with a fixed release date and a heavy workload, the Product Owner must identify and remove items that do not provide meaningful value for that specific goal. Even if a feature has potential business value in the future, if it does not serve the immediate initiative, developing it now is considered waste. This focus on " maximizing the work not done " is essential for ensuring timely delivery. By eliminating non-essential items, the team can focus their energy on the high-value stories that are critical for a successful release, thereby increasing the overall efficiency and impact of the delivery effort.

===================================

The Initiative Horizon acts as the bridge between high-level organizational strategy and the specific activities of the delivery team. Its primary purpose is to inform decisions concerning which solution options are viable and which features should be prioritized to satisfy the identified strategic needs. This horizon involves analyzing the potential impact of various initiatives and determining their expected lifespan and the value they will contribute over time. Unlike the Strategy Horizon, which deals with long-term goals, the Initiative Horizon focuses on more immediate, tangible outcomes that can be achieved through specific projects or product increments. It provides the necessary context for the delivery team to understand what they are building and why, ensuring that the work remains aligned with broader business objectives while remaining responsive to changes in priority or feedback.

In an agile context, canceling the initiative is a viable and responsible option when analysis shows that the solution is not delivering the desired outcomes or sufficient value . This follows the principle of " Avoiding Waste " by stopping the consumption of resources on a failing project. Rather than succumbing to the " sunk cost fallacy, " an agile organization uses empirical data from the delivery horizon to pivot or stop work. This allows the enterprise to redeploy its people and budget toward other initiatives that have a higher probability of success or value. Determining when a goal cannot be met is a key function of agile analysis, ensuring that the organization remains focused on strategic priorities and maintains the flexibility to respond to new opportunities or threats.

========= To mitigate the risk of over-production (creating more output than is necessary to satisfy the goal), the team should assess if the need has been met every time a solution component is delivered . This practice is a key application of the " Avoid Waste " principle at the Initiative Horizon . Agile analysis emphasizes delivering the minimum amount of output required to achieve a specific outcome. By stopping to evaluate whether the business need has already been satisfied after each increment, the team can identify the point of diminishing returns. If the goal has been achieved, the remaining work in the backlog can be cancelled or de-prioritized, allowing resources to be redeployed to other high-value initiatives. This continuous assessment ensures that the organization remains efficient and focused on outcomes rather than simply checking off list items.

===================================

========= Identifying effective solution options requires the team to move beyond simply " building things " to " solving problems " . To achieve this, a shared understanding of the underlying business need and the specific desired outcome is mandatory. Without this common ground, the team risks developing solutions that are technically sound but fail to deliver the intended value or address the root cause of the stakeholder ' s problem. This alignment typically occurs at the Initiative Horizon , where analysis focuses on comparing different ways to satisfy a need. By maintaining focus on the outcome rather than a fixed output, the team can remain flexible and creative, evaluating various paths (such as manual processes, software changes, or third-party tools) to ensure the selected option provides the highest return on investment for the organization.

===================================

========= At the Strategy Horizon , the primary goal of analysis is to facilitate decision-making regarding the organization ' s portfolio of work. Therefore, the team should only develop enough detail to allow stakeholders to prioritize the initiative against other competing goals within the enterprise. Excessive detail at this stage is considered waste because strategic priorities can shift rapidly, and detailed requirements developed too early are likely to become obsolete. Analysis at the strategic level focuses on high-level outcomes, potential value, and broad estimates rather than specific features. This level of granularity provides just enough information for executives to determine if an initiative is worth pursuing or if resources should be allocated elsewhere, maintaining organizational agility and ensuring that delivery teams are always working on the most valuable strategic priorities.

===================================

Change is the act of transformation in response to a need. Change works to improve the performance of an enterprise. These improvements are deliberate and controlled through

business analysis activities.