CAPM Practice: Determine how project methodologies influence business analysis processes

Lean BA reduces waste in requirements: unnecessarily detailed specs for far-future features (over-production), waiting for stakeholder reviews (delay), re-gathering requirements because of miscommunication (rework). Identifying and eliminating these wastes accelerates requirements delivery without compromising quality.

**Why not A:** Lean thinking is not restricted to manufacturing projects. Its principles of eliminating waste, optimizing flow, and maximizing value apply broadly to knowledge work, software development, and business analysis processes across all industries and project types.

**Why not B:** Lean thinking does not require eliminating all requirements documentation. It requires eliminating unnecessary documentation that does not add value. Documentation that supports communication, compliance, or team alignment is retained; only wasteful, redundant documentation is removed.

**Why not C:** Reducing the number of team members to cut costs is a staffing decision, not lean thinking. Lean focuses on optimizing processes to eliminate waste in how work is done, not on reducing headcount. Understaffing can actually increase waste through overwork, delays, and quality issues.