AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine running Azure DevOps Server.
N/A
Pivotal Tracker
Score 7.2 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.
Jira has been growing in hardware design teams since is being integrated with CAD software. The best of Azure is that you can manage since level of access control to multiple types of teams. Another bonus is that Jira has more mobile features that let your team stay connected …
Because of the microsoft ecosystem and the product is also build on ms services cloud which uses azure internal services so it is easy to integrate. more reliant support available for the microsoft services because of the well established user community of the product and …
Azure DevOps is a fully integrated solution that solves all of the problems that our separate tools did in a much easier-to-use way. Before we implemented DevOps we had three different solutions that we had to integrate with each other and required a lot of manual intervention …
Managing projects is a breeze using Azure DevOps Server, and the tool also automates testing and checks to see if the project is within its scope. Intuitive, with a low learning curve for novice users; it's also simple to collaborate on projects and keep tabs on their progress …
Honestly speaking, GitHub is better in terms of version control and JIRA has better functionality when it comes to Agile boards, other than that, the UI could have been a bit better for Azure DevOps Server. In all other areas, I feel overall Azure DevOps Server is better.
In my opinion, DevOps covers the development process end to end way better than JIRA or GitHub. Both competitors are nice in their specific fields but DevOps provides a more comprehensive package in my opinion. It is still crazy to see that the whole suite can be used for free. …
I was new to the agile methodology when it was first introduced to the Enterprise. Different project teams opted to leverage different project management tools, two of the most common being Jira and DevOps. For someone overcoming a huge learning curve already, I felt that …
My organization already has an established Microsoft relationship which allowed us to move faster in procuring the product. The alternative would require my large organization to move at a snail's pace at procurement. This is not necessarily a hindrance for most other …
I was not involved in the purchase decision for this product. Since I have started working at my company, we have always used [Azure DevOps Server]. So I can't comment on how it performs vs its competitors. I have used many project management tools that are not as robust, but I …
I've used and currently use JIRA, which is a similar software to Azure DevOps Server. Azure DevOps Server is more detailed and comprehensive than JIRA. They both offer many of the same features and capabilities but Azure has a better overall interface and is more in-depth. It …
Azure DevOps Server is a fantastic tool and my favorite for organization and management of large application building projects. It was selected for its ease of use with a user-friendly design that allows any team members, particularly outside of developers, to quickly get up to …
At the time we brought Azure DevOps in-house it really was the only game in town. Our company migrated from Visual SourceSafe to TFS to Azure DevOps without any issues or downtime. Git isn't overly intuitive so I never recommend it and shy away from it. I loved it when …
Microsoft Azure DevOps is the one that integrates everything you can possibly use and provides a solution that eases your developing process. It has a strong support community and well-written documentation. No matter what you do, you will always find the right pipeline. It is …
Azure DevOps server has quite an upper hand while we compare it with other tools in the market. Its not just a tool in fact its been a complete suit. If we look out at other products available as alternative options to Azure DevOps Server, they are meant for a specific purpose …
TFS gives and edge over JIRA for inbuilt version controlling that TFS has. TFS provides a GIT version control repository that offers centralized TFVC and distributed GIT Version control. Version controlling is a key feature that promoted TFS over JIRA in the implementation of a …
The advantage of Team Foundation Server is the integration capability with Microsoft technologies and products, such as Visual Studio. Although this is an important consideration, Team Foundation Server is not a straightforward tool and needs to be improved to work seamlessly …
Git and GitHub are very popular right now and they are OK. But they do not integrate automated Testing and Building... The Work Item Management of Jira is about as complicated as the one of TFS so we use Trello. The other Source Control Systems are more complex to use because …
JIRA is very user friendly. It's ideal for people new to the software development lifecycle and the tracking of the work. They have simply nailed the intuitiveness. Pivotal Tracker might be the better long-term tool because of the flexibility that comes with it. But as …
I have used a number of systems like Pivotal Tracker over the last 15 years. I have had several occasions to use Wrike separate from and alongside Pivotal Tracker. Wrike was more difficult to use and seems to either be locked down by permissions, so I had to "fight" to do my …
The only thing that PT compares to is Salesforce and we now utilize both platforms - Salesforce is a bit more organized in its automated task flow and allows us to connect our other platforms to it for efficient data transfer and data consistency.
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 …
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 …
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. …
JIRA allows teams to tailor the application workflow to meet their needs, while "opinionated" Pivotal Tracker enforces a consistent workflow approach on all team members. While I, personally, may prefer to have a system configured to my particular habits and desires as a …
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.
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 …
I've used Jira ages ago, and it was still a young product in its initial iterations. The UI was a clunky and was missing a lot of ease with drag and drop for individual stories, uploads, etc. Management of users was useable, but not as ideal as it could be.
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 …
We were using JIRA and found it lacking in their UI and some of their services, especially communication. PT communicates much easier with simple links to tasks for execution and QA review.
Basecamp is just really a super note taking and asset depot. I would not consider true …
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, 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 …
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 …
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.
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 …
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 …
Jira is very complex, while tracker is more straightforward to use. Tracker requires less micromanagement and upkeep. Asana is pretty but not useful for product and engineering build. It is more geared towards design projects.
In our case it was best suited when we started working remotely, we were able to track everything in out projects easily, able to share our codes, give reviews for the codes and also create integration and deployment CI/CD plans for the release and testing. It helped our team members with the productivity, early prototyping and release. Create summarised reports of different aspect of our projects. Even in other scenarios it is one of the best tools to use for collaboration and project management. I haven't found any specific scenario where it is not appropriate
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 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.
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.
Because we are a Microsoft Gold Partner we utilize most of their software and we have so much invested in Team Foundation Server now it would take a catastrophic amount of time and resources to switch to a different product.
For standard users the interface is friendly. but if you are a manager some tools are a little confusing to use, like the query system that you always need to create from scratch. Templates should be more helpful for queries and for standard procedures that you need to duplicate PBIs over time. The search history of Work Items is a little painful to use.
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.
I have not had to use the support for Azure DevOps Server. There have never been any issues where I was not able to figure it out or quickly resolve. Our Scrum Master has used support before though, and the service has always been prompt and clear with a customer-focus
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.
Azure DevOps is a fully integrated solution that solves all of the problems that our separate tools did in a much easier-to-use way. Before we implemented DevOps we had three different solutions that we had to integrate with each other and required a lot of manual intervention to make sure they worked correctly.
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.
It has streamlined the pipeline and project management for our agile effort.
It has helped our agile team get organized since that is a new methodology being leveraged within the Enterprise.
The calendar has improved visibility into different OOOs across the project team since we all come from different departments across the larger organization.
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.