User Story Mapping

Understands the User Story Mapping concept (Jeff Patton). Can participate in story mapping sessions. Distinguishes between backbone, walking skeleton, and release slices.

Understands the user story mapping concept and its application for technical products. Knows the structure: activities, tasks, user stories. Participates in mapping sessions and helps define MVP considering technical dependencies.

Independently conducts story mapping sessions with the team. Defines MVP through release slices. Uses story maps as a product scope communication tool.

Independently facilitates user story mapping sessions with product and engineering. Defines walking skeleton considering architecture constraints. Prioritizes releases through horizontal slicing with technical trade-offs.

Applies story mapping for quarterly strategic planning. Combines with impact mapping and opportunity solution trees. Teaches the technique to other PMs and designers.

Applies user story mapping to complex technical products with multiple user personas and API consumers. Integrates technical architecture decisions into story map. Defines release strategy through mapping considering platform dependencies.

Standardizes scope decomposition and visualization approaches at the division level. Applies story mapping for cross-product initiatives.

Defines user story mapping practices for the division. Introduces mapping as standard practice for feature kick-offs. Trains TPMs on facilitating mapping sessions with cross-functional teams. Integrates with roadmap planning.

Uses story mapping and similar tools for visualizing strategic product initiatives at the portfolio level.

Shapes enterprise story mapping approach for complex technical programs. Coordinates cross-product story maps for unified user journeys. Defines mapping standards for multi-team initiatives. Mentors product leaders.