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 7.6 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.
N/A
Pricing
Pivotal Tracker
Rally Software
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Pivotal Tracker
Rally Software
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Pivotal Tracker
Rally Software
Considered Both Products
Pivotal Tracker
Verified User
Project Manager
Chose Pivotal Tracker
Rally is too complicated - there are far too many fields that all have the same meaning. It's a better agile tool in my opinion since it it was designed purely as an agile tool, but since the CA technologies acquisition, the tool has become more complicated and there are far …
Compared to Rally the tool seems more accessible because or the suite of apps available. It also feels more polished and stable than Rally. It definitely has more tools and features but again it can be overkill for a smaller team or project.
Pivotal Tracker is a one page dashboard where Rally, one has to go to different pages to see everything in more detail or makes edits. In Rally I feel everything is stored away and the dashboard is not as easy to find to figure out the acceleration of group. Rally is used at my …
Rally has much more features with regards to the the traditional Agile methodology and has more extensive tracking features for the project managers. Pivotal Tracker was used for a smaller company and smaller teams but since my current company is larger in scale and has more to …
I've also evaluated the following agile solutions: ActiveCollab, Agile Bench, Agilo for Scrum, Atlassian JIRA, Pivotal Tracker, SpringGround, Targetprocess. Telerik Teamprocess, VersionOne, ZebraPlan etc. If it’s time to transition to software that’s specific to your Agile …
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.
Rally is well suited to help outline the specific tasks of a project, create timelines, indicate progress/status of tasks and provide views of team members' workloads. My team used it for our weekly stand up meetings in order to update one another on our progress, and our manager used it as a way to determine who had capacity for additional tasks. It facilitated our transition to a more agile work environment and we used it to implement 2 week "sprints".
There are dashboards that provide friendly and useful metrics at the team, program and portfolio levels which help get an easy and quick visual representation of what's going on.
Story management made easier, It offers a quick way of quickly entering a number of user stories without losing the overview, by just typing the title and selecting a few attributes directly in the overview screen.
Sprint management is seamless in CA Agile Central . It allows you to drag stories from the backlog to the sprints and back again. When a story is dragged into an sprint, it automatically checks the velocity for that sprint and indicates how many more story points can be chipped in. No more manual checking needed by scrum master with respect to allocation and team velocity.
Though CA Agile Central has many inbuilt apps, but it also has an App-SDK that allows you to build free app extensions using JavaScript and HTML. So, as per their needs, teams can customize & build various apps & dashboards.
Dashboard is an awesome feature which allows you to select and drag panels with all kinds of graphical information about the current sprints and releases.
It offers tremendous support for scaled Agile & almost all scaling frameworks are supported specifically tuned to SAFe .
CA Agile Central includes several applications but it also integrates well with Jira, Confluence, Jenkins, Eclipse, Subversion, IBM, HP, Salesforce.com and many other products to allow users to organize projects to their specifications. So you can still use Jira at a team level & CA Agile Central at the program & portfolio level for efficient tracking & management.
The custom tags are very helpful in segregating the user stories based on the project needs. Even though it's a very small feature, it is very effective ( you will realize why specifically if you are using Jira).
CA Central Agile enables agile delivery with ease and provides comprehensive features to track time-boxes, Work In Progress items of the forecast increments.
Backlog management is hassle free since you can either drag and drop your user stories to the desired position on the backlog, or change a setting and manually enter priorities as a number.
In-story task management is still a weak point. The ability to @mention users in tasks and mark tasks as 'in-progress' would go a long way.
Epics do not span projects. This becomes troublesome when scaling Pivotal Tracker's agile methodology to multiple teams.
Splitting stories is often confusing for team members as there is no concept of a 'parent' story with child stories that have split off of it. There are only two levels: Epic & Story.
User management is pretty basic and could be better. For example more filters and reports and more ability to do mass updates.
The report generator is very, very basic and is not WYSIWYG. It has limited filters to generate reports. Often a Scrum master will need to export data to Excel or a tool like Crystal Reports to get enhanced reporting capability.
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
We have had employees in the past look at Drupal, and other open source project management tools to assist in our needs. Unfortunately each solution took too much time to implement, design and configure that we could not stop the work we were doing for clients to complete a full set up of a project tracker. Thankfully Pivotal is a predefined solution with no configuration needed. Simply input your projects, design your Stories with Tasks and begin your tracking.
It was a close race between Jama, JIRA and Rally. We decided to go for Jama as a requirements management tool and use Rally for Agile projects. The cost was another factor that made us select Rally.
Time is money with development and a lot of things can fall through the cracks. Having a good system for making sure you're building the most relevant product for customers is really important so it was well worth it for us.
The process we used worked for us and it helped us streamline our development which reduced a lot of things falling through the cracks and headaches. I'm sure there are other products that can do the same job just as effectively but Pivotal Tracker worked well for us.
it helped organizing many of the processes management use to communicate tasks with engineers, and provided detailed charts on the speed/blockage during any iteration
with time Rally became the main tool we used to track and report tasks/defects in our projects, but frequent service outages made it very hard to continue consider as a reliable solution
too much features is good, but for engineers a few features (User Stories section, iterations, defects, and Kanban boards) are necessary and the rest is just noise