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)
Mattermost
Score 9.0 out of 10
Enterprise companies (1,001+ employees)
Mattermost from the company of the same name in Palo Alto is a messaging, collaboration and communication platform providing high security and compliance for the businesses that need it.
$0
per month per user
Pricing
Azure DevOps Services
Mattermost
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)
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 …
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 …
One of the foremost reasons that acted in favor of Azure DevOps was its all-in-one packed web portal which enabled easy access to all the CI/CD tools and kits. Customizable screens, notifications via Teams/mails, project views, etc. Most other tools/products offer only part of …
While GitLab has the same features as Azure DevOps, and a potentially more competitive price, its project management features are a bit more primitive. It could be helpful for small projects, but ultimately for our larger projects we went with Azure DevOps. Bitbucket has good …
Azure DevOps provides a full workflow from planning through to development through to production. After the acquisition of GitHub by Microsoft, GitHub is becoming more fully-featured with the features being ported becoming more polished in the transition. Both are great …
DevOps is more full-featured than its on-prem predecessor or any of the above with the possible exception of the Atlassian suite. I would say those two are roughly comparable. However, the ease of integration is much better with DevOps and other Microsoft products (although …
They are really close. Azure DevOps is better because of the deep integration with Microsoft technologies. Jira is better on the customization side. However, Azure DevOps is really improving on that front. They are releasing new features every other week now. Azure DevOps also …
They're very similar. I think it's really a matter of preference. Again, one of the things I like about Mattermost is that it's strictly for business (atleast for us) it's different from the more mainstream messaging apps used so we can kind of separate work vs personal messages.
Much more expensive than most chat applications but you have more control over things by self-hosting. Your security team will be able to design a very secure place to store all your code, passwords, and internal details, but most companies will not require this. It would be …
In comparison to Slack, where Slack is strictly for internal communication, Mattermost actually has the format to display and not alter source code. Google chat is also even more limited in comparison to Slack and Mattermost. If you collaborate on code every single day, then …
These products all required cloud connectivity and licensing that was a significant cost. Mattermost allowed us to pilot this among just the Ops team and then evangelize this to the other infrastructure team. This allowed us to slowly show the value of this software and expand …
Unlike Slack and Discord, Mattermost is self-hosted and focused on security. I used Discord before for community management and much simpler and less secure operations. Slack is great, but the fact that is cloud based takes out a lot of its independence.
We used to have Mattermost and now we have Microsoft Teams. They are both very similar. Mattermost and Microsoft Teams are both great for communicating internally via calls, chats, meetings, etc. They are also both easy to set up an use. However, the Microsoft Teams mobile app …
Mattermost works better in that there aren’t constant updates and changes which can make finding past messages difficult. Mattermost also works better for channel creation and communication
Honestly iv just used these two but when it comes to customization, they don't come close to Mattermost. Slack and Teams are Less flexible, Not self hosted. Not Open source,etc I will also say that i noticed integration capabilities are very limited with teams and slack and not …
Mattermost is much faster and easier to use. It also has many more features beyond chat. They are more customizations and features for workflow and messaging on this platform also. The ability to integrate with other platforms via plugins, the security features, and the open …
I feel slack is a bit more difficult to use overall than Mattermost. Mattermost makes the tasks of communicating across departments and team members easier, as well as giving the ability to share information via hyper links, attachments, and other forms of communication among …
We selected mattermost since we can control storage of our data. Slack is a great tool and offers more robust features compared to mattermost. However, the previously mentioned reason & the competitive pricing allowed us to stick with mattermost.
Microsoft Teams feels quite clunky and the video chat is buggy. Slack is close but maybe not quite as feature-rich. Mattermost just feels like the right tool for a company my size ~1000+ users. No one has had any major issues with this tool and there haven't been any …
First of all, we don't lose messages; we can see or search messages from any point in the past. Second, it offers to manage the whole product ourselves from hosting to serving users of our organisation. We feel that we have full control over data, managing users, …
ADO is well suited for the visibility of day-to-day tasks and responsibilities as well as things such as Features, user stories, etc. Off the top of my head, I can't think of any scenario where it might not be well suited, as you can customize ADO to your liking to a degree.
Mattermost is definitely appropriate for a growing company with team members spread out across the u.s. and Canada. It’s given me the ability to have access to anyone with the information I need or the ability to develop friendships, working relationships with people I otherwise wouldn’t have access to
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.
Need to make the changes so that it doesn't occupy most of the CPU utilization and memory
Execution of Bulky SQl Queries leads to either the SQl being out of exception or the VS being unresponsive
Integration with Microsoft products is easy, but with non-Microsoft products it is more difficult, and you have to make a lot of configuration changes to integrate
With every upgrade of the Visual Studio, like from VS 2010 to VS 2013 , we need to upgrade our hardware/machine, as the VS hardware requirement also increases
If code is getting compiled in one visual studio, like in VS 2010, that the same code could possibly give an error when compiled in VS 2013, due to certain changes in keyword, data format, etc., with the VS upgrade
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.
Mattermost works perfectly within our company as a way to communicate seamlessly. I have had no issues with the product and continue to use it often while on and off site. The mobile app allows me to continue to communicate with my team even when I don't have my laptop with me.
Azure DevOps is a powerful, complex cloud application. As such there are a number of things it does great and something where there is room for improvement. One of those areas would be in usability. In my opinion it relies too much on search. There is no easy way to view all projects or to group them in a logical way. You need to search for everything.
It's an extremely easy to use software, and I would recommend it to every company that is growing. I think they could improve their notification system, as it gets a little spammy sometimes and important notifications get lost. Also needs to improve the number of private chats that you are allowed to create.
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.
We have not had to contact support for Mattermost ever. All that we have needed has been available in the documentation or website. One of our DevOps team members set it up in a couple of hours. The whole team was using Mattermost that same day. No support needed.
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 interfaces, I feel it would be a complete project management system.
Unlike Slack and Discord, Mattermost is self-hosted and focused on security. I used Discord before for community management and much simpler and less secure operations. Slack is great, but the fact that is cloud based takes out a lot of its independence.
The platform is adaptive to storage data center outages in case our cloud storage provider goes away, Mattermost still works with our local database. However, files couldn't be shared. We can switch storage to local temporarily; that's a benefit. Later it all syncs up to main storage.
When our team switched to Mattermost from paid solutions, we had much savings and access to unlimited past messages and storage quota (we use our cloud storage provider)
We have better visibility of our tools and other products running adjacent to Mattermost due to integration capability. We use it for notifications/ updates sent from other products.