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)
Broadcom Clarity
Score 4.8 out of 10
N/A
Broadcom Clarity (formerly CA Project Portfolio Manamagement) features project, resource, staffing and budget management; scenario comparisons; forecasting; and labor, expense, materials and equipment management.
N/A
Planview Portfolios
Score 8.5 out of 10
N/A
Planview Portfolios is an end-to-end project portfolio management and enterprise architecture management tool. It includes two components: Portfolio and Resource Management and Capability and Technology Management. The platform is available as a cloud-based or on-premise service.
N/A
Pricing
Azure DevOps
Broadcom Clarity
Planview Portfolios
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
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Azure DevOps
Broadcom Clarity
Planview Portfolios
Free Trial
No
No
No
Free/Freemium Version
No
No
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
Azure DevOps
Broadcom Clarity
Planview Portfolios
Considered Multiple 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 …
Planview and Microsoft Project have many similar features. However, the direct contact with the Planview team for questions, tech support, and training is unprecedented and appreciated. Microsoft Project: -Weaknesses: Limited to single project management, lacks risk and time …
Planview Portfolios is the market leader in the area, the flexibility of the product and the continuous investment by Planview makes Planview Portfolios currently the best in the market. The support organisation for implementation and run of Planview Portfolios rounds off the …
We are just in the process of deploying AgilePlace and will connect with Portfolios Smartsheet, which does have the functionality we need. We are just starting to use AgilePlace. We have a business group doing a proof of concept.
Planview has been growing continuously in the last decade or so, and its acquisitions of some big players in the market have imparted much-needed confidence in the tool. The ability to integrate Planview using APIs, Snap Logic, or Planview's own tool, 'Hub,' makes it stand out …
We are currently in the process of evaluating but so far Planview seems to fit our needs the best. Portfolios was selected prior to me joining the team.
Planview has much more potential in terms of it's products and capabilities. It can integrate more easily with many more of our other products and software. Planview reporting is much more intuitive.
Planview Portfolios has an extremely robust data structure that supports many different use cases. Its customizability, large suite of features, and great customer service makes it a fantastic and scalable solution for many different businesses and business process …
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.
Planview Portfolios is well suited to provide a single, central, view of the truth. There is clear expansion capabilities to integrate it as a true Enterprise toolset with existing organisation wide (not just delivery) - you can pick and choose what you need to implement and that list gets longer. The ability to quickly gain an understanding of resources within the overall portfolio and some really clever tools regarding capacity and demand modelling. I think the only challenge we have encountered is modelling our Business as Usual activity to a level of detail - this is due to other tools being very embedded not just in the organisation but across a lot of industries.
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.
Out of the box analytics. Canned, but modestly configurable reports that provide quick insights to project and resource performance.
Flexible configuration enables resource management at a macro or micro level.
Modeling (what-if). I can create projects, load with resources and quickly stack it against our existing portfolios to identify conflicts and optimize scheduling.
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.
Portfolios are useful enterprise solutions for new and old use cases. They have robust reporting capabilities and many opportunities to customize the functions without additional costs. Although some desired features are still in development, and the reporting infrastructure has some issues, Portfolios continue to offer more capabilities than we can take advantage of at any 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.).
Perfect tool for planning resource time management. Giving flexibility with ease in uptodate . Team collabration . Team aligment. Top management aligment. Close the project with feed back . Team aligment. Expert contribution in task . Task management easy for project manager . Nice tool to have for project manager. Cost contol & project management is very easy with Planview
We are long time Planview users and its availability is only limited to our internal SLAs for nightly backups. I have never experienced any unexpected or prolonged software downtime from Planview itself.
There are occasions when the system is a bit sluggish. However, it may not always be on the Planview side. We are investing in better tools to monitor our network performance, which will help us diagnose issues more effectively in the future.
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.
Consultants are knowledgeable and friendly; it is easy to build relationships with the support people you work with and they learn how best to help you. The vendor is continuously looking for honest feedback about their tool and they use that information to design their product roadmaps
Always have a pre-implementation meeting or conference call with Planview to ensure all are on the same page, disclosure of all and any customization (including reports) and plan for support after implementation of a specified amount of time with the assigned implementation resource. And document everything
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.
We are currently using Planview AgilePlace. Also we use Tasktop Hub for integrating with other applications within the organization. We would like to use ProjectPlace which is integrated with Planview Portfolios in the future.
We are constantly growing and expanding. It is challenging to accommodate different user needs, but the system does provide means of doing that as we desire.
The positive impact is the ability to manage our projects enterprise wide.
Managing and reporting on projects and programs via portfolios makes it easy to identify troubled projects/programs that need immediate attention.
The negative is that pushing too much change too quickly is hard for us. We need to get our users focused on the basics of PM before we can adopt everything else. We need to introduce change to different companies based on their maturity level. Too much change too quickly is not always beneficial. We need to focus on core competencies.