Overall Satisfaction with Pivotal Tracker
We used Pivotal Tracker some months ago when we decided to implement scrum inside the team. I used Pivotal tracker for some time around 2011 and I knew you have to use the "pivotal way" to be able to enjoy the tool. This is the main advantage and also the main flaw of the tool.
- If you're implementing a new process on your team and you like what Pivotal Tracker provides, it works well.
- The kanban view is good and compact.
- It was not expensive for our use case.
- If you find out that you prefer to work in a different way, the tool starts to fall apart. You have to follow its way of working.
- It's not flexible at all. You have some configurations to do, but it is what it is.
- The web app feels heavy, it's not simple at all
- The team realized that scrum will not work in the way we are working.
- The tool did the job as expected but in the end, we found that we will not need it because that's not the process we want to have for ourselves.
It works good enough. I didn't have many problems with that. The user interface is a bit confusing though. The team took some time to understand where some configurations were.
Didn't have to use it.
- KanbanFlow, JIRA Software, Trello and Todoist
We selected Pivotal Tracker because it is highly opinionated about the process. It worked quite well for what we were expecting from it. Other software we tried were much more flexible, so we could implement our own process there.
If you have a team that has almost no process and wants to start doing something, Pivotal Tracker may help you with that. You first need to check the process the tool proposes (mostly scrum) and decides if it's what you want or not. If you think it's exactly what you need, start with Pivotal Tracker because it will enforce a lot of things to your sprints.