Map
The problem to solve
Most projects use a board with columns to order their task by status and priority. We all know the kanban board. It works fine until the project starts to grow. Then we bother with things like task relation (parent task, blocked task), organizing tasks into different levels (stories, epics, projects, sprints, views), adding labels, tags, or milestones, and trying to set up priorities. Finally, all this creates a system that is hard to follow and maintain. And we hold meetings to align priorities and explain the boards to each other. All these things are not fun but necessary. That's why we created the map.
The solution
On the Prio map, we use a visual hierarchy instead of different types of labels. That approach helps your team to stay organized and keep the structure clean. A real-world map shows where you are and how can you go from your position to your destination, as the Prio map helps the team to know how you will achieve the goal.
Values
- Automated estimation based on team past performance
- Graph structure helps you to vizualize the task relations
- Clear priorities based on the graph. If you move one task it will recalculate the priorites instantly all the others. (Priority management)
- It shows where the teammates are or where they should be. (Markers)
- Shows where if your process is blocked (Flames)
- You can kepp your eyes on the big picture by default.
- You can communicate the business value next to the actual task that the team needs to complete. (Reward system)
