Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Three tips for boosting your board's efficiency with Story Maps

Trello is one of the most effective tools for driving your sprints. It's customizable for every Agile team and product owners and Scrum masters (SM) love it. However, Agile teams often struggle with:

  • bigger projects that flood the list with cards
  • seeing the big picture: what does next month look like?
  • integrating new ideas mid-development?


Three problems, one solution

My suggestion is to keep the product backlog on a user story map. Why? Trello boards are perfect for day-to-day work where the PM or SM specifies and distributes tasks for the current Sprint or release. In contrast, user Story Mapping provides a perfect overview of the whole product, making it easy to understand the context and goals. A user Story Map is the best place for strategic thinking (e.g., prioritizing ideas, planning Sprints, looking two steps ahead.)


User Story Mapping in a nutshell

There are ample educational materials on the web regarding user story mapping, so I will only give a short summary of the method. It's an Agile, user-centered planning method which starts with collecting user activities then exploring each step following a narrative flow. Activities and user steps (as sub-activities) are the backbone of the product backlogs. The body of the backlog is made up of all tasks, user stories, and ideas created through the narrative flow.


SM_1.jpgWhat does this look like? Each piece of information is written on cards and placed on the wall or in Story Mapping software. The planning team or the PO arrange the cards by moving high priority tasks upwards. Then, the body is categorized into working features.

In order to address the previously mentioned struggles Agile teams face, we have created a Story Mapping tool called StoriesOnBoard that offers real-time, two-way Trello integration. First, a new user can navigate a sample webshop filled with tasks in order to better understand how the software can work for them. Next, the new user can explore an empty Story Map which is connected to the Trello board.


Trim your board and keep focused!

I'm sure you've seen very long Trello lists with the longest (and most annoying) lists on the first and last sections of the board. This is because teams run into problems when trying to store cards outside of the current scope. Some teams opt to collect tasks of upcoming Sprints in separated lists, but this can cause problems for the development team, slowing them down; the development team performs better when they don’t have to deal with cards that are not relevant to the current Sprint. Teams often trim the board by archiving them, losing opportunities for retrospect.

SM_2.jpgWe have a solution: by creating the user journey on a Story Map and importing tasks from Trello in one click, titles, descriptions, and statuses are synchronized. 


Next, cards are arranged under user steps. (This efficiently detects holes in the product, but that's another story.) Then, the body of the backlog is sliced/categorized into Releases; if you don't have release strategy, then prioritize cards and group them into working features. 


Now the Trello board can be wiped clean, archiving finished tasks and removing cards irrelevant to the current Sprint. (Don't worry! Removed cards remain on the Story Map! They can be imported later when the development team finishes the sprint.)


Look further (than next week)

Trello boards manage all of the day-to-day development but often struggle to see the forest for the trees. A product owner must be able to see what the next quarter looks like in order to share further steps with contributors. Our method provides the perfect solution.

Ordering features into Releases create an easy-to-understand overview for stakeholders. This bird's eye view of the user Story Map exhibits:

    • planned features
    • schedule of the development process
    • how working features are related

This tool offers opportunities for predicting story points, hours, days, etc and development progression can be tracked via burndown charts or other reports.

Don't confuse your team with non-prioritized tasks

Give the green light to new ideas, but don't leave them unscheduled. Our tool automatically separates new cards from the previously created backlog. Simply collect ideas via an input-list on the development board, then empty this list by sending cards onto the user Story Map. Prioritize new cards on a Story Map by either:

    • moving cards into a scheduled release
    • creating a new release from new ideas
    • removing irrelevant tasks

Hard to rank/categorize tasks? Create new releases based on a prioritization method such as Must have, Should have, Could have, Won't have (MoSCoW method).



Log in or Sign up to comment
Deleted user June 3, 2018

In a software development Project - Each user story needs to undergo a SDLC cycle. I.E. Design-Develop-Test-Ready-Release workflow steps. Are all these steps part of "In-Progress" Kanban list? How to differentiate and track time? What if in between the issue goes on HOLD for some reason?

Gergő June 6, 2018

Nupur, Hi!

Thanks for the questions. Here are my answers:

1. We use the story map with a different scope, just to overview the project (planning, prioritizing). So TODO/DOING/READY/DONE statuses are enough. For sophisticated status-management, I suggest creating as many Trello lists as you need. You can assign all individual Trello list to a StoriesOnBoard status. Our dev team uses the tools in the same way. Eg: assign "develop" and "test process" to "doing". By moving the cards between lists the status won't change.

2. You can add estimations to cards (story points, hours, whatever you need), and also Trello has cool powerups for time tracking. Just make sure to add the same estimations. 

3. If a user story (or Issue) slips out of the current iteration you can move the card to next iteration or you can add a release for those cards. (eg. icebox)  Just like prioritization releases (next selected, must have etc.) Try to handle story maps as elastic backlog, moving cards between releases is completely natural.

AUG Leaders

Atlassian Community Events