Try our new research platform with insights from 80,000+ expert users

Microsoft Azure DevOps vs Planview AgilePlace comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

Microsoft Azure DevOps
Ranking in Application Lifecycle Management (ALM) Suites
2nd
Ranking in Enterprise Agile Planning Tools
1st
Average Rating
8.2
Reviews Sentiment
7.6
Number of Reviews
130
Ranking in other categories
Release Automation (1st)
Planview AgilePlace
Ranking in Application Lifecycle Management (ALM) Suites
17th
Ranking in Enterprise Agile Planning Tools
11th
Average Rating
9.0
Number of Reviews
11
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of November 2024, in the Application Lifecycle Management (ALM) Suites category, the mindshare of Microsoft Azure DevOps is 21.8%, down from 26.5% compared to the previous year. The mindshare of Planview AgilePlace is 1.5%, up from 1.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Lifecycle Management (ALM) Suites
 

Featured Reviews

Akshat Prakash - PeerSpot reviewer
Allows us to deploy code to production without releasing certain features immediately and agile project management capabilities offer resource-leveling
My company has experienced benefits from using it or from recent updates in Azure Pipelines. For instance, we can manage different code versions from the same repository across different environments. We also use feature flags; the code is deployed, but the feature can be made visible to the end user at a later time. Additionally, as part of the deployment, we integrate automated and regression testing, which stops the deployment if testing fails, thus preventing regression bugs. This saves time and increases productivity by reducing the need for manual testing. Lastly, it integrates with the project management aspects, allowing us to link code deployments with project milestones. Azure DevOps supported our shift towards DevOps culture or practices. We shifted to the cloud environment and started migrating from our data centers about eight or nine years back. It has been a long journey. However, we have used Azure DevOps for almost five to six years in every project. We also use automation testing in Azure, so we have an integrated test suite that allows us to perform functional and regression testing effectively via the Azure DevOps system.
NS
Gives us visibility into projects and enables users to leave comments on different projects
We use the submit feedback button pretty often. I encourage the teams to use that if they see anything that could be improved. But we've been really happy with how fast LeanKit improves. The biggest improvement would be the API and data connections and making the data more accessible or quicker to access. One of our team members has brought up actual-time tracking on a card as a potential improvement. They had an interest in knowing how long a specific card had been worked on by a specific user or somebody that was assigned to that card. But there's not really a way for them to start and stop a time that they were actually working on it, except for if we created a different lane and they dragged it into the lane and then stopped using it in the lane. They requested that there'd be some sort of timer function on each one of the tasks.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The CI/CD pipeline setup is more user-friendly. You can manage various stages, and there are over 400+ plugins available for each stage."
"In Microsoft Azure DevOps, you have a one shop to get everything."
"The installation is very straightforward."
"Most of the features are very valuable for us, especially the source code control and task management."
"It is easy to use. The shared repository is useful. Everything is in one environment."
"There are a lot of helpful features available for tracking dependencies."
"The initial setup is very easy."
"DevOps is easy to use because we can arrange each task in a project and follow up with the testing, development, and business teams. We manage everything through this."
"Using the tool seems to save time versus trying to do things in a regular manner. It is highly collaborative; everybody can see things in one place. It is a highly functional, but pretty simple tool. That is hard to find: A tool that has a lot of functions, but is also simple."
"Adoption across stakeholders and visibility have been the biggest success for us with LeanKit."
"LeanKit is amazing when it comes to getting answers about a given card's status. That's one of the biggest takeaways that we've had. The status is right there on the board. Everybody can see it. You just click on it and it gives you everything that you need to know, especially the comments feature because it gives us a timeline of updates. We use that a lot where we write a comment on the card and then we can see and track progress as we move it across the board."
"People found the ability to set up different lanes and the ability to see where they're within the progress most valuable. They can use different colored cards or sticky notes, and then they can separate out which cards belong to a department or the initiative they're working on. They can filter who's working on it, and I've got good feedback about that."
"It makes work visible, so everybody knows where everything is. It uses Kanban, and that makes work visible."
"The transparency that it brings is valuable. I like to look at things from all angles, and sometimes, flip chart paper on a wall and sticky notes are better than something on a screen, but the way they've made it accessible from all points for anyone within an organization is great. As a project management guy, sometimes, you have to force people into new environments where they have to see what you're talking about. Any screen is a barrier, and people got to get into the screen. How do you know they do? You don't necessarily know, but you are getting around that barrier with a countermeasure of making it accessible to as many as possible. So, everyone can jump in there and see everything. It is fully transparent, and I like that. This is one thing that helps."
"I would say it's highly scalable. LeanKit can scale across the enterprise easily. Every business could probably find a use case for leveraging LeanKit."
"My team specifically uses our board for all of our Remedy tickets that come in. We had a card for every ticket that we get, and we're able to add the link to that specific ticket there.If I'm out of office, for example, and someone else needs to work a ticket or someone is being contacted to work on a ticket, I don't have to sign on it. Someone else can easily access that ticket because I put the link in there. It's nice. It has a lot of great functionality in there."
 

Cons

