4 ms·

I feel like JIRA was just a configurable workflow tool at a time when all the processes around software development were still being defined/standardized. It wo

I feel like JIRA was just a configurable workflow tool at a time when all the processes around software development were still being defined/standardized. It worked well for it's era because people could get it to do whatever they felt was perfect fit for them, but overtime I feel like it's broken down for much the same reason that people prefer to buy a SaaS product that has 95% of their needs out of the box. Processes (agile) and UIs (kanban) have been much more standardized in software project management and only now does it seem like some companies are coming up to give you that 90% out of the book with 10% the overhead/ management. Pivotal Tracker came close.. Clubhouse.io is the one I've seen doing it best.

jacques_chester 9y ago
Pivotal Tracker has been around for a fair while now; it's usually compared to JIRA. They have quite different DNA. Tracker grew out of Pivotal Labs and it is mostly molded to how Labs and R&D teams do their daily and weekly work. To me it seemed constricted and limited until I came to work at Pivotal; now it makes sense.
chrisco255 9y ago
I've used Pivotal Tracker and I think it's great for small teams, but I can not see a big company with 500+ users using it. JIRA is better for ticket tracking, issue linking, cloning, reporting, integration with Bitbucket/Github branches, user permissions, build system integrations, burndown charts, analytics, media services support, and not to mention the ecosystem around JIRA is just huge. Disclosure: I'm an Atlassian employee, but I had these opinions before I started.