Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
Pivotal Tracker
Score 5.0 out of 10
N/A
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
Trello
Score 8.4 out of 10
N/A
Trello from Atlassian is a project management tool based on a Kanban framework. Trello is ideal for task-management in a to-do list format. It supports sharing boards and cards across users or teams. The product offers a free version, and paid versions add greater automation, collaboration, and administrative control.
$6
per month per user
Pricing
Azure DevOps
Pivotal Tracker
Trello
Editions & Modules
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
Basic + Test Plan
$52
per user per month
No answers on this topic
Standard
$6
per month per user
Premium
$12.50
per month per user
Enterprise
$17.50
per month per user
Free
Forever Free
Offerings
Pricing Offerings
Azure DevOps
Pivotal Tracker
Trello
Free Trial
No
Yes
No
Free/Freemium Version
No
No
Yes
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
A discount is offered for annual billing and for larger numbers of users.
More Pricing Information
Community Pulse
Azure DevOps
Pivotal Tracker
Trello
Considered Multiple Products
Azure DevOps
Verified User
Consultant
Chose Azure DevOps
VSTS is better than these options because there is integration with git and other services. Code reviews, branching, etc. are easier with VSTS. Although, Trello and Excel are probably better if you have smaller teams and smaller projects, I believe it isn't scalable. But if you …
Trello is simple to use, but it's only for a Kanban board. Jira might be the same, but I don't really have enough experience with Jira to fully compare them. When I used it, it missed certain functionalities that I was used to in Azure DevOps. Visually it's a lot different too.
Azure DevOps covers way more than just an awesome Agile storyboard. The widgets, the reporting, the interaction with Power BI and the features that hook into pull requests and DevOps in general, go way beyond what your competitors offer. I find Azure DevOps easy to navigate …
Compared to other tools we have used, Microsoft STS has been a much more complete tool. Communication, collaboration, tracking, management, automation, testing, speed to production—all these areas have been improved since we started using Microsoft STS. We have been looking for …
We are moving away from VSTS to Version One since Version One has a better end to end workflow for a product based team (where product and development work very closely together and need to access the same data and communicate in an efficient manner.)
Unlike the other tools I have used, VSTS has everything under one roof. The other tools I have used are specific to a particular requirement like code version control, task management etc. VSTS on the other hand, has all aspects of the project tied together which makes it more …
I personally prefer Pivotal Tracker to Trello, but Trello has it's advantages. Trello, through its card system, allows for more organization at a more specific level than Pivotal Tracker does. Pivotal Tracker has better bug tracking with its status updates, and gives a project …
In my opinion, Trello is more of a pretty UI than a agile tracker. So, if you have a technical team where you want to increase efficiency, I would go with Pivotal Tracker.
I have also used Trello and JIRA. A small company with only a couple of projects may be best suited with Trello due to its cost and simplicity, whereas JIRA may be better suited for a large company that can afford a dedicated JIRA manager, due to its complex configurations and …
Our organization actually does not exclusively use Pivotal. We also have teams on solutions like Trello and LeanKit. It's all preference, those who buy into all the agile features that pivotal provides, love it. Those who do not need all the overhead, simply use a different …
Pivotal Tracker, for better or worse, provides a more structured and rigid workflow than most. That makes it easy to get started, but if you have your own workflow you want to integrate into it, it could mean it'll take longer to get used to or customize. It's still more …
Compared to other task management tools, Pivotal Tracker has the best blend of functionality and cost. When you need something simpler than JIRA, and not solely focused on code or UI related tasks like BugHerd, and have a more direct approach to completing tasks than Trello - I …
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 …
It's not necessarily a matter of better vs. worse when it comes to all of these different tools. They all serve a different purpose to different sized teams. I found Pivotal Tracker and monday.com to be a matter of preference while serving a similar purpose. Good for smaller …
I haven't used dev-specific tools other than Pivotal Tracker but it's useful because it is built for a specific use case. The simplicity of an Asana or Trello is great and they have their advantages, but the additional functionality mentioned was worthwhile and a compelling …
Pivotal Tracker keeps users 'close' to the software project(s) by allowing users to understand, in plain words, the tasks and expectations of each software release, whereas other tools are either way too close to the source code or require an extensive amount of maintenance. …
We selected Pivotal Tracker because it is highly opinionated about the process. It worked quite well for what we were expecting from it. Other software we tried were much more flexible, so we could implement our own process there.
We selected Pivotal Tracker because of its simple, elegant workflow. This is the ideal; it's where we want to be. So we continue to improve, and as we get better, we get more out of the software.
The other software products we evaluated were too complex, and we found that …
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 …
I used to be a huge JIRA fan, until I realized how much time I was spending fixing complicated custom workflows and statuses. I spend almost no time administering Pivotal Tracking. And it turns out, those complicated, custom workflows weren't helping us anyway.
Overall I have found that I prefer using Pivotal over all the competitors I've tried. There are certain aspects of the other products which I do like but as a whole Pivotal does a better job. My one request is that I feel it is very much a web app and the other products have …
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.
Trello is very good for communicating plans between developers and management. It's much better than my memories of Pivotal Tracker, tries to provide better tools for agile methodology, but I found it rather difficult to use well. For initial planning within our team we use …
Azure DevOps works well when you’ve got larger delivery efforts with multiple teams and a lot of moving parts, and you need one place to plan work, track it properly, and see how everything links together. It’s especially useful when delivery and development are closely tied and you want backlog items, code and releases connected rather than spread across tools. Where it’s less of a fit is for small teams or simple pieces of work, as it can feel like more setup and process than you really need, and non-technical users often struggle with the interface. It also isn’t great if you want instant, easy programme-level views or a very visual planning experience without putting time into configuration.
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.
For teams or individuals with lots of individual tasks/details to track, Trello is perfect! It basically removes the need for a paper checklist. For those that need an overall project management tool that requires less tasks and more overarching goals, collaboration amongst various teams, and gantt charts I would suggest monday.com
I did mention it has good visibility in terms of linking, but sometimes items do get lost, so if there was a better way to manage that, that would be great.
The wiki is not the prettiest thing to look at, so it could have refinements there.
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.
I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.
I am very likely to renew Trello, because it doesn't cost anything to do so. I am also very likely to use Trello's upgraded features in the future because a lot of my team's data is stored on there and they have already gotten used to the platform. Trello is very easy for new team members to pick up, making the onboarding and usability very streamlined.
It's a great help to get more information about new feature release and stay updated on what the dev team is working on. I like how easy it is to just login and read through the work items. Each work item has basic details: Title, Description, Assigned to, State, Area (what it belongs to), and iteration (when it’s worked on). See image above.They move through different states (New → Discovery → Ready for Prod → etc.).
It was generally easy to use once you got the hang of it. The searching and tagging of tickets was fine, commenting worked well, and release planning was good. However, it wasn't the most intuitive tool in the beginning. The UI is pretty outdated and could have used upgrades over time.
Trello is incredibly intuitive, both on desktop and mobile right away. It is also full of helpful features that make it even easier to use, and is flexible enough to suit almost any organizational need. Onboarding for the software is thorough, but concise, and the service is frequently updated with even more QOL improvements.
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
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 haven't reached out to their support very often and their support is very limited anyway for the free users. They do have tons of great articles and videos in their Help Center and constantly send emails with updates and add-ons to the product. The fact that I've barely ever had to contact their support team means that they've developed a great product.
For our small business, getting a few of us started well on Trello was the key, I think. As long as a couple of us were really comfortable with the interface, we could lead others and help them with any questions. From now on, anyone who works with us just naturally uses Trello for information sharing - it's just part of what we do.
Microsoft Planner is used by project managers and IT service managers across our organization for task tracking and running their team meetings. Azure DevOps works better than Planner for software development teams but might possibly be too complex for non-software teams or more business-focused projects. We also use ServiceNow for IT service management and this tool provides better analysis and tracking of IT incidents, as Azure DevOps is more suited to development and project work for dev teams.
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.
Trello is more simple and not as "robust" as the other tools, but it's easier to use and manage and understand and ACTUALLY get stuff done with. It's simplicity is part of the beauty of using it. You don't need a million options that nobody uses, you just need to get stuff done.
We have saved a ton of time not calculating metrics by hand.
We no longer spend time writing out cards during planning, it goes straight to the board.
We no longer track separate documents to track overall department goals. We were able to create customized icons at the department level that lets us track each team's progress against our dept goals.
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.
Trello keeps me organized, focused, and on track. I could filter the Trello board to only see my issues and understand what I needed to work on and when.
Trello helped our team implement an agile structure. It's a very simple kanban method of viewing all of your team's tasks and statuses. You can completely customize the columns to your team's specific workflow and create tags relevant to your work.
Trello helps reduce unnecessary communications between teams. When I want to request translations, I simply create a card on the localization Trello board -- no need to directly message anyone on the team, and I can watch the status of the card change from "in progress" to "in review" to "translated," all without having to directly ask for updates.