IIBA Updated IIBA-AAC Exam Questions and Answers by brielle

Planning Stakeholder Engagement is the business analysis task focused on identifying the right participants for an initiative and determining the best methods to involve them. In an agile context, this task is critical for establishing effective communication channels between the delivery team and those who will actually use or be impacted by the solution. Identifying " frontline " stakeholders—those who have direct interaction with the problem or opportunity—ensures that the feedback received is empirical and grounded in real-world scenarios. This proactive engagement allows practitioners to capture diverse perspectives, foster a culture of collaboration, and ensure that the product vision remains aligned with user needs. By planning how and when to engage these individuals, the team can ensure that feedback loops are timely and that the solution is continuously refined based on meaningful stakeholder input.

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

Value stream mapping complete, fact-based, time-series representation of the stream of activities required to deliver a product or service.

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.

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

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

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