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

Microsoft Azure DevOps vs Planview AgilePlace comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 15, 2024

Review summaries and opinions

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

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.1
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
Reviews Sentiment
7.2
Number of Reviews
11
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of January 2025, in the Application Lifecycle Management (ALM) Suites category, the mindshare of Microsoft Azure DevOps is 20.3%, down from 26.2% compared to the previous year. The mindshare of Planview AgilePlace is 1.5%, up from 1.2% 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

"I really like the Microsoft DevOps survey."
"You can have test cases in DevOps but not in JIRA. And, DevOps has advantages in terms of executing those test cases."
"Everything that's related to the pipeline has been very good."
"Azure is an advantage when working with other Microsoft solutions."
"Fields can be customized and the reporting is good."
"The solution integrates well with other Azure services and third-party tools."
"Most developers and project managers choose the Microsoft tools to begin with because of familiarity, and these new tools are almost an extension of the tools you're already familiar with. There's a lot of knowledge transfer, which helps, rather than bringing in a new product line."
"I like the tracking and that we can monitor our velocity."
"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."
"Adoption across stakeholders and visibility have been the biggest success for us with LeanKit."
"We use the board and card hierarchies in terms of sprints so that we can see if we have cross-functional teams that are working on the same projects together, especially when projects have dependencies. The parent-child relationship within cards is really nice so that we can see what kind of dependencies there are when we're trying to get projects finished."
"It makes work visible, so everybody knows where everything is. It uses Kanban, and that makes work visible."
"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."
"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."
"The "Blocking" feature has helped our scrum masters track impediments and share them at the program level to stakeholders with accountability and detail so that they understand and the action items which can be noted easily."
"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."
 

Cons

"One potential enhancement in Azure DevOps could be integrating more customizable reporting features, particularly for Power BI integration."
"The only downside is that the deployment could be a little challenging but it is manageable."
"Non-functional testing such as security testing, log testing, and performance testing can be improved with a better visualization."
"Templates could be improved."
"I think that they have some menus there that are not very well placed."
"Microsoft could improve Visual Studio by making it easier to find the plugins you need to get your job done. Maybe they could implement an AI search instead of a simple tech search. Sometimes, people come up with a catchy name for something, and you don't know how it's spelled. For example, a developer might come up with a packet wizard and spell weird, like P-A-K-I-T."
"I'd like to have something better for the test plan."
"I can't think of anything I would like to improve, since I don't have complete knowledge of the platform yet. I'm sure that as I gain more experience, I will understand it better. The price could maybe be cheaper, but I'm sure I'll have more ideas as to improvements and additional features once I've used it more."
"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."
"They have a feature called Instant Coffee. It was in the beta phase. They released it from beta, and now, it is a legit thing. We were in the pilot here. I liked the idea of Instant Coffee, and I like how it is integrated, to some degree, with LeanKit, but I have two big rocks to throw at them on this. The first one is that Instant Coffee does not save your work very well in terms of saving it in formats that you can then go back and edit as Visio would. It leads to the next point, which is, we're not really clear on what they're trying to do with Instant Coffee. I feel that they're trying not to reinvent Visio, Miro, and other software programs out there that do mapping, visual diagrams, etc. Miro is fantastic in that regard. I gather they're not trying to reinvent Miro, but it sure would be nice if it had more aspects of Miro in it, such as being able to draw arrows and write on them on the top."
"Being able to track actual time on cards or sprints, instead of using just the planned start and stop date, would also be useful. I would like to see something like JIRA has with actual sprint starts and stops."
"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."
"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."
"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."
"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."
"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."
 

Pricing and Cost Advice

"The price is reasonable for the solution."
"We pay a monthly license for Microsoft Azure DevOps."
"The pricing of Azure DevOps falls within the average range and it is fixed."
"The main agile features are very expensive."
"Microsoft Azure DevOps is an expensive solution."
"Microsoft Azure DevOps is free for up to five users and allows you to track a maximum of three projects."
"With Azure, you have to pay for every user."
"There are other solutions available that are open source and free, such as GitLab."
"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."
"As far as I understand, it is not an expensive application."
"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.
831,158 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
27%
Insurance Company
13%
Manufacturing Company
10%
Computer Software 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: January 2025.
831,158 professionals have used our research since 2012.