CAPM Practice: Determine how project methodologies influence business analysis processes

Lean identifies waste as anything that doesn't add value. In BA work, waste includes: over-specified requirements that constrain solutions unnecessarily, comprehensive documentation for features that will be deferred indefinitely, and lengthy sign-off processes for low-risk decisions. Lean BAs minimize waste while maintaining quality.

**Why not A:** Waste in Lean thinking refers to activities that consume resources without adding value to the customer — it has nothing to do with physical office space or document storage. This answer takes a literal, physical interpretation of "waste" that misses the entire conceptual framework of Lean methodology as applied to knowledge work and business analysis.

**Why not C:** Lean does not consider all documentation to be waste. Lean distinguishes between value-adding and non-value-adding activities. Well-targeted requirements documentation that supports development and stakeholder alignment is valuable. The Lean principle is to eliminate unnecessary documentation, not all documentation — a critical distinction that this answer fails to make.

**Why not D:** Lean thinking originated in manufacturing but has been widely adapted to knowledge work, software development, and business analysis. Agile and Lean-Agile frameworks explicitly apply Lean principles to requirements work, including concepts like minimizing work in progress and eliminating wasteful processes. Restricting Lean to manufacturing ignores decades of successful cross-domain application.