IIBA Updated IIBA-AAC Exam Questions and Answers by jeremiah

=========

Planning Stakeholder Engagement is a critical task that involves identifying the right individuals to participate in the agile process. The goal is to find stakeholders who can provide specific, detailed feedback and who will be the primary users of the final solution. In an agile environment, direct interaction between the delivery team and these stakeholders is essential for validating assumptions and refining the product backlog. By planning how and when to engage these individuals, the practitioner ensures that the feedback loop is efficient and that user needs are captured accurately. Effective engagement planning fosters collaboration, builds trust, and ensures that the solution being developed is human-centric. This proactive involvement of the right people reduces the risk of rework and ensures that the delivered increments truly meet customer expectations.

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

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

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.

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