Which statement about Story Mapping is true?

• A. It's only for non-functional requirements
• B. It is a planning method visualizing features from the end-user perspective
• C. It adds no value to sprint planning
• D. It replaces backlog grooming

Answer: (B)

Story Mapping is a planning technique that places the user’s journey at the center, organizing features as a map of activities and the user tasks that support them. This visual arrangement helps teams see how a user would accomplish goals with the product and to prioritize work based on real user value.

The statement describes this approach accurately: it’s a planning method that visualizes features from the end-user perspective, showing how each feature supports user tasks and the overall flow. By laying out activities on the map and grouping related stories under them, teams can identify the minimum viable product, sequence work for releases, and discuss trade-offs based on user value. It’s not limited to non-functional requirements, since the map commonly includes functional stories arranged around user goals. It also doesn’t claim to replace backlog grooming; instead, it complements it by providing a clear structure for refining and prioritizing the backlog. Additionally, it adds value to sprint planning by offering a user-centered view of scope and priorities.