Contents:

Slicing a release is the process of taking a broad product vision and dividing it into manageable, shipable increments. Using the StoriesOnBoard MCP Server, you can move away from manual drag-and-drop actions and use AI to strategically organize your backlog into releases like MVP, Version 2.0, or Marketing Launch.

Create your story map, the visual product backlog from scratch or user StoriesOnBoard MCP server to build it up or even import from Jira or Azure DevOps for instance. Then simply ask your AI tool to use the MCP server connection to identify the MVP according to your needs.

The MVP release has been created and now we need our AI tool (in this example we used Claude) and provide the right prompt to identify what to build first.

The prompt we used in this example:

I need to define the Minimum Viable Product (MVP). Perform the following steps:

Analyze the Map to retrieve the entire structure.

Evaluate Value: Identify the 'Happy Path'—the absolute minimum set of cards required for a user to complete a core transaction (The Best User Experience with the lowest complexity).

Identify Business Value: Look for subtasks that satisfy legal, safety, or core revenue requirements.

Execute the Move: For every card identified as essential for launch and move that card into the release named 'MVP'. Specific Criteria for the AI:

Prioritize Function over Polish: If a subtask is a 'nice-to-have' UI improvement, leave it in the backlog.

Maintain Integrity: If you move a Subtask to MVP, ensure its parent Task and Activity are also represented or logically accounted for.

Report Back: Once finished, provide a summary of which cards you moved and a brief justification for why they were chosen for the MVP."

Then the AI assistant used StoriesOnBoard MCP server to analyse and select the right backlog items that we should first deliver and move these items into the MVP release.

Use this when you have a massive map and need to find the shortest path to a working product.
​

Analyze the 'QuickBite' story map. I need to slice an MVP release. Identify the absolute minimum subtasks required for a user to find a restaurant, place an order, and pay. Move all essential cards to the 'MVP' release and leave the 'nice-to-have' features (like social sharing or advanced filters) in the 'Unscheduled' pool.

Use this to organize a release specifically for backend or foundational work.
​

Search all cards across the board for keywords like 'API,' 'Database,' 'Security,' and 'Authentication.' Move these cards into a new release named 'Technical Foundation'. If a card is currently in 'MVP' but is purely a UI polish item, move it back to the general backlog to make room for these technical requirements.

Use this when your next release is focused on a specific platform or user persona.
​

We are focusing on the Courier experience for our next sprint. Review all tasks under the 'Delivery Operations' activity. Find every subtask that specifically mentions 'GPS,' 'Rider App,' or 'Push Notifications' and move them into the 'Courier v1' release. Provide a summary of the total estimated effort for this release once finished.

Learn more about: