We performed a comparison between Microsoft Azure DevOps and Planview AgilePlace based on real PeerSpot user reviews.
Find out in this report how the two Application Lifecycle Management (ALM) Suites solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The reports have been most valuable. We have created some dashboards allowing us to be able to check our teams, their progress, and mission plans."
"It's got something that you won't find in other products."
"The solution is easy to implement and easy to use."
"It is good for the purpose it is designed for. It is good for maintaining a repository of application code, creating pipelines for deploying the code, building the code, and deploying the code. It can be easily used by developers. There are no issues."
"The most valuable feature is that we can run integrations with DevOps. From a QA perspective and a testing perspective, we can run those tests and integrate automation tools. Then we can run those tests as part of the deployment process. Every time we are deploying something, it automatically runs all the tests."
"Azure is an advantage when working with other Microsoft solutions."
"Technical support has been excellent. On that side, Microsoft is very good. The customer support of Microsoft has really improved this past year. On the cloud side also we are very satisfied because it offers very good support."
"The most valuable features are continuous integration and deployment, and simplicity."
"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."
"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."
"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."
"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."
"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."
"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."
"All of the tests of the applications are done on the mobile or web interface and it could be improved."
"Requirements management is an area that can be improved."
"They have to add more features such as schedules and more flexibility in the platform."
"The solution's roadmap and Gantt charts could be improved."
"It would be very useful if it had better integration with Microsoft Word because we would like to be able to define the priority requirement document and add it to different stages of the backlog."
"When converting to DevOps, it was difficult to map."
"The UI, the user experience, is challenging for newcomers."
"While reporting in Azure DevOps is a robust capability, there's always room for enhancement, particularly in providing more granular reports."
"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 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."
"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."
"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 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."
"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."
Earn 20 points
Microsoft Azure DevOps is ranked 2nd in Application Lifecycle Management (ALM) Suites with 127 reviews while Planview AgilePlace is ranked 17th in Application Lifecycle Management (ALM) Suites. Microsoft Azure DevOps is rated 8.2, while Planview AgilePlace is rated 9.0. The top reviewer of Microsoft Azure DevOps writes "Allows us to deploy code to production without releasing certain features immediately and agile project management capabilities offer resource-leveling". On the other hand, the top reviewer of Planview AgilePlace writes "Gives us visibility into projects and enables users to leave comments on different projects". Microsoft Azure DevOps is most compared with GitLab, Jira, TFS, Rally Software and AWS Amplify, whereas Planview AgilePlace is most compared with Jira, Jira Align, Rally Software and Digital.ai Agility. See our Microsoft Azure DevOps vs. Planview AgilePlace report.
See our list of best Application Lifecycle Management (ALM) Suites vendors and best Enterprise Agile Planning Tools vendors.
We monitor all Application Lifecycle Management (ALM) Suites reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.