Overall Satisfaction with Pivotal Tracker
We use Tracker to manage our backlog and feature roadmap. Our whole organization uses it: product, development, and design. Design also has a their own project to manage their personal backlog. The stories are written in the way that anyone can read them without being technically too specific. An example would be:
As an Admin
When I am on the dashboard
And I click "show stats"
I should see stats within a given date range.
As an Admin
When I am on the dashboard
And I click "show stats"
I should see stats within a given date range.
- Measuring the velocity of the team. Every week there is an estimated velocity of how many points can be accomplished per week, or per sprint.
- Managing priority of stories. Whatever is at the top of the backlog takes precedence over what's below.
- Integration points. We use the webhooks for git and for Slack that makes the monitoring really easy.
- Bulk adding of stories in reverse order. When you create a bunch of stories, you often do it in the order you want them done, and they inputs them in backwards. So you need to drag each one over individually in order to get the sequence that you want. This is particularly annoying for epics.
- Everything has been positive with this product. It is easy to pick up and dive in.
- As far as organization and transparency, I have found no better product.
I've used JIRA ages ago, and it was still a young product in its initial iterations. The UI was a clunky and was missing a lot of ease with drag and drop for individual stories, uploads, etc. Management of users was useable, but not as ideal as it could be.