IIBA-AAC flashcards
IIBA-AAC · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Strategy horizon
- The analysis horizon concerned with understanding the enterprise, defining a vision, and identifying potential value before committing to a change initiative.
- Initiative horizon
- The analysis horizon where the scope of a change is defined, a product roadmap is created, and the backlog is prioritized to deliver value.
- Delivery horizon
- The analysis horizon where requirements are elaborated just in time, the team is supported, and the solution is validated against stakeholder needs.
- See the whole
- An agile analysis principle meaning the analyst considers the enterprise, the solution, and the context together rather than optimizing a single part in isolation.
- Think as a customer
- An agile analysis principle requiring the analyst to understand what customers value and to use that perspective to guide analysis and prioritization decisions.
- Analyze to determine value
- An agile analysis principle stating that analysis effort should focus on discovering and defining what is valuable to stakeholders, not documenting everything.
- Get real using examples
- An agile analysis principle that uses concrete examples, such as given-when-then scenarios, to clarify requirements and reduce ambiguity in communication.
- Understand what is doable
- An agile analysis principle that requires the analyst to consider technical feasibility, team capacity, and constraints when defining and prioritizing work.
- Stimulate collaboration and improvement
- An agile analysis principle encouraging the analyst to foster teamwork, shared understanding, and continuous improvement across the product lifecycle.
- BACCM
- The Business Analysis Core Concept Model with six concepts: change, need, solution, stakeholder, value, and context, used to frame analysis in any horizon.
- Product vision
- A concise statement of the desired future state that guides strategy and initiative decisions; it describes the value the product will deliver to customers.
- Minimum viable product
- The smallest version of a product that delivers enough value to early customers to generate validated learning; used to test assumptions before further investment.
- Product roadmap
- A high-level plan showing how a product will evolve over time to achieve the vision; it communicates direction and priorities without committing to detailed dates.
- Backlog
- An ordered list of work items, such as user stories, that the team may deliver; the analyst helps keep it prioritized by value and refined for readiness.
- Backlog refinement
- The ongoing activity of reviewing, updating, and detailing backlog items so they are ready for the team when needed; also called backlog grooming.
- User story
- A short, simple description of a feature told from the perspective of the person who desires it, typically in the form: as a role, I want a goal so that benefit.
- Acceptance criteria
- Conditions that a product backlog item must satisfy to be accepted by the stakeholder; they clarify intent and support testing and validation.
- Definition of done
- A shared checklist of criteria that a backlog item must meet before the team considers it complete; it supports consistent quality and transparency.
- Given-when-then
- A format for expressing acceptance criteria using a scenario: given a context, when an action occurs, then an expected outcome results; it reduces ambiguity.
- Just-in-time elaboration
- Detailing requirements only when they are about to be implemented, rather than upfront, to avoid waste and accommodate learning and change.
- Iterative analysis
- Performing analysis in repeated cycles, refining understanding and outputs each time, instead of attempting to define everything completely at the start.
- Continuous delivery
- An approach where the team keeps the solution in a releasable state and delivers value frequently, supported by analysis that is ongoing rather than phase-bound.
- Value
- In the BACCM, the worth or importance of something to a stakeholder; analysis aims to identify, define, and maximize value across horizons.
- Stakeholder
- In the BACCM, a person or group with a relationship to the change, need, or solution; the analyst identifies and engages them appropriately.
- Context
- In the BACCM, the circumstances and environment that influence and are influenced by the change; analysis must consider context in every horizon.
- Need
- In the BACCM, a problem or opportunity of importance to stakeholders that motivates a change; needs are analyzed to determine value and solution options.
- Change
- In the BACCM, an act of transformation in response to a need; the analyst helps define and manage change across strategy, initiative, and delivery.
- Solution
- In the BACCM, a specific way of satisfying one or more needs in a context; analysis evaluates and defines solutions that deliver value.
- Business model canvas
- A strategic management template for describing, analyzing, and designing business models; used in the strategy horizon to visualize value creation and delivery.
- Persona
- A fictional representation of a user type based on research, used to keep analysis focused on customer needs and to guide story writing and prioritization.
- Story mapping
- A technique that arranges user stories along a user journey to show the big picture and to slice releases; it supports prioritization and scope decisions.
- Minimum marketable feature
- The smallest feature set that delivers meaningful value to customers and can be marketed; used in the initiative horizon to scope releases.