CAPM Practice: Determine how to gather requirements

Value stream mapping documents the current flow of a product or service from request to delivery, marking value-adding and waste steps. It reveals process improvement requirements by showing where delays, rework, and handoffs occur — generating clear improvement requirements.

**Why not A:** "Mapping each requirement to its financial return" describes a form of cost-benefit analysis or requirements prioritization, not value stream mapping. Value stream mapping is a lean technique that visually maps the flow of materials and information through a process to identify waste and inefficiencies, not a financial mapping of individual requirements.

**Why not C:** "Financial analysis of sprint value" confuses value stream mapping with agile financial metrics or earned value management. Value stream mapping focuses on process flow and identifying non-value-adding steps in a workflow. It is not a financial analysis technique applied to sprint deliverables.

**Why not D:** "Mapping stakeholder value to project outcomes" describes a form of benefits realization or stakeholder analysis, not value stream mapping. While understanding stakeholder value is important, value stream mapping specifically examines the end-to-end process steps to identify waste, delays, and opportunities for process improvement.