The IIBA Agile Analysis Certification (IIBA-AAC)

========= 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.

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

The INVEST acronym (Independent, Negotiable, Valuable, Estimable, Small, Testable) is a standard used to evaluate the quality of user stories. The " I " specifically stands for Independent , meaning that a story should be self-contained and free from strict dependencies on other stories. Independence is vital in agile analysis because it allows the Product Owner to re-prioritize the backlog without triggering a cascade of planning changes. When stories are independent, the delivery team can work on them in any order that maximizes value, facilitating a more flexible and responsive delivery process. Reducing dependencies minimizes the risk of bottlenecks and allows for the incremental release of features, ensuring that each story represents a distinct unit of business value that can be validated and deployed on its own merits.

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

========= In addition to initial estimates of business value, a Product Owner must prioritize the backlog based on what they learn from delivered stories . Agile delivery is an empirical process where each completed increment provides new data about technical feasibility, user preferences, and business impact. This continuous learning often reveals that some remaining stories are more important than originally thought, while others may no longer be necessary at all. By incorporating these insights into the prioritization process, the Product Owner ensures that the backlog remains a dynamic and accurate reflection of the most current understanding of value. This responsive prioritization is essential for navigating the uncertainty of complex projects and ensuring that the delivery team is always focused on the work that matters most at that moment.

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.

Kano Analysis is a specialized technique used to categorize product features based on their impact on customer satisfaction. When determining the scope of a Minimum Viable Product (MVP) , Kano Analysis helps the team identify " Threshold " or " Must-be " characteristics. These are the baseline features that, if omitted, will cause intense customer dissatisfaction and render the product unviable. By focusing on these threshold features alongside high-impact performance features, the team can define the smallest possible set of functionality that provides value and satisfies the core customer need. This prevents " scope creep " and ensures that the team does not waste time on " delighter " or " excitement " features until the core viability of the product has been proven in the market. This strategic prioritization is central to agile delivery and resource optimization.

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

When a team loses track of how their daily work connects to the broader goals, the Product Roadmap is the most effective artifact to assess . The roadmap acts as a bridge between the Strategy Horizon and the Delivery Horizon , visualizing the high-level path toward the product vision over time. Unlike a detailed backlog, the roadmap focuses on themes, major features, and strategic milestones. By reviewing the roadmap, the team can see where their current features fit into the " Big Picture " and how they contribute to achieving organizational objectives. This realignment helps the team refocus on Value and Outcomes , ensuring that their technical efforts remain purposeful and that they are delivering increments that actually move the needle on the product ' s long-term success.

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

========= In the Strategy Horizon , organizations often face external pressures such as new competitive threats. To mitigate the risk of making poorly defined or reactive decisions, the agile analysis principle of " Get Real Using Examples " is applied to identify and assess the impact of these changes. By using concrete examples of how a competitor’s move or a market shift affects the organization ' s value proposition, stakeholders can better visualize the threat and its consequences. This practice moves analysis from abstract theory to tangible impact assessment, allowing the organization to pivot its strategy based on empirical evidence rather than guesswork. Constantly assessing these changes ensures that the portfolio of initiatives remains relevant and that the organization can sense and respond to threats in a timely, effective manner.

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

Creating common customer scenarios is a direct application of the principle " Get Real Using Examples " . This principle encourages teams to move from abstract requirements to concrete, real-world situations to ensure a shared understanding of how a solution will be used. Scenarios act as tangible examples that help stakeholders visualize functionality, allowing them to provide more accurate feedback during elicitation and refinement sessions. This practice reduces ambiguity and helps the team identify edge cases or business rules that might otherwise be overlooked. By using these examples, the team can validate that the user stories in the backlog actually address the practical challenges faced by the customer, ensuring the final output delivers genuine value and solves the intended business problem.

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