Question: What are some best practices to manage very large ‘user Story framework maps’ without over-complicating entire process of creating user stories for user roles?
I just discovered this app and I am LOVING it! Its like Trello on steroids mixed with draw.io and balsamiq. really cool software.
Right now I am using Miro to heavily document my ‘social application (think similar to Facebook) user activities, tasks, and stories. I have over 1500+ user tasks so far. In my case I have 4 areas of the application in which I have created (4) User Story Framework Map Boards
- Public Area (where non-auth users can visit and what they can do)
- Standard users (User Type - A) - What authenticated standard user type A can visit and do
- Other User Type (User Type - - what authenticated user type B users can visit and do
- App Admin User Type (User Type - C) - this is like the ‘Facebook admin / Facebook staff user for reference. This is what all User type c can visit and do.
So I have already broken up the application into ‘areas’. The boards are still VERY large. Is there a best practice way I can manage this without losing performance or having VERY large boards that are difficult to maintain?