Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
Planview AgilePlace
Score 7.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
Planview AgilePlace
Editions & Modules
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
Basic + Test Plan
$52
per user per month
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
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
Planview AgilePlace
Considered Both Products
Azure DevOps
Verified User
Anonymous
Chose Azure DevOps
This is the first platform our dev team shared to us so I can't really compare but overall its such a great tool to have even if you are not from tech or dev team.
We would use App Center for distributing our app to testers, and we could implement the same functionality as was handled by App Center, and as far as I remember we even had some automatic conversion of our jobs from App Center. After the conversion, we could see that Azure …
We love the multi-tier hierarchy in Azure DevOps for tasks, with epics, features, stories, bugs and tasks all available in a nice nested hierarchy. It's not as pretty as Monday.com and doesn't work as well OOTB as ServiceNow SPM however.
It is a similar tools with its pros and cons but does not really a differential - I would say it does the same but its own way, sometimes better, other times worst. It is a matter of preference or demands that come from superior decisions, so you just have to take it.
Jira is fantastic for project management and customer facing portal. It is not good for pure development (no integration with Git, pipeline management, automated testing features). If DevOps were to integrate and adopt the project features of Jira as well as the customer facing …
The moment I have been working with this tool everything has benn operating efficiently. The software development process has borne positive results under scalable environment. The cost of running Azure DevOps Services us much lower as compared to other tools in the market. It …
ADO has better linking than Confluence and is adaptable for a specific need, whereas Confluence might be a bit more rigid, but it's also sort of along the same lines as to what can be done with both tools. ADO also had an ease of use to it and can do a bunch of stuff with it, …
Jira is super clunky and doesn't behave in a modern fashion. monday.com is too flexible and doesn't provide enough feature set. AWS is the most competitive, but it's hard to wrap your brain around all of the features and offerings provided by amazon. ADO does a better job of …
Azure DevOps has a drag and drop editor so that you can quickly drag build steps into a build or release pipeline. This is much faster than looking up the correct yaml syntax. Additionally, its support for Microsoft and Azure is great. If you're on the .net stack or you use …
Azure DevOps has more services and better integration with other tools. When it. Comes to the overall software development process management ecosystem.
Microsoft Planner is used by project managers and IT service managers across our organization for task tracking and running their team meetings. Azure DevOps works better than Planner for software development teams but might possibly be too complex for non-software teams or …
Trello is simple to use, but it's only for a Kanban board. Jira might be the same, but I don't really have enough experience with Jira to fully compare them. When I used it, it missed certain functionalities that I was used to in Azure DevOps. Visually it's a lot different too.
Azure DevOps Services have huge functionality and are well supported by Microsoft as well. You will get plenty of features in the marketplace and learning documentation.
Writing the Docker Images, Storing them in Azure Container Registry and then Deploying onto Azure Kubernetes Services is an Easier process which no other software/product is currently providing in the market. Best till date in terms of End to End deployment and maintaining …
Azure DevOps is widely used because of its collaboration and integration with various other tools. Here the assign of the sub task is quite easy compare to Jira. Also Azure Devops can we integrate easily with Git for better code representation and versioning. It reporting is …
Azure DevOps is a completed product and ecosystem. It offers a robust ecosystem that does everything that is needed. The above products do lack features like pipelines tasks, third-party integrations. Besides all cloud benefits, the main advantage of Azure DevOps Services …
Currently, we use both products, however, we use more the Atlassian suite. We have started recently using Azure DevOps for specific implementations and projects. We don't have any plan yet to migrate all our projects to Azure DevOps, we may in the next couple of years. …
We tested alternatives for Azure DevOps over time. We tested GitHub a while ago and back then lack of some features that now hast, like the project boards and private repositories. We will check GitHub next year.
We also tested AWS CodeCommit and found it very cryptic, …
Beside all cloud benefits, the main advantage Azure DevOps Services compared to Azure DevOps Server is the easier remote access for third party team members, and always up to date software. On the other hand, on prem deployment (Azure DevOps Server) makes complex access or …
The greatest strength of Azure DevOps Services (formerly VSTS) is that it's a one-stop solution for all agile project management instead of setting up bits of different software put together for each and every need. Azure DevOps Services (formerly VSTS) has a great ecosystem …
I prefer Azure Devops over all other code repository / ci/cd systems that I've used in the past. All features are integrated into a single service (back log, repo mgmt, deployment pipelines, artifacts, etc.). The tools are easy to use and super powerful.
Our company is already using a lot of Azure services and it makes more sense to start using Azure DevOps Services (formerly VSTS) when we needed a CI/CD tool. We tested different features of Azure DevOps Services (formerly VSTS) and found out that the build and release …
AgilePlace is better than JIRA when it comes to ease of use and intuitiveness of the tool. Card based model and ability to customize/tailor the way you want makes AgilePlace is a great tool. Look and feel as well as colored cards, makes the board layout much more easier to …
All these tools are different and have different uses. Depending upon SDLC your organization uses, you would use any of these tools. They all have their plusses and minuses.
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.
Front-End Web Developer, Office of Mediated Education
Chose Planview AgilePlace
I use Trello a bit for personal use. It's much less powerful than LeanKit, but it's also a better design and simpler to use. ServiceNow has some kanban board stuff built-in, but I wasn't super impressed with it. JIRA seemed to be even more complex than LeanKit for the short …
I think that LeanKit is very similar to Asana's Kanban feature and Trello, but is much less sleek looking than Asana. Asana's clean and sleek UI makes me enjoy project management much more than LeanKit. It might sound silly that the UI makes so much of a difference to me, but …
Our company uses LeanKit, Pivotal Tracker, and Trello. It all depends on what team you're on. There's even a team that just does KanBan on a whiteboard. In the end, I would tank LeanKit above Pivotal Tracker, but below Trello. The differences are relatively subtle between …
Both VersionOne and Trello are good products. VersionOne is for the real hardcore Agile shops who want to track and report on everything related to the Agile process. Trello is a tool that works for Agile, but really is just a simple list making/tracking tool. Both tools serve …
I have used Trello, which is not as robust for tracking and customizing workflows as LeanKit is. It does not scale well to big teams. JIRA is the standard project management software but does not support Kanban well.
Nearly all the other tools I evaluated against are free, so that's one area where LeanKit is not as competitive. LeanKit does allow the experience to be much more customizable, though.
Being from QA I prefer Spiratest and QC for the fact my team can do all our work in one program and it is linked. But the tech department as a whole prefers Leankit as it is the tool of choice based on ease of use and overall performance.
While LeanKit was not designed for project and task management, we selected it because of its collaborative nature as a project and task management platform for our marketing team. It was also selected because our engineering and product management teams were using Leankit. We …
DevOps is much more user friendly than Git itself. There is a more GUI-centric interface, tighter integration with the Azure / Entra architecture. For those of use in the Microsoft-sphere, it really is excellent for code-centric project management. I rate this as an 8 because it does not seem quite as well suited for fully functional / non-code project aspects in implementation. Nor does it have customer / end-user portal / front end for easy reporting and insight.
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.
Flexible Requirements Hierarchy Management: AZDO makes it easy to track items such as features or epics as a flat list, or as a hierarchy in which you can track the parent-child relationship.
Fast Data Entry: AZDO was designed to facilitate quick data entry to capture work items quickly, while still enabling detailed capture of acceptance criteria and item properties.
Excel Integration: AZDO stands out for its integration with MS Excel, which enables quick updates for bulk items.
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.
I did mention it has good visibility in terms of linking, but sometimes items do get lost, so if there was a better way to manage that, that would be great.
The wiki is not the prettiest thing to look at, so it could have refinements there.
I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.
It's a great help to get more information about new feature release and stay updated on what the dev team is working on. I like how easy it is to just login and read through the work items. Each work item has basic details: Title, Description, Assigned to, State, Area (what it belongs to), and iteration (when it’s worked on). See image above.They move through different states (New → Discovery → Ready for Prod → etc.).
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.
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
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.
We love the multi-tier hierarchy in Azure DevOps for tasks, with epics, features, stories, bugs and tasks all available in a nice nested hierarchy. It's not as pretty as monday.com and doesn't work as well OOTB as ServiceNow SPM however.
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.