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
Planview AgilePlace
Score 9.9 out of 10
N/A
AgilePlace is a project management solution built around flexibility, data-driven analytics, and workflow automation. The software was acquired by Planview in December 2017 to expand that company's capabilities.
$19
per user, per month
Pricing
Azure DevOps Server
Planview AgilePlace
Editions & Modules
No answers on this topic
Teams
$19
per user, per month
Scaled Teams
$29
per user, per month
Custom
Contact Sales for Quote
per user, per month
Offerings
Pricing Offerings
Azure DevOps Server
Planview AgilePlace
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
All editions include unlimited boards.
More Pricing Information
Community Pulse
Azure DevOps Server
Planview AgilePlace
Features
Azure DevOps Server
Planview AgilePlace
Project Management
Comparison of Project Management features of Product A and Product B
Azure DevOps Server
-
Ratings
Planview AgilePlace
7.4
Ratings
3% below category average
Task Management
00 Ratings
10.00 Ratings
Resource Management
00 Ratings
9.90 Ratings
Gantt Charts
00 Ratings
10.00 Ratings
Scheduling
00 Ratings
9.90 Ratings
Support for Agile Methodology
00 Ratings
9.30 Ratings
Support for Waterfall Methodology
00 Ratings
4.00 Ratings
Document Management
00 Ratings
6.50 Ratings
Email integration
00 Ratings
7.30 Ratings
Mobile Access
00 Ratings
2.10 Ratings
Timesheet Tracking
00 Ratings
6.40 Ratings
Change request and Case Management
00 Ratings
7.20 Ratings
Visual planning tools
00 Ratings
7.30 Ratings
Agile Development
Comparison of Agile Development features of Product A and Product B
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
AgilePlace is a great way for teams, or individuals, to bring visibility to the work in process and in their backlog. The color coding and icon use helps to quickly analyze the type of work or status of the work. The product team is doing a good job at listening to their user's feedback and implementing improvements. Where it falls short is when reporting needs to occur.
Okta Integration: We love using SSO for all our SaaS apps, and as new team members join, they can be automatically joined to the appropriate LeanKit boards.
Filtering and viewing: Can filter and refine by several fields as well as custom fields. Assigned Users, Tagged, Card Type, Date, etc
Their analytics and reporting can be helpful for PMs, especially if they have several teams they oversee.
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.
LeanKit isn't the best designed Kanban system I've seen, but overall it's pretty usable. The boards I've used are pretty complex, so it can be difficult to find things. I found that searching and filtering for specific cards was somewhat of a challenge. Dragging a card from one lane to another is kind of a fun way to get things done though.
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
Every time I have reached out to the AgilePlace support team I have received a timely response in addition to professional & personal feedback. Their consultants are knowledgeable and the management team is happy to jump in and help when needed.
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.
Originally, we had evaluated two other tools next to Planview LeanKit: Kanbantool and Kanbanflow. The latter was a close contestant for productive use, as it was also very customizable and a joy to work with and look at. It also had lower user fees and a mobile integration. In the end, we picked Planview LeanKit because of several reasons: Aesthetics: The look was much more clean and professional. Reporting: It was obvious from the start that we could use Planview LeanKit as a tool for improvement. API: We needed to integrate the Kanban into our central systems and Planview LeanKit API was (and still is) a way to do it. Card Headers: This sounds like a simple thing, but the headers above the titles fit our work perfectly and looked perfect, which helped the decision.
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.