Overall Satisfaction with Pivotal Tracker
Pivotal Tracker is being used mainly by our engineering, product, and QA groups to manage the development work stream. Pivotal Tracker helps us maintain a well defined and easily understandable backlog of stories. It also becomes a place for us to track all of development past and present which then serves as the manifest of where we've been and what we are about to do.
- Pivotal tracker is simple to use. I can easily onboard a new developer to Pivotal with a 10 minute conversation.
- Pivotal tracker is very straight forward. It makes sense to craft the backlog in a linear fashion like Pivotal has it.
- Tagging and email notifications are great.
- Support for third party integrations is also a plus.
- Deleting a story means that it is gone forever. There is no archiving.
- [Doing a] stack of work becomes quite hairy, no great way to manage or modularize that information.
- Mobile application could be improved for sure, Pivotal seems very built for the web. I always get the notifications but they never bring me to the relevant story within the application. Even a tool like Basecamp can do that for me.
- Pivotal has helped us bridge the backlog across various offices and offsite developers.
- Pivotal has helped us keep our backlog and workstream clear and concise which helps us do more.
- Pivotal does not roll up very easily for bringing the stack to higher up execs. For this we've had to use other tools such as Trello.
Overall I have found that I prefer using Pivotal over all the competitors I've tried. There are certain aspects of the other products which I do like but as a whole Pivotal does a better job. My one request is that I feel it is very much a web app and the other products have more solid mobile applications. Pivotal has sold me as my primary option due to its web portal but I would love to see a better mobile application.