AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine running Azure DevOps Server.
N/A
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.
Jira has been growing in hardware design teams since is being integrated with CAD software. The best of Azure is that you can manage since level of access control to multiple types of teams. Another bonus is that Jira has more mobile features that let your team stay connected …
Because of the microsoft ecosystem and the product is also build on ms services cloud which uses azure internal services so it is easy to integrate. more reliant support available for the microsoft services because of the well established user community of the product and …
Azure DevOps is a fully integrated solution that solves all of the problems that our separate tools did in a much easier-to-use way. Before we implemented DevOps we had three different solutions that we had to integrate with each other and required a lot of manual intervention …
Managing projects is a breeze using Azure DevOps Server, and the tool also automates testing and checks to see if the project is within its scope. Intuitive, with a low learning curve for novice users; it's also simple to collaborate on projects and keep tabs on their progress …
Honestly speaking, GitHub is better in terms of version control and JIRA has better functionality when it comes to Agile boards, other than that, the UI could have been a bit better for Azure DevOps Server. In all other areas, I feel overall Azure DevOps Server is better.
In my opinion, DevOps covers the development process end to end way better than JIRA or GitHub. Both competitors are nice in their specific fields but DevOps provides a more comprehensive package in my opinion. It is still crazy to see that the whole suite can be used for free. …
I was new to the agile methodology when it was first introduced to the Enterprise. Different project teams opted to leverage different project management tools, two of the most common being Jira and DevOps. For someone overcoming a huge learning curve already, I felt that …
My organization already has an established Microsoft relationship which allowed us to move faster in procuring the product. The alternative would require my large organization to move at a snail's pace at procurement. This is not necessarily a hindrance for most other …
I was not involved in the purchase decision for this product. Since I have started working at my company, we have always used [Azure DevOps Server]. So I can't comment on how it performs vs its competitors. I have used many project management tools that are not as robust, but I …
I've used and currently use JIRA, which is a similar software to Azure DevOps Server. Azure DevOps Server is more detailed and comprehensive than JIRA. They both offer many of the same features and capabilities but Azure has a better overall interface and is more in-depth. It …
Azure DevOps Server is a fantastic tool and my favorite for organization and management of large application building projects. It was selected for its ease of use with a user-friendly design that allows any team members, particularly outside of developers, to quickly get up to …
At the time we brought Azure DevOps in-house it really was the only game in town. Our company migrated from Visual SourceSafe to TFS to Azure DevOps without any issues or downtime. Git isn't overly intuitive so I never recommend it and shy away from it. I loved it when …
Microsoft Azure DevOps is the one that integrates everything you can possibly use and provides a solution that eases your developing process. It has a strong support community and well-written documentation. No matter what you do, you will always find the right pipeline. It is …
Azure DevOps server has quite an upper hand while we compare it with other tools in the market. Its not just a tool in fact its been a complete suit. If we look out at other products available as alternative options to Azure DevOps Server, they are meant for a specific purpose …
TFS gives and edge over JIRA for inbuilt version controlling that TFS has. TFS provides a GIT version control repository that offers centralized TFVC and distributed GIT Version control. Version controlling is a key feature that promoted TFS over JIRA in the implementation of a …
The advantage of Team Foundation Server is the integration capability with Microsoft technologies and products, such as Visual Studio. Although this is an important consideration, Team Foundation Server is not a straightforward tool and needs to be improved to work seamlessly …
Git and GitHub are very popular right now and they are OK. But they do not integrate automated Testing and Building... The Work Item Management of Jira is about as complicated as the one of TFS so we use Trello. The other Source Control Systems are more complex to use because …
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, …
In our case it was best suited when we started working remotely, we were able to track everything in out projects easily, able to share our codes, give reviews for the codes and also create integration and deployment CI/CD plans for the release and testing. It helped our team members with the productivity, early prototyping and release. Create summarised reports of different aspect of our projects. Even in other scenarios it is one of the best tools to use for collaboration and project management. I haven't found any specific scenario where it is not appropriate
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
Because we are a Microsoft Gold Partner we utilize most of their software and we have so much invested in Team Foundation Server now it would take a catastrophic amount of time and resources to switch to a different product.
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.
For standard users the interface is friendly. but if you are a manager some tools are a little confusing to use, like the query system that you always need to create from scratch. Templates should be more helpful for queries and for standard procedures that you need to duplicate PBIs over time. The search history of Work Items is a little painful to use.
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.
I have not had to use the support for Azure DevOps Server. There have never been any issues where I was not able to figure it out or quickly resolve. Our Scrum Master has used support before though, and the service has always been prompt and clear with a customer-focus
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.
Azure DevOps is a fully integrated solution that solves all of the problems that our separate tools did in a much easier-to-use way. Before we implemented DevOps we had three different solutions that we had to integrate with each other and required a lot of manual intervention to make sure they worked correctly.
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.
It has streamlined the pipeline and project management for our agile effort.
It has helped our agile team get organized since that is a new methodology being leveraged within the Enterprise.
The calendar has improved visibility into different OOOs across the project team since we all come from different departments across the larger organization.
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.