Creating User Story Maps with Product Context Analyzer
A User Story Map organizes user stories around the tasks and subtasks identified in the context-of-use analysis. By connecting individual stories to the overall task flow, it helps teams maintain the big picture of what the system needs to support. The resulting map provides a structured, task-centred view of system functionality from the user's perspective.
Specify the activity you want to analyze. The activity can be a single task, a responsibility, or a multi-phase journey
Example: Order Pizza from a delivery service for a business meeting
Describe the activity in a single sentence without prescribing a particular product or solution.
Optionally include context such as who is performing the activity and under what circumstances.
Adding context helps make the analysis more domain-specific.
PCA creates user story maps for each task included in the analysis.
The analysis takes several minutes depending on the scope and number of tasks identified
Select a task from the task hierarchy to explore its detailed context-of-use information
Example: Order Pizza
The User Story Map is generated for the selected task and its subtasks
Select the User Story Map view to see user stories organized around the task and its subtasks
Each subtask provides context for the user stories associated with that part of the task flow
Use the map to understand how individual user stories relate to the overall task
Use the task and subtask structure to make conscious decisions about which parts of the user workflow the release will support and which remain outside its scope.
Group and prioritize user stories while keeping each slice connected to the larger task flow and the user context it needs to support.
Review user stories in the context of the tasks they support instead of prioritizing isolated backlog items without seeing the overall workflow.
Walk through the map against an existing or proposed design to identify subtasks or required functionality that may have been overlooked.
Provide detailed user stories organized by subtask so implementation can account for the functionality required throughout the user workflow.
Provide implementation tools with task-centred user stories and their surrounding workflow instead of asking them to build from isolated feature descriptions.