Agile Business Analysis Common Agile Analysis Techniques 2

Question 1

A business analyst is facilitating a story mapping session. What is the PRIMARY purpose of the horizontal axis in a story map?

Accepted Answer

Represent the sequence of user activities over time

Answer

The horizontal axis in a story map represents the narrative flow of user activities in the order they occur.

Question 2

Which technique involves asking 'why' repeatedly to drill down to the root cause of a problem during agile analysis?

Accepted Answer

5 Whys

Answer

The 5 Whys technique iteratively asks 'why' to peel back symptom layers and expose the true root cause.

Question 3

During backlog refinement, a BA uses MoSCoW prioritization. A feature labeled 'Could Have' means:

Accepted Answer

It should be delivered if time permits but is not critical

Answer

'Could Have' items are desirable but not critical, and are only included when time and resources allow.

Question 4

A product owner wants to validate assumptions about user behavior before building a feature. Which agile analysis technique is MOST appropriate?

Accepted Answer

Prototyping and usability testing

Answer

Prototyping and usability testing allow teams to validate assumptions about user behavior with minimal build investment.

Question 5

In Behavior-Driven Development (BDD), the Given-When-Then format is used to:

Accepted Answer

Express acceptance criteria in a testable, human-readable format

Answer

Given-When-Then structures acceptance criteria as scenarios that describe system behavior in plain language understandable by all stakeholders.

Agile Business Analysis Practice Test