Jira vs Pivotal Tracker: What are the differences?
Developers describe Jira as "The #1 software development tool used by agile teams to plan, track, and release great software". Jira's secret sauce is the way it simplifies the complexities of software development into manageable units of work Jira comes out-of-the-box with everything agile teams need to ship value to customers faster.. On the other hand, Pivotal Tracker is detailed as "Build better software, faster". Collaborative, lightweight agile project management tool, brought to you by the experts in agile software development.
Jira and Pivotal Tracker are primarily classified as "Issue Tracking" and "Agile Project Management" tools respectively.
"Powerful" is the primary reason why developers consider Jira over the competitors, whereas "Agile" was stated as the key factor in picking Pivotal Tracker.
reddit, Lyft, and Heroku are some of the popular companies that use Jira, whereas Pivotal Tracker is used by Zendesk, Movielala, and DeveloperTown. Jira has a broader approval, being mentioned in 2090 company stacks & 1470 developers stacks; compared to Pivotal Tracker, which is listed in 198 company stacks and 54 developer stacks.
What is Jira?
What is Pivotal Tracker?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
I use Jira because
- It's used widely as the best SW dev tool
- It's so easy to use
- Flexible to configure
- Great for tracking of tickets while leading meetings
- Accessible from Everywhere
In overall, especially for large projects, Confluence is must. On the other hands, for small-mid size projects, #Trello is also great due to visualisation power.
Over time, as our teams became bigger and projects became more complex, we started to take agile processes more seriously and wanted more advanced (by our standards) project management abilities, like burndown charts, velocity tracking, etc. We also wanted to handle a lot of content management tasks that were primarily done by non-technical teams but often touched engineering.
After using Pivotal Tracker and Wrike, JIRA ended up being the right choice for us. Its design was flexible enough to do engineering project management, content management and other tasks like product roadmapping effectively. It had all the bells and whistles we wanted (plus many more we never got around to using). Given that it is a flexible service that tries to do everything, it is ideal for a team that can 1) dedicate significant bandwidth to upfront setup and organization and 2) empower admins to establish and enforce best practices among team members.
#Collaboration #IssueTracking #AgileProjectManagement #ProjectManagement
Pivotal is nice if you’re a contractor or have a small team with simple process. In fact, in those circumstances it may be one of the best tools out there aside from Trello.
However, if you have a larger team, it’s difficult for Pivotal Tracker to fit your process. It’s also difficult to plan with Pivotal Tracker - it often ends up being more of a triage tool than a good planning tool.
The biggest limitations are the limited states for stories and limited views - everything is in a column and you can’t preset a view the whole team can see, so team members have a very hard time visually seeing the same set of stories.
Most of my time in JIRA is spent
- Waiting for pages to load
- Clicking on links, because the information that I need is not available on the first pages I reach
- Looking for the next link to click, because each page has a different layout and the bug title or the latest comment might be placed anywhere on the page
Additionally, any time I search the documentation I get bug reports from years ago that appear unresolved or instructions for modifying the on-premesis installation (we have their cloud service).
Compared to Bugzilla and Redmine, Jira requires a lot of manual configuration which can make project issues not compatible status-wise.
It is used for bug tracking, issue tracking, and project management The basic use of this tool is to track issue and bugs related to your software and Mobile apps. It is also used for project management. The JIRA dashboard consists of many useful functions and features which make handling of issues easy.
So much relief as you can track each and every issues, bugs, dev project and maintenance and a time machine when it comes to do that less interesting timesheet or daily status. Its a rescuer.
We use Pivotal Tracker to organize our development for all of our clients. Tracker enables our agile-inspired process, which helps us deliver the most value to our clients.
We use a combination of Scrum and Kanban for our tasks. We focus more on the integration with Bitbucket to keep track of tasks and have bi-directional accountability.
We use JIRA because it's a single tool that can be customized to each of our business processes: product development, customer on-boarding, and internal operations
The agile process planing feedback and control is done in JIRA, with integrations in all places, like bitbucket code, confluence pages and build process