Free Agile Analysis Certification Exam IIBA-AAC Exam Practice Test

The team establishes ground rules for considering business analysis performance improvements. They agree that speed and accuracy of executing analysis activities becomes very important at the following horizon:

• Feedback horizon
• Strategy horizon
• Initiative horizon
• Delivery Horizon

During a team meeting, the team discuss a technique where real or perceived benefits to the customer, direct costs and opportunity costs are assessed. Which technique are they discussing?

• Minimum Viable Product
• Impact Mapping
• Kano Analysis
• Value Modeling

When recommending solution options at the Initiative Horizon, the team decides that their goal is to provide decision makers with:

• The exact cost and timeframe options will take to complete
• Just enough information to make an informed and accurate decision
• The list of stakeholders that are allowed to have input
• Everything known about the resource team doing the delivery

The team discusses the agile principle of avoiding waste and decide it's important because it allows the team to:

• Verify that the budget is aligned with spending
• Focus on items that contribute to satisfying the need
• Ensure clear and effective communication
• Demonstrate ongoing quality backlog refinement

The team is making important decisions when assessing the initiative they are working on. Feedback received from the Delivery Horizon informs:

• Priority and sequencing of solution components
• Identification of reporting requirements
• Suggestions for team process continuous improvement
• How to build the required solution components

A team has been delivering a steady stream of small value increments towards a goal for 4 months, and has completed several solution components, with several still potentially doable. The solution owner examines the reactions to the delivered components from customers, and decides which one(s) the team will do next. The solution owner is demonstrating:

• Adaptation to revised strategy
• Change in response to feedback and learning
• Action in response to activity
• Maintenance of solution alignment

The team is prioritizing stories in the backlog and discussing the elements that result in a well-structured, actionable backlog. They identify the following as a central consideration:

• Accessibility of key stakeholders for signoff
• Rapid delivery of value
• Refining the personas used
• How many features are in the backlog

The team decides a story is too big to do in one iteration. The correct technique to apply at this point is:

• MoSCoW approach
• Story decomposition
• Epic analysis
• Story partitioning

When decomposing stories, the concept of ''breadth before depth'' signifies progressively breaking down:

• Estimates and resources required to accomplish the story
• Backlog items to the lowest level of detail upfront
• Business goals into user stories representing smaller increments of value
• Tests to align with usable functionality delivered through each story

At the strategy level, a major component of waste can be avoided by ensuring the enterprise:

• Only begins an initiative when a budget is approved for all work
• Has a shared understanding of organizational goals and priorities
• Has changes to existing work approved by senior management
• Has comprehensive business cases approved by senior management