This is an old revision of the document!
Host: Mark Kilby
How many of you maintain backlogs? How many of you have become lost in long backlog of stories?
Storymaps are another way to organize your backlog to better understand your themes, epics and how to better deliver value
It starts here; you need to empathize with your users
A persona helps you “get into the user’s head”. Not just a role like in use cases. - What is their background? - What other systems do they interact with? - How many hours per day do they work with your system? - What do they need? - What do they not need?
Example: Financial Management System
Persona: Rob the Regional Manager
Background: has many responsibilities; works at least 10 hour days; travels; given revenue goals
Rob works with multiple teams; so he needs: - burndown charts - view across teams - reports - off-line data
Workflow is represented left to right Each column represents a feature/epic with several columns representing a key step in the workflow Columns then divided into user stories and sorted by priority MMF = Minimal Marketable Feature – minimum number of user stories to deliver the basic feature MVP = Minimal Viable Product – minimal number of MMFs for a customer to purchase
Story maps can help answer “when is it going to be delivered”? - size the user stories; roll up points to epics/features/MMFs - compare to team velocity
Digital story mapping tools – a few out there or plug-ins for existing tools, but none excellent
Use a board or spreadsheet if you have remote teams
PO can use for stakeholder expectation management
Also a discussion tool – if epic is almost done but new stories come in that are related, recreate epic and add story
Storymaps help manage product visually
created by Steve Bockman