Pivotal Tracker is a project management program primarily for software developers. It is built from the ground up to facilitate the agile development cycle, and is optimized for structuring projects in sprints, or “stories.”
The solution is now owned and supported by VMware, and is part of the Pivotal / Tanzu product line up.
N/A
Rally Software
Score 6.8 out of 10
N/A
Rally Software headquartered in Boulder, Colorado developed the Rally agile software development / ALM platform which was acquired by CA Technologies and rebranded as CA Agile Central. After CA's acquisition by Broadcom the software was once again rebranded as Rally.
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.
If your organisation is planning to adopt Scaled Agile Framework Methodology (SAFe) without being worried about cost, CA Agile Central is one of the best tools. Here, you can look at various release trains and how that then flows up to the overall program budget. You can look holistically across all the release trains with minimal effort and have it flow up to the program office’s budget. It also helps by easily maintaining backlogs and integrating more seamlessly into software developers releases, iterations, and features. It has no conformance issue as it supports almost all the browsers like IE from version 8.0, Firefox from 3.6 and the newest versions of Chrome (from 6.0) and Safari (from 4.0).
Pivotal Tracker helps our team visualize our projects in the form of stories (virtual cards) moving through our workflow. This encourages us to break down projects into manageable chunks and have important conversations about deliverables and scope.
The forced-prioritization allows our team to have a shared understanding about what is most important and make collective decisions about what our team will work on next.
By dividing future iterations by our team's velocity, Pivotal Tracker accurately predicts when we will complete future work.
structuring teams separately in a clean way. You can add as much teams as you want, and guarantee each team's work would stay separate in browsing, graphs and analytics.
detailed menus and drop-downs listing of features - technically it covers all there is of agile aspects and some more
ability to set your email notifications on/off
ability to split user stories into the next iteration if work isn't done in the previous one - no need to duplicate your user story manually
Used to have a newsfeed-type feature with all the updates from the previous day. They removed it. I liked getting a snapchat of what changed from before.
When signing up for email alerts, can be inundated with emails for every change to the status of a story.
Communication on stories through the comment section can be a little difficult, and not very organized.
Assuming we were paying - right now my group gets it for free as the broader engineering organization pays for it. There would be switching costs. There would be pretty minimal data migration, but the biggest cost is getting people to learn a new tool and starting off on the right footing. Evaluation and identification of the right product is a big part of switching too
It works good enough. I didn't have many problems with that. The user interface is a bit confusing though. The team took some time to understand where some configurations were.
Great UI, recent refresh was terrific. Great graphs and metrics, inline editing for updates, and a multitude of views on sprint progress make for a great team collaboration experience. There is also an active community and forums so that if you do need help, it is readily available
The screens render relatively quickly but many actions that you would expect to require a single click require multiple clicks and pop-up windows. The extra windows and clicks make the product feel ponderous.
We've never had to request support in the 5 years I have been using it. A solid solution! Everything I have had questions about is on the website. New features are in their newsletter with more details on their website. Often I am using the new features within a few minutes of reading the article.
I've had to use support only one time and my issue was eventually resolved but not because of my ticket--because others complained about the functionality taken away so they brought it back. My ticket was never answered or addressed. So I can't really say much for the support factor for Rally.
It more or less confirmed that we are using it the way they had in mind. We were hoping for a epiphany in terms of how we could use it better.
They also want to be a go to source for agile processes and have an online resource center. It’s not that great but had a couple of nuggets. It hasn’t really helped us too much and we are not too far off from the classical interpretation of agile.
I would recommend training, in particular for organizations that multiple on-going projects. The product seems optimized for larger, more complex teams and getting proper training on how to configure, administer and use the system would be beneficial
Implementation of RALLY services and program satisfaction among various group,... 1) Dev Outcomes: How were our resiliencies, development, learning & practitioners “make them do the work,” but that they ask you to do it “in a way like before. 2) The Ops group: Just wish to make sure any change won't break current production envirements All the stake holders has to be on the same page
Pivotal Tracker, Asana and Trello all have free versions making them ideal for smaller companies to try out. All of them blast Kannan boards and issue tracking capabilities. While Trello and Asana are great products in themselves, Pivotal Tracker edges them out with its wealth of features including trackability of epics, burndowns, better reporting, and analytics. JIRA, on the other hand, is way more customizable, has more reporting capabilities and more features than Pivotal Tracker but is more expensive too. At the end of the day, it comes down to what you're looking for in an agile project management tool as well as how much you're willing to pay for it.
Rally and Asana have comparable features and are both valuable project management tools, but Asana's user interface is well-organized and highly intuitive. It's easy to add tasks and collaborators, edit due dates, indicate progress on tasks, close out projects, etc. However, Rally's interface is somewhat cluttered and difficult to navigate. My team ended up choosing Asana over Rally due to these concerns.
Pivotal Tracker has been a cost-effective solution for what we need. It has allowed our ROI to be greater than if we went with another system.
Learning curve; with this easy to use tool, it has been a shorter learning curve for new hires to find what they need to accomplish their task.
Flexibility; we are right now stuck at 4 levels of classification; project; Story, Task, Comments. If we were able to expand on this, we would be able to role this out faster to other departments within our business.
