What is our primary use case?
While DevOps is a well-established area offering robust capabilities, our focus lies in its adaptability to our specific needs. It enhances collaboration and project management. Additionally, we leverage DevOps for its robust reporting capabilities, which empower us to make informed decisions and track progress effectively.
How has it helped my organization?
When implementing CI/CD workflows using Azure DevOps, we leverage its standard model as our foundation. However, we also integrate third-party tools such as Jenkins, NGINX, Argo, and Tecton, all of which are compatible with Azure DevOps. This interoperability greatly benefits us, as Azure DevOps seamlessly integrates with these tools, enhancing our workflow capabilities.
Azure DevOps has significantly enhanced our team's agile project management and planning processes. One notable capability is the rapid setup time of a new Azure DevOps system, often completed within minutes, eliminating the need for extensive setup hassles. Additionally, once established, the platform has proven to be highly robust, with no instances of downtime or performance issues encountered. This stability extends over the years, with projects maintained on Azure DevOps for two to three years remaining consistently stable. This reliability ensures that projects don't slow down or require intricate management, as Azure DevOps provides a seamless and dependable solution.
Azure Boards has significantly enhanced our team's collaboration efforts. We have a long history of using the platform, even before it was branded as Azure DevOps, with various name changes over the past five years. Boards are a particularly powerful feature, offering ready-made templates that serve as a solid foundation for project management. Additionally, the platform allows for customization, enabling users to tailor boards to specific project needs. This flexibility extends to offering different boards for different management levels, catering to both team and executive needs.
Azure Test Plans have significantly improved the quality and efficiency of our testing process by incorporating test cases and methodologies seamlessly into the suite. It serves as a one-stop solution for our testing needs, empowering both developers and QA teams to identify and address issues that impact overall quality.
Since adopting Azure Pipelines, we've witnessed significant improvements in our release management processes. It serves as a one-stop solution for CI/CD, offering maturity and flexibility. We have the autonomy to configure our CI/CD pipelines according to our specific needs, whether we choose to implement continuous integration (CI) only or both CI and continuous delivery (CD), either manually or automated. While there is potential for enhancement in providing more out-of-the-box CI/CD templates, overall, teams have not encountered any significant issues with Azure Pipelines.
What is most valuable?
Two of the most valuable features include the integrated project management suite, which consolidates source code and project management in a single location, and its powerful reporting capabilities.
What needs improvement?
There's potential for Microsoft to enhance third-party integrations. This could streamline the testing process by providing access to these tools directly within Azure DevOps, eliminating the need for separate subscriptions and browsers. While reporting in Azure DevOps is a robust capability, there's always room for enhancement, particularly in providing more granular reports. Also, integrating Co-pilot, Microsoft's AI-powered tool, into Azure DevOps could greatly enhance the platform and potentially offer valuable assistance and insights throughout the development process.
For how long have I used the solution?
We have been working with it for the last five years.
What do I think about the stability of the solution?
The system is exceptionally robust and reliable, and we rarely encounter any performance issues. I would rate it eight out of ten.
What do I think about the scalability of the solution?
It's capable of handling large volumes of data, project archives, source code, and more without any issues. Around three thousand developers regularly engage with Azure DevOps in various capacities. We have plans to expand its usage in the future. I would rate it eight out of ten.
Which solution did I use previously and why did I switch?
We have been part of the Microsoft Compliance journey through its rebranding to the integration into Microsoft Studio. In addition to Azure DevOps, we also utilize Jira, including both Jira Cloud and on-premises versions, as well as other project management tools like Monday.com and Asana, catering to various customer preferences and requirements.
How was the initial setup?
The initial setup was quite intuitive. I would rate it eight out of ten.
What about the implementation team?
Deployment time is swift and efficient. Once we initiate the process, the team typically has it available within minutes. For maintenance, we have a team of two people.
What was our ROI?
The return on investment is evident in the ease and compatibility Azure DevOps provides, sparing us from the complexities of managing additional products while focusing on building our own. This capability adds tremendous value to the entire value chain we offer to our customers. I would rate it six out of ten.
What's my experience with pricing, setup cost, and licensing?
The pricing of Azure DevOps falls within the average range and it is fixed. When evaluating costs, it is not a significant expense for our organization. I would rate it four out of ten.
Which other solutions did I evaluate?
We conducted evaluations of other vendors as well, with Jira emerging as the strongest contender at that time. When considering an on-premises solution, particularly for internal team collaboration, an internal instance of Jira suffices, leveraging available compute units and VMs within the organization. However, for external client collaboration, especially when teams are geographically dispersed, Azure DevOps in the cloud presents a more viable option. Additionally, Azure DevOps offers an intuitive interface for efficient project management and source code integration. From a cost perspective, Azure DevOps proves to be more economical, priced at seven dollars per user.
What other advice do I have?
Azure DevOps is a highly stable and robust product, providing users with a dependable experience. It offers more functionality than initially anticipated, making it essential to explore its full capabilities beyond just storage management or source code usage. It's crucial for users to thoroughly understand the product and its features to leverage its full potential. We are highly satisfied with it as we haven't encountered significant problems where the product itself is unresponsive or features are failing to load. Performance issues, authentication failures, and other common concerns are non-existent, as the standard mechanisms work flawlessly for us. Overall, I would rate it eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure