FREE Agile Business Analysis Process Questions and Answers Flashcards

In Agile business analysis, what is the main benefit of using story mapping as a process planning tool?

Answer: It visualizes the user journey and helps prioritize features by identifying the minimum viable product

Story mapping arranges user stories along a narrative flow, making it easier to identify which features constitute the minimum viable product and should be built first.

Which Agile business analysis practice best supports continuous stakeholder alignment throughout a project?

Answer: Regularly scheduled showcase sessions where working increments are demonstrated

Showcase sessions provide stakeholders with hands-on exposure to working software, enabling real-time feedback and ongoing alignment with business objectives.

What challenge does a business analyst face when managing dependencies between multiple Agile teams?

Answer: Coordinating shared backlog items and ensuring consistent understanding of cross-team requirements

Cross-team dependencies require careful coordination to ensure that shared requirements are consistently understood and that delivery timelines align across teams.

How should a business analyst handle conflicting priorities between the product owner and key stakeholders in an Agile process?

Answer: Facilitate a structured prioritization session using techniques like MoSCoW or weighted scoring

Facilitated prioritization sessions using objective criteria help resolve conflicts transparently and ensure that decisions are based on business value rather than individual preferences.

What is the purpose of conducting a pre-mortem analysis during Agile iteration planning from a business analysis perspective?

Answer: To proactively identify potential failure points and develop mitigation strategies before work begins

A pre-mortem analysis asks the team to imagine that the iteration has failed and work backward to identify risks, enabling proactive mitigation before problems occur.

Why is it important for a business analyst to distinguish between functional and non-functional requirements when refining an Agile backlog?

Answer: Because non-functional requirements often affect architecture decisions and must be addressed early to avoid costly rework

Non-functional requirements such as performance, security, and scalability influence architectural choices that become increasingly expensive to change if not addressed early in the project.