"Microsoft Azure DevOps could improve by having better integration with other email servers."
"It is not that intuitive. Sometimes, it is hard to find some of the functions. I would like to have an old-fashioned menu structure to be able to easily find things. Its environment setup is not very good. They should improve the way it is set up for different screens and make it easier to find functionalities and maintain team members."
"The communication could work better, especially for the development team."
"All of the tests of the applications are done on the mobile or web interface and it could be improved."
"We are facing some problems because the capacity can only be measured within a project. It cannot be measured across multiple projects. So, the reporting needs to be enhanced, and there should be more graphs to be able to easily give the upper management insights about all the employees from different departments. It will be helpful for employee management. Currently, the managers over here are using Power BI for insights because the functionality of Azure DevOps Boards is not enough. So, we have to export the data into another visualization tool and get the results."
"Templates could be improved."
"The portfolio is one area where DevOps has room for improvement. Built-in reporting and visualization also could be better. We're using Power BI and Tableau to compile more complex reports and dashboards. Azure DevOps has some out-of-the-box reporting capabilities, but they're very simple. It's usually okay on the team level, but if you have to run a complex report, it's difficult and insufficient, so we use Power BI as an extension."
"Its interface could be more user-friendly. It could be simplified for users with no prior knowledge. There should also be better tutorials."
"There's room for improvement with the Instant Coffee feature. There are other businesses that have been interested in leveraging a virtual whiteboard or sticky note capability and how Instant Coffee was developed has not met the mark."
"The integration with the Enterprise One product is probably an area for improvement. It's not really broken. It's just that it is such a handy tool and a great way to visually manage things. There is a very limited hookup/integration between Enterprise One, which is the master Planview tool, and LeanKit. While they are looking at this on their roadmap, it definitely needs to happen. There is a lot of opportunity there."
"We are a 750-employee company, so we got lucky that our board approved the kind of funding we needed for the solution. But, LeanKit probably needs to reduce its pricing."
"Within the current features, if they can give some ability to show more icons on the card, it would be helpful. It would help us in showing more data on the cards."
"I do not know what it can do in the area of scrum. Maybe it has that functionality. I have never tried to set it up. You think of LeanKit from the perspective of Kanban. I don't know if there is a template for scrum, a scaled agile framework, or any of those scaling frameworks."
"It is a pretty good product. It is really hard to think of things that I'd want to be improved. Sometimes, we use it for project management lessons learned. So, we have three columns, such as Could be Improved, Keep Doing, and Works Really Well. It would be helpful if there was a template set up for something like that because we code different cards based on the category. For example, if something belongs to the Could be Improved category, we may have those cards as yellow, but then I have to change the color of them and put a header. It is not as smooth, but it still works fine. To be honest, I don't have a lot of complaints about it."
"Our overall impression of Leankit has been very positive, however, our experience with the JIRA integration into our Leankit boards was much harder than we anticipated and that could be improved by simplifying it somehow."
"The ability to report on customizable fields and third-party extensions needs improvement. I'd like to see more of those being able to be used. I don't know how that works for Planview, but just getting a little bit more added there would be nice."
 

Pricing and Cost Advice

"The costs are moderate and justify the value provided."
"I find that the pricing is good, and it is competitive with the other vendors in the market."
"With Azure, you have to pay for every user."
"The price of the solution is expensive."
"Its pricing is reasonable for the number of features that you get and the functionality that you can utilize for the agile delivery, which is what we are using it for. I found it extremely cost-effective."
"We pay a monthly license for Microsoft Azure DevOps."
"The price of this solution is fair."
"I am not aware of any licensing subscriptions for the solution."
"As far as I understand, it is not an expensive application."
"I don't know what it would be on its own. It was basically included with what we were already paying or using. So, it was a no-brainer. It wasn't like we had to sell the company on making a purchase or anything like that. There weren't any costs that came in after implementing it."
"In general, Planview's cost structure is reasonable. You get quite a lot of functionality for the license cost that you get."
"I don't believe there are any costs in addition to the standard licensing fees."
report
Use our free recommendation engine to learn which Application Lifecycle Management (ALM) Suites solutions are best for your needs.
816,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
13%
Computer Software Company
12%
Financial Services Firm
12%
Government
9%
Financial Services Firm
26%
Insurance Company
12%
Manufacturing Company
11%
Healthcare Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

Which is better - Jira or Microsoft Azure DevOps?
Jira is a great centralized tool for just about everything, from local team management to keeping track of products and work logs. It is easy to implement and navigate, and it is stable and scalabl...
Which is better - TFS or Azure DevOps?
TFS and Azure DevOps are different in many ways. TFS was designed for admins, and only offers incremental improvements. In addition, TFS seems complicated to use and I don’t think it has a very fri...
What do you like most about Microsoft Azure DevOps?
Valuable features for project management and tracking in Azure DevOps include a portal displaying test results, check-in/check-out activity, and developer/tester productivity.
Ask a question
Earn 20 points
 

Also Known As

Azure DevOps, VSTS, Visual Studio Team Services, MS Azure DevOps
Planview LeanKit, LeanKit
 

Learn More

Video not available
 

Overview

 

Sample Customers

Alaska Airlines, Iberia Airlines, Columbia, Skype
REA Group, Thompson Reuters
Find out what your peers are saying about Microsoft Azure DevOps vs. Planview AgilePlace and other solutions. Updated: November 2024.
816,406 professionals have used our research since 2012.