Release or Version Planning in Agile User Story Maps. Yes or No?
Hello I have seen competing thoughts about including release, sprint or version segments in an Agile User Story Maps.
To my knowledge you can create a User Story Map but then create a flat Product Backlog based on this. If new requirements are needed you can add to the User Story Map and also then the flat Product Backlog. This has the negative effect of having to manage 2 boards, but has the positive of being able to see a flat linear list and what is near the top should be most often pulled into the next Sprint.
But I am seeing examples of using just a User Story Map as a way to visualize a customer journey as well as a using it as the Product Backlog with sections for Sprints. This has the negative impact of not being able to see what is at the top of a linear list, but has the positive effects of keeping the customer in mind through visualizing their journey, and only managing 1 board.
See this example image to help understand what I mean.
Let me know which you would go with or your approach!
Do you and the team find that the benefits of maintaining two boards outweigh the over head?
But I am seeing examples of using just a User Story Map as a way to visualize a customer journey as well as a using it as the Product Backlog with sections for Sprints. This has the negative impact of not being able to see what is at the top of a linear list
If the team chooses to go with the more customer centered view perhaps there's a creative solution the team can come up with to handle the drawbacks.
To my knowledge you can create a User Story Map but then create a flat Product Backlog based on this.
Why do you think a Product Backlog has to be flat, and could not actually be a User Story Map?
Hi Ian,
How would the Dev team know which user stories were most important if using a User Story Map? Since there are both horizontal items (epics) and liner vertical items (user stories)?\
Tony those are great questions that will drive a solution!
Thanks!
How would the Dev team know which user stories were most important if using a User Story Map?
Wouldn't they be identifying a walking skeleton and MVP release candidates?
Ian thanks for this article, very helpful!