CAPM Practice: Determine how to gather requirements

User story mapping creates a two-dimensional view — user activities across the top (backbone), stories at varying detail below. It reveals gaps, supports MVP definition, and plans releases as horizontal slices through the map that deliver end-to-end user value.

**Why not A:** User story mapping is not a testing representation technique. While the resulting map can inform test planning by showing user workflows, its primary purpose is to arrange user stories along a narrative flow to visualize the user's journey, identify gaps, and plan incremental releases based on end-to-end functionality.

**Why not B:** User story mapping has nothing to do with plotting the geographic locations of users. The term "mapping" refers to organizing user stories spatially—typically with a backbone of user activities across the top and detailed stories arranged vertically by priority—to create a holistic view of the product's functionality.

**Why not D:** Assigning stories to individual team members is a sprint planning or task allocation activity, not user story mapping. User story mapping focuses on understanding the big picture of user needs and organizing stories into coherent release slices, rather than determining who will implement each story.