CAPM Practice: Determine how to gather requirements

Requirements decomposition breaks high-level requirements (epics, capabilities) into progressively smaller, more detailed requirements (features, user stories, tasks) that can be designed, estimated, and implemented incrementally.

**Why not A:** Organizing requirements alphabetically is a sorting method, not decomposition. Requirements decomposition breaks high-level requirements into smaller, more detailed sub-requirements based on functional hierarchy, not alphabetical categorization.

**Why not B:** Decomposition is not about simplifying requirements to reduce documentation. It actually increases detail by breaking large requirements into smaller, actionable pieces. The goal is to make requirements implementable, not to reduce the volume of documentation.

**Why not D:** Removing outdated requirements from the backlog is requirements retirement or grooming, not decomposition. Decomposition is a constructive process of breaking requirements down into finer detail, not a removal or cleanup activity.