Overall Satisfaction with Trello
I have used Trello for 5 years. First, I used it specifically for our mobile technical development tasks. For 2 years I used it for all internal tasks and projects with specific spaces. Now, users are [in our] marketing, functional and technical profiles. Most of these people learned the Agile method (projects). Other people use Trello for tasks (documentation of to dos, learning to plan). This is our collaboration tool.
- Visual presentation: you can easily see tasks, tasks status, users and roles
- Avoid problems of a physical board and post it (dixit Kanban): place, move it, post it loss ...
- Projects and tasks structuring: you need to do thinking before adding a new task. This is a good behaviour.
- Sometimes we could be lost in the visual interface and have some difficulties to know where we are and where something is that we are looking for. Especially if you use Trello for different tasks and projects.
- Positive impacts: Jobs, projects and tasks structuring, collaboration between employees and between teams/services and saving of time after first weeks of use
- Negative impacts: Some people could be lost without a physical board, not for people who dislike the Agile method but it does help to change their point of view
I used JIRA, Basecamp and Redmine. JIRA is for big/huge projects, very technical ones. Redmine is fine and used by another team. It needs more rules for a good Agile use and you can do what you want (more than with Trello, too much). And the visual interface is not as useful as Trello's. Document management could be better with Redmine. Basecamp is a good solution but we chose Trello. ;)
Trello is well suited for:
- Small team for a limited number of projects
- Small or larger team for internal tasks of several kind
- Team with people in several spaces