Pivotal Tracker Information Reviews & Insights

Pivotal tracker tool is Very easy to use and can be used for smaller and medium projects . In pivotal tracker the best is detailed tracking which is really helpful for me when i need to cross verify my work from previous months. Pivotal tracker allows us to keep track of every tasks, add notes anytime and update their status on time. Pivotal tracker is mainly Used for Agile project management.

The UI of the Pivotal tracker is really beautiful and amazing, which looks trivial, but we have it open all the time, so it's nice for us. In Pivotal tracker for me its very Easy to create tasks or stories anytime without facing any problems. Pivotal tracker provides us a ton of features to track the tasks and manage a team and the projects. Pivotal tracker allows for a entire team to be on the same page of the tool in regards to where is the project right now, right status of every task, what is being worked on and by whom.

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.

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.

We use Pivotal Tracker to track the development and MIS teams' work and ongoing support of software and infrastructure they have built for the company across about a dozen projects/solutions. These solutions range from infrastructure, eCommerce, internal custom software, and mobile applications. We use it to track features, chores, and bugs for each of these areas. We have from time-to-time exposed it to external vendors for project collaboration and centralized project management of those projects. It is an excellent tool for keeping track of the work and being able to quickly prioritize work, check the status, and re-prioritize tasks based on changing requirements.

Pivotal Tracker is extremely easy to use. New users are able to learn the system and start using it on the same day. I could not manage the number of projects here without this system that gives me a great view of what is happening in each project. Features, chores (maintenance type tasks), and bugs are clearly identified so I can work with Product Owners to prioritize the work according to internal and external customer needs.

We used Pivotal Tracker because our head developer preferred it to other project management/dev tools. The most important function is for helping developers to prioritize dev work. Developers don't always prioritize the highest priority items so it worked well to have a project manager owning the roadmap while the devs had a consistent checklist of priorities to work on each sprint.

Pivotal Tracker is great for software development teams. Approvals are pretty sleek which allows for back and forth between developers and the QA process if there are bugs or the product isn't being built up to specs. It's less useful as a general project management software but they're pretty clear on their website that it is geared towards software development teams.

We used Pivotal Tracker as a list of engineering bugs, tasks, and backlogged items for the engineering team. We eventually moved off of Pivotal Tracker but while using it, it allowed us to prioritize the tasks and bugs logged by our users as well as the product management team. They did so by utilizing the points feature.

Pivotal Tracker is best suited for a smaller team (JIRA becomes more necessary as your company scales). It is best for engineering bugs, tasks, and backlogged items for the engineering team. Also good to connect to your Slack channel for team visibility. I also found it helpful that you have flexibility with the sub-sections you can create within Pivotal Tracker.

Pivotal Tracker is a SaaS project management tool that is used by software development teams and stakeholders to track software projects using an agile methodology. The Ventus Software Development team uses this application extensively to track multiple software projects including but not limited to new features, bugs, chores, epics, and releases. Where Pivotal Tracker really excels is its usability. The layout of the project and the view of the 'stories' within it makes it really easy to organize iterations and have a clear understanding of what everyone is working, what you have to work on, what has been completed, and what has yet to be completed. Where Pivotal Tracker can improve is on the management of stories. It's not impossible, but as often happens on software projects, developers start something and move to other things if they get stuck or need to address something more pressing. I feel that there need to be some controls around starting and 'pausing' stories and clearly identifying that they've been put on pause. Not a big deal. Pivotal Tracker integrates into other applications like Slack, Git, Bugzilla, Usersnap, and a plethora of others.

Pivotal Tracker is well suited for companies that manage multiple software projects with onshore and even offshore teams. More specifically, it's appropriate for teams that use an agile or pseudo-agile project methodology. Pivotal Tracker is not so well suited for software projects that follow a waterfall or other form of project methodology.

We used Pivotal Tracker some months ago when we decided to implement scrum inside the team. I used Pivotal tracker for some time around 2011 and I knew you have to use the "pivotal way" to be able to enjoy the tool. This is the main advantage and also the main flaw of the tool.

If you have a team that has almost no process and wants to start doing something, Pivotal Tracker may help you with that. You first need to check the process the tool proposes (mostly scrum) and decides if it's what you want or not. If you think it's exactly what you need, start with Pivotal Tracker because it will enforce a lot of things to your sprints.

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.

I believe Pivotal Tracker is well-suited for any project, large or small. It scales up for large companies with many users, or can cater to a single user with a personal project. On a fundamental scale, it is a great platform to just get all you ideas out on paper. Large stories can be broken down into smaller ones, and it gives good insight on what is nice-to-have vs imperative.

We have been using Pivotal Tracker (PT) to track and manage our sprints. It allows us to simply place all of our work and assign it to specific engineers. One of the key things it helps us do is track the stage and age of tasks to help get a good understanding of where things are.

I think PT would be great if your team religiously stuck to sprints however we are more fluid than that and so I think some of the features do not make a difference to us.

Out of all the tools I have seen I do think it is the best for managing sprints however it is not a good external facing roadmap. However, I do not think it is trying to be that.

Currently, Pivotal tracker is being used by my graphics and technology department to track their work tasks on their day to day work. We have been able to successfully monitor and track work to ensure there are no dropped or missed items. Currently, we are looking into expanding to use this software with our support service team to track additional client work. At this moment, the difficulty in expanding this software across our entire business is the fluidity of categorizing stories to look for matches in the system.

When working with a new team member, some of the first questions we are always asked is "What can I do next?" with the use of this tool, we have our new tech hires review pivotal for all outstanding work; assign to them what they believe they can handle and make an attempt. This has let us known what is being worked on and where difficulties and training is needed within our organization.