User Story maps should be able to show Master Features and Features from multiple products.
We have complex products that have to work together in order to deliver usable solutions. Any step that the user does (install, configure, receive certain data, etc) requires work on multiple products (hardware devices, firmware on those devices, software user interface, data collection system) to make the solution work.
Our Master Features always contain Features spread across multiple products.
The User Story Map seems to be a great way to visualize how the Features within a Master Feature are delivered over multiple releases, but if we can’t actually see all of the Features under that Master Feature, it loses the value. We would love to have a better way to visualize the relationship between Master Features and Features.
Agree, most of our solutions are for enterprises and have separate and collective value. While this is a good feature, the inability to span across business processes that are addressed by separate products renders it unusable. I would assume opening up filters and being able to connect would be fairly straight forward. Seems like an oversight in the first place than really being a new idea/feature.
The restriction of user story mapping to a single workspace reduces it's value to just about zero for any multi-product company.
This is vital for amalgamated products and conceptually it seems like a weird restriction to have user story mapping only for a single workspace considering initiatives and masterfeatures can span multiple products.
This would help us, too. I love using the user story map to organize a product effort. Once we identify those user stories, we need to give ownership to other products/workspaces to complete the features. But, we'd still like to see the big picture in the user story map. Perhaps we can have user story maps that live at a parent / product line level and can see all the features from the products?
I’m able to add features to the user story map that belong to the same master feature but that are created in a different workspaces. The way I do it is not user friendly but it works. Move the feature created in another workspace to a release in the current workspace (Where you are creating your user story map). Then, you’ll be able to see the ticket on the side menu “add existing records” under the “features“ drop down list. Select it and It’ll show up in your user story map. Then, manually move it to the right release on the other workspace (edit the release field in the feature) and voila! your user story map will be updated with the external release.
We definitely need something more user friendly. There should be a way to list the features from other workspaces that are part of the same master feature to add them easily.
We need this too! The Story maps are a fantastic way to visually organize epics and features across releases, but it's useless to us unless we can also organize them across workspaces too.
For example - a workspace that has a mobile app and a workspace that has the website
the same user activity triggers workflows on all of the above: for instance, buying something on the webapp should trigger a notification on the app.
Should be a rather simple solution- allow a product line workspace to contain story maps of the contained workspaces...
We are in a very similar situation, but we use initiatives instead of master features for tracking cross-product work. Our features are linked to an initiative.If user story maps were made to span more than one product, we might transition from initiatives to master features to get this functionality.