Common Agile Analysis Techniques Flashcards

An Agile team is building a new e-commerce platform that will serve both tech-savvy young adults and less-technical older adults. To ensure the design and features meet the distinct needs of these groups and to foster empathy within the team, which technique should the business analyst recommend?

Answer: Creating Personas

Personas are semi-fictional representations of a product's key user segments. [9] They are created based on user research to help the team understand user characteristics, needs, and goals. [7] This technique is ideal for building empathy and ensuring that development decisions are made with a clear picture of the end-user in mind, which is crucial when serving diverse user groups. [6, 19]

What is the primary purpose of creating an Impact Map during an agile inception or planning phase?

Answer: To visually connect specific deliverables to business goals, showing how features impact key actors and objectives.

Impact Mapping is a strategic planning technique that visually links a central business goal to the actors (who can influence it), the impacts (how their behavior should change), and the deliverables (what the team will build to enable those impacts). [3, 5] Its primary purpose is to ensure that all development effort is explicitly tied to achieving measurable business outcomes. [2, 4]

A product owner is struggling to prioritize features for a new mobile banking app. Some features are basic expectations (e.g., check balance), while others could be unexpected delights (e.g., AI-powered savings advice). Which analysis technique is specifically designed to categorize features based on their potential to satisfy or delight customers?

Answer: Kano Model

The Kano Model is a prioritization framework that classifies product features into categories based on how they affect customer satisfaction. [12] These categories include Must-be (basic expectations), Performance (more is better), and Attractive (delighters), helping teams make strategic decisions about which features will provide the most value and positive emotional response from users. [11, 20]

An Agile team has a large user story, 'As a user, I want to manage my entire account profile,' which is too big to complete in a single iteration. Which of the following is the MOST important reason for the business analyst to facilitate splitting this story into smaller, independent pieces?

Answer: To enable a faster feedback loop by delivering value incrementally.

The primary agile rationale for splitting large stories is to deliver smaller, valuable increments of functionality more quickly. [1, 16] This allows the team to get a working piece of the feature to stakeholders and users sooner, enabling a faster feedback loop that can guide future development and reduce the risk of building the wrong thing. [8, 14]

A team is experiencing significant delays in their 'idea-to-production' cycle. The business analyst suspects there are bottlenecks, such as long waits for testing environments or manual deployment processes. Which technique is BEST suited for visualizing the entire workflow, identifying waste, and optimizing the flow of value?

Answer: Value Stream Mapping

Value Stream Mapping (VSM) is a lean technique used to analyze the end-to-end flow of work required to deliver a product or service to a customer. [26] It is specifically designed to visualize the process, identify bottlenecks, quantify delays, and highlight non-value-added activities (waste), making it the ideal tool for improving the overall efficiency of a delivery cycle. [18, 22]

An Agile business analyst is writing acceptance criteria using the 'Given/When/Then' syntax. What is the primary benefit of using this format, which is central to Behavior Driven Development (BDD)?

Answer: It provides a clear, unambiguous specification of behavior that can be understood by business, development, and testing roles.

The Gherkin (Given/When/Then) syntax creates a shared, ubiquitous language for describing a feature's behavior without detailing its implementation. [28, 32] This format is easily understood by non-technical stakeholders (like product owners) and technical team members (developers, testers), fostering collaboration and creating a single source of truth for requirements that can also serve as a basis for automated tests. [24, 25]