I find using story maps a very effective way in convincing clients to use the lean start-up principles, by forcing them to think long and hard about what features are mvp and which should be released first (ie by visualizing the releases and the backlog etc).
My problem is that I'm currently working on a very technical solution. It's more about getting a user (B2C) application (that has a lot of UIs) and creating a cloud version of it (B2B) that will be handled by a handful of admins. As part of the estimation we figured out that on the mvp phase we should mostly use command line and not bother too much with UI.
My question is: how can user story maps be used to visualize a project like this where there isn't too much of a user story going on. it's mostly stuff going on at the backend to scale operations of which a UI has already been implemented for the individual consumer.
The following is a list of tasks that I would like to put on a user map, and I'm struggling on how to lay them out:
Backend/API-Basic-Setup Backend/DB-Model/Setup Backend/DB-Model/Credit-Cards Backend/DB-Model/User-Data Backend/DB-Model/Task Backend/DB-Model/Task-Machine-Assignment Backend/DB-Model/Cloud-State Backend/DB-Migration Backend/Pubsub-Setup Backend/Provider/Abstraction Backend/Provider/Abstraction-Min-Implementation Backend/API/User-Data-CRUD Backend/API/Task-CRUD Backend/API/Task-Machine-Assignment Backend/API/Bot-Facing-APIs Backend/Coordination/Task-Scheduling Dashboard/Login Dashboard/User-CRUD Dashboard/Task-List-Management Dashboard/Task-Create-View Dashboard/Task-Provisioning Dashboard/Machines-Overview Bot/Web-Server-Interface-Setup Bot/Refactor-Existing-Tasks Bot/Connect-API-To-Web-Routes Bot/DB-State-Setup Bot/Deploy-updates Bot/Instance-image