IIBA IIBA-AAC - IIBA Agile Analysis Certification

In the Strategy Horizon , practitioners operate in a high-level environment often characterized by a surplus of complex information. Effective analysis at this level involves filtering through this noise to interpret new information—such as market shifts, competitor moves, or internal performance data—and identifying what is truly important for the organization ' s future direction. By providing this clarity, agile business analysis enables stakeholders to make informed, data-driven decisions regarding which strategic goals to pursue and which initiatives to fund. This " sensing and responding " capability is vital for organizational agility, as it allows the enterprise to adapt its strategy in real-time based on meaningful insights rather than outdated plans. This focused interpretation ensures that the organization remains competitive and continues to deliver value in a rapidly changing environment.

A Spike is a time-boxed research activity used by agile teams to gain enough information to resolve technical uncertainty or provide a more accurate estimate for a complex backlog item. In this scenario, the broad disagreement regarding the estimate indicates that the team lacks a shared technical understanding of the implementation details. By dedicating a small amount of time (4 hours) to investigation, the team follows the principle of " Understand What is Doable " by grounding their estimates in empirical findings rather than guesswork. Spikes help mitigate risk early in the delivery cycle and prevent the team from committing to work they do not fully understand. Once the research is complete, the findings are shared with the broader team, allowing for a collaborative and informed estimation during subsequent planning or refinement sessions.

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

In constant and rapidly changing environments, organizations are required to be able to sense and respond to local opportunities and problems without the need to involve the whole organization, while also looking forward at emerging threats and opportunities. These planning horizons provide a framework for the shift in focus that occurs when moving between understanding the long-term strategic needs of the organization and the immediate needs of a customer.

Personas are archetypal representations of users used to understand their goals, behaviors, and pain points. While personas can be established during strategy sessions, they are most heavily utilized at the Initiative Horizon to help model customer needs and guide the development of specific solution components. At this level, the team uses personas to refine features, prioritize the backlog, and evaluate which solution options will provide the most value to specific user segments. This technique ensures the team " Thinks as a Customer, " preventing the development of generic functionality that fails to resonate with actual users. By applying personas at the Initiative Horizon, the team creates a more targeted product vision and ensures that the criteria for success are directly linked to the user ' s experience and business outcomes.

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

========= The decision to cancel remaining work on an initiative is a direct application of the " See the Whole " principle. This principle encourages the team to look beyond local tasks and consider the entire system and the overarching goals of the organization. If the team determines that the desired value has already been achieved or that the remaining components will not provide sufficient additional benefit to justify the cost, they must have the courage to stop. " Seeing the Whole " allows the team to recognize that continuing a low-value initiative is a waste of organizational resources that could be better utilized elsewhere. This holistic view ensures that the enterprise portfolio remains optimized for value delivery and that the team’s efforts are always aligned with the most significant needs of the business.

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

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.