Pivotal Tracker is a steep learning curve but one of the best Software Development tracking tools out there
March 11, 2020

Pivotal Tracker is a steep learning curve but one of the best Software Development tracking tools out there

Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with Pivotal Tracker

Pivotal Tracker is used across the whole organization - maybe minus 2 people - so 8 or so. It helps us track software development work into compartmentalized tickets. Almost every ticket is touched by everyone that uses Pivotal Tracker in some way. I.e. there's a problem we are trying to solve, someone creates a ticket, someone picks up the ticket to start the software development, someone does the software development work, someone checks their work, someone tests their work, someone passes the ticket, someone checks the work of the person who passed the ticket, etc.
  • Constant updates - you can always see who touches the project as a whole.
  • Clean, concise ticket structure.
  • It's not user friendly at first. But very powerful once you understand the tools.
  • It's nice that you can customize your lanes (columns).
  • I can't speak to this as I serve on the project but don't pay for the product.
Jira is very user friendly. It's ideal for people new to the software development lifecycle and the tracking of the work. They have simply nailed the intuitiveness. Pivotal Tracker might be the better long-term tool because of the flexibility that comes with it. But as mentioned, the learning curve is very steep for Pivotal Tracker.
N/A, never used support

Do you think Pivotal Tracker delivers good value for the price?

Not sure

Are you happy with Pivotal Tracker's feature set?

Yes

Did Pivotal Tracker live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Pivotal Tracker go as expected?

Yes

Would you buy Pivotal Tracker again?

Yes

Medium to small teams - this is a great tool. I'm not sure about large teams because the Project History column would be so filled with information it might be hard to figure out what's going on/what updates have been made. But for Medium-Small teams this is ideal because of the detail laid out in the project history column.