Board Management
As a newcomer to Stories and Storymaps and playing around with CdIt in conjunction with JP's User Story Mapping book, I could imagine that (many) hundreds of maps might be created in the lifetime of a project.
Considering the various forms of common understanding required during the life-cycle - vision, different forms of planning, scoping, slicing, reviewing, developing etc. all iteratively repeated, then all the resulting stories and maps should be capable of being appropriately managed - i.e. stored, organised, indexed, retrieved, deleted, archived, etc
.
I have discovered that a single map can be saved as a csv file and so primitive management could be based on saving them in a tree-structured folder hierarchy. I have yet to discover a way to import a saved map and can appreciate that the saved structure in the csv file includes vital information to re-create the map in its original row/column arrangement, although it would appear that textual information could currently be edited outside Cardboard It, directly in a spreadsheet; so perhaps this should be controlled - as allowed or not, as part of story management.
Perhaps story board management should be the subject of a CbIt story map?
Incidentally as a retired and lone role-player of all the roles, my projects involve self-collaboration which is not very easy to undertake - often too lazy to do it - but story mapping might be the answer to record my self decision-making processes - if I can force myself to do it!
-
Anonymous commented
Now discovered Import csv on the Home page! Makes some form of management immediately feasible!