“Imagination is everything. It is the preview of life’s coming attractions”. Albert Einstein
An interesting thought came to me while thinking on how to bring in dynamics in story map to make it a tool that will help PO both in day-to-day work/tracking and overall release management.
Key benefits that will serve this are:
- A full picture of upcoming product being built (within scopes of upcoming releases);
- Transparency about features are being worked on now/coming soon;
- Highlighting what features are READY and DONE;
- Done row indicates stories that correspond to the functional areas of the product and are accepted by product owner in sprint review meeting(s), having story definition of DONE met.
- Areas row indicates key functional areas of the product as any story map has.
- Wip row indicates work-in-progress, e.g. stories that are part of the running sprint (that team committed upon);
- Ready row indicates stories that are ready to be presented to team according to definition of ready. PO moves stories in this row only if those compliant with INVEST rule;
- Pipeline row indicates all the stuff that is planned for the future. As you can see some stories are non-READY here for whatever reasons (not yet completed, or even bigger items (epics) that are not yet prepared for sprint planning and thus cannot be taken by development team);
NOTE: pipeline row can be splitted itself into several rows to indicate scope planned for releases.
This simple board will serve as Kanban-style board turned by 90 degrees CCW. You can always add rows that indicate whatever states your PO team will find beneficial. Such a board can be easily used by PO daily in managing both day-to-day focus on getting READY for upcoming sprint, while keeping an eye on overall priorities and backlog.
Here’s real-live example implemented: