This answer directly reflects a core principle of agile analysis. The goal is not to produce comprehensive, detailed documentation upfront but to perform "just enough" analysis to make the next informed decision and enable the team to proceed with the next increment of work. This just-in-time approach minimizes waste (a key lean principle) by avoiding effort on details that may change or prove unnecessary. It allows the team to remain flexible and adapt to new information as the solution evolves.

A. This describes a "Big Design Up Front" (BDUF) approach, which is antithetical to agile methodologies as it creates waste and reduces flexibility.

B. While analysis outputs may be used to inform management, the primary driver for the level of detail is to enable team decisions, not to preemptively answer all possible executive questions.

C. Attempting to gather enough information for "all stakeholder needs" at once is a characteristic of a waterfall approach and is impractical in an agile context where needs are discovered iteratively.

1. IIBA

Agile Extension to the BABOK® Guide

Version 2

Section 4.2

"The Planning Horizon". This section explains that in agile

the level of detail increases as the work becomes more imminent. "Items to be delivered in the near future are described in great detail

while items to be delivered further out are described at a high level." This supports analyzing to a level of precision just enough for the next decision.

2. IIBA

Agile Extension to the BABOK® Guide

Version 2

Section 7.1.4

"Guidelines and Tools - Just In Time (JIT) Analysis and Elaboration". This guideline explicitly states

"In agile business analysis

requirements are elaborated to the details needed just before they are needed for implementation." This directly supports the concept of doing just enough analysis for the immediate next step.

3. IIBA

Agile Extension to the BABOK® Guide

Version 2

Section 3.2.5

"Avoid Waste". This principle

derived from lean thinking

emphasizes that any activity not adding value is waste. Creating overly detailed analysis far in advance of when it is needed is a form of waste

as the requirements may change. Analyzing just enough to make the next decision avoids this waste.