Story Maps help in visualizing the backlog. You can place all the features and user stories on the story map such that significant information can be obtained by merely looking at it. This is most helpful for non-technical stakeholders.
Below is how a story map looks like. Check out the video above to understand this story maps’ example,
Backbone – The most core features. High level grouping of all features on the story map
Walking Skeleton – Backbone’s most important user stories. Once these features are ready, the product becomes usable
Below are the 6 points to remember about story maps,
- Releases can be sprints too (Difference between Release and Sprint)
- First release (Release 1) should focus on delivering as many walking skeleton features as possible
- Beyond the first release, the team works on features as per the priority
- User stories can move to a different release as more information becomes available
- Team can easily visualize the entire release plan with the help of a story map
- Remember this is a GASP
Check more articles on Agile
