Microsoft Azure DevOps Reviews

We build CI/CD pipelines. It's the Azure DevOps phase. Everything is in one place, like version control. CI/CD Pipelines, Release Pipelines. Everything is in there. 

So we have everything in one place basically. We use it as a complete end product.

The first thing is that everything is in one place. Azure DevOps integrates Secrets management, release pipelines, and build pipelines. 

The CI/CD pipeline setup is more user-friendly. You can manage various stages, and there are over 400+ plugins available for each stage. It's more user-friendly overall, which simplifies setting up pipelines and managing the workflows.

There is room for improvement on the UI side, especially with merge requests. If we compare Azure DevOps to GitLab when it comes to branches and PRs (pull requests), GitLab has a better interface.

Regarding CI/CD pipelines, Azure DevOps is improving. They're adding new plugins and making overall upgrades. For instance, they used to have only one type of pipeline, but now they have YAML-based release pipelines. Build pipelines are still under development, I believe, but their roadmap is in good shape.

They're also integrating IAM enablement directly into the UI. So, if you want to use the Azure portal to produce roles or make similar changes, you can now do that within Azure DevOps. It's a positive development. Overall, the roadmap for Azure DevOps is very strong.

I have been using it for six years. 

The stability is improving and looks very promising. Moreover, it's free. Initially, a subscription was required, but now Azure DevOps is provided for free if you are using the Microsoft Azure cloud and have that option enabled. 

So, it's a very stable product.

It's agent-based. You must manually configure a pool of agents to run all your pipelines and deployments anytime. There have been some disturbances with the agent pools, but they are improving. 

Initially, there were many issues with agent pool stability, but now, as you increase and update your agent pool, it becomes more robust. There isn't automatic scalability; you must ensure the agent pools are properly configured initially.

Myentire organization uses it because many projects under this organization use Azure DevOps. There are more than a thousand end users. 

The customer service and support are pretty good. There is a bunch of documentation out there. 

It is not to complicated to use. If there is something required, the support is accessible. 

I used Kitlabs, GitLab, GitOps, Jenkins, and Central Station, among others.

We looked at the features, and for one, Azure DevOps integrates all development and operations for continuous deployment in one place, which none of the other products offer in the market.

For Git, we needed repositories. 

The initial setup is of medium complexity compared to others. It's not too complex, nor is it too easy. It's a medium setup, and it includes all the key features. You can create departments, projects, and programs—everything is taken care of with Azure DevOps. 

It's like ServiceNow for continuous improvements and deployments in the DevOps world. Every project and support request I handle for clients has its challenges, but Azure DevOps manages these effectively.

Deploying code to your endpoint is a one-person job. You can configure your system, integrate your CI/CD pipeline, and set up authentication on your own. 

However, at an organizational level, where roles need managing and permissions must be assigned—for example, some can only handle releases while others manage builds—you need a robust access control system. 

In such cases, you would need two to three administrators to handle everything.

People involved in the process would be Azure DevOps admins, who control everything related to permissions and Azure DevOps operations, such as setting up pipelines, running deployments, etcetera. While our application teams handle some tasks, issues like access problems or agent failures are taken care of by the admins.

I would recommend using it.  Overall, I would rate the solution an eight out of ten.

We are using Microsoft Azure DevOps for project management using Azure Boards, CI/CD pipeline, repository, and test plans.

The most valuable feature of the solution is the pipeline. The solution integrates well with other Azure services and third-party tools.

The solution's roadmap and Gantt charts could be improved. We recently started using Azure Test Plans, and we're not seeing a lot of good dashboards in it.

I have been using Microsoft Azure DevOps for five years.

I rate the solution an eight out of ten for stability.

It is easy to scale the solution by increasing the number of agents. Our clients for Microsoft Azure DevOps are enterprise businesses.

I rate the solution a nine out of ten for scalability.

It took a few weeks for us to do the solution's initial setup.

Compared to other tools, Microsoft Azure DevOps is a cheap solution.

Microsoft Azure DevOps gives us an end-to-end solution. We could write the epics feature and user stories. From there, we could create the batches in the repository and create a pipeline to deploy. We can also use test plans to test different application scenarios. We are using Microsoft Azure DevOps as an enterprise-level solution.

Azure Boards have been good at improving our project tracking and agility. We are using the Azure repository, and it's working well for us. Microsoft Azure DevOps is deployed on the cloud, and we are using a Software as a Service (SaaS) version.

I would recommend the solution to other users because of its pricing and because it is an end-to-end platform for everything, including project management.

Overall, I rate the solution a seven out of ten.

Previously, our DevOps operations relied on TFS and Visual Studio systems. However, with the rise of cloud computing, Microsoft introduced Azure DevOps, a comprehensive solution encompassing version control, reporting, requirements management, project management, and automation tools, including testing and release management capabilities. It integrates seamlessly with Azure services, facilitating the development and deployment of applications on the cloud platform. It supports the entire software development lifecycle, from development to deployment. For instance, when developing a project, it assists in the build, test, and release processes, ensuring smooth progression to higher-level environments. 

Additionally, it supports project management activities such as user story management. Its features include repositories for storing code, pipelines for automating processes, and environments for managing deployment configurations. 

The platform has improved our team's productivity in the versioning system within the release management functionality. Each application deployment is assigned its version. When certain features are unavailable or require enhancement in a deployment, Microsoft incorporates these improvements into the subsequent version of the release pipeline. 

They could provide clearer guidance on deployment practices for the product. Currently, two main deployment methods are available: YAML server deployment and release management using pipelines or Terraform. They should offer recommendations on which approach is the best practice for deployment.

We have been using Microsoft Azure DevOps for 5 years.

It is a stable platform. Being a cloud-based solution, it benefits from zone redundancy policies, ensuring continuity even if one server experiences downtime.

We have more than 35 Microsoft Azure DevOps users in our organization.

The initial setup process is easy.

The costs are moderate and justify the value provided. With Azure DevOps, we can easily track your projects, monitor statistics and reports, manage backlogs, and plan deliveries. We can manage larger teams under one platform.

The product documentation contains all the necessary information to get started with the platform and understand its evolving features. Additionally, numerous resources are available on platforms like YouTube, where various vloggers share valuable insights and tutorials on using Azure DevOps effectively.

I rate it an eight.

We use the product end-to-end, from project management to CI/CD. We use the tool to create sprints and iterations, track bugs and issues, close down sprints, and have complete CI/CD pipelines end-to-end for all our branch's build releases.

The solution works smoothly. We have been using the tool for our projects since day one. It's easy to move around in the tool. All our projects are 100% on the cloud. Azure DevOps is an end-to-end solution. From project management to CI/CD, everything is connected. It speeds up our development and tracking.

The CI/CD feature is the most valuable for my team's productivity. All the features are helpful. The tool is helpful even in the test cases. We use Azure DevOps because it gives us everything in one product. Source control is useful. The tool enables us to track the projects end-to-end. We can track everything from the requirements stage to the production stage.

Azure Artifacts must be improved. When we do containerization or imaging, it is not friendly with Docker images. It might be because we are using open-source tools. There is no document that explains how to connect to Azure Artifacts when we're building a Docker container. 

The documentation must be straightforward. If we look online, it is very difficult to find or understand. The only way to connect to Azure Artifacts is to create a personal access token. Something doesn’t feel right with having the personal access token in the NuGet.config of our projects. However, it works fine.

I have been using the solution for 10 years.

The product’s stability is good enough.

The product is scalable. We have more than 40 users in our organization.

The setup is straightforward. Using the task and building the pipeline is not an issue. We spent a week trying to find out how to connect to Azure Artifacts. We need a normal .NET Core API and have the Docker file built. We must use a personal access token and keep it in the config files. It is not smooth enough.

The ROI is good enough. Once the system is set, we can focus on the core products.

We pay yearly licenses. The tool could be cheaper.

Microsoft Azure DevOps is the best choice because it is an end-to-end solution. Everything is integrated and trackable from every point. Right from my operations team to developers, everyone gets a clearer picture of everything. Overall, I rate the product a 9 out of 10.

As a software development team, we use Microsoft Azure DevOps extensively across various functions. We rely on its capabilities for source control, enabling us to efficiently manage our codebase and facilitate collaboration. Additionally, we leverage Azure DevOps for test management, including the creation and execution of test cases and test plans. Furthermore, we utilize its features for project planning, tracking work items, and generating weekly documents to ensure smooth progress tracking.

Azure DevOps has been instrumental in facilitating agile project management and collaboration within our team. We extensively utilize all the features offered by Azure DevOps, enabling us to seamlessly handle tasks such as test management, project management, software defect resolution, and source code management throughout the software development cycle.

We are leveraging the capabilities of Azure Repos for our source code management needs, finding them highly advantageous for our workflow.

Azure Pipelines have significantly improved our deployment process by enhancing automation. We utilize Azure Pipelines to standardize our build process, ensuring consistency in our artifacts and maintaining high-quality outputs. Additionally, it has enabled us to enhance our testing procedures, leading to more efficient issue detection and resolution.

Azure Test Plans have significantly influenced the quality of our releases. Acting as our test engine, they have played a crucial role in ensuring the quality of our software. Post-release, all identified defects are thoroughly addressed, and developers are requested to provide corresponding test cases to prevent recurrence of issues.

Azure Port is considered the most valuable feature.

When comparing with Jira, I find that the task management capabilities in Azure DevOps are not yet fully comprehensive and should be enhanced.

We have been using it for three years.

It provides good stability. I would rate it eight out of ten.

I would rate its scalability capabilities seven out of ten. Currently, approximately ten individuals utilize the platform. However, we plan to expand its usage in the future.

The initial setup was fairly complex and time-consuming. I would rate it four out of ten. During the initial setup, we encountered the most difficulty with Microsoft's documentation. It proved to be quite lengthy and lacked clear guidance, which made the setup process challenging. Consequently, we had to explore various additional resources to ensure a smoother setup of Azure DevOps.

For our initial deployment, we allocated one DevOps engineer who dedicated approximately one and a half months to complete the setup.

The cost is quite affordable.

The initialization process may pose some challenges, but I find that the investigation aspect is handled quite effectively. Overall, I believe it's well-suited for both general and specialized DevOps use cases. I would rate it seven out of ten.

As an architect, I use Azure DevOps for our projects, primarily focusing on setting up CI/CD workflows. We track tasks and maintain timesheets on Azure DevOps. I collaborate with project managers to define deployment pipelines and ensure smooth deployment processes. While Azure DevOps serves as our project management tool, my main role involves architecting deployment strategies and working closely with the project management team to implement them effectively.

Switching to Azure DevOps initially posed challenges, but as our team became familiar with it, we found it greatly improved our daily operations and productivity. Its streamlined processes made our development workflow more efficient.

What I like most about Azure DevOps is how easy it is to manage projects and control deployments. Once configured, team members can manage deployments if they have permissions. Additionally, the reports feature helps generate itemized invoices for the services provided to clients, which is valuable for billing purposes.

One potential enhancement in Azure DevOps could be integrating more customizable reporting features, particularly for Power BI integration, to provide better insights into project data.

I have been working with Azure DevOps for five years.

Azure DevOps is quite stable.

Azure DevOps is scalable and can be used in distributed environments and for different tenants.

Before Azure DevOps, we used various tools like Jira. We decided to switch to Azure DevOps to have all services unified in one place, simplifying management. The main advantage is having everything centralized.

The initial setup process for Azure DevOps was somewhat complex, requiring documentation and technical support. Migration from previous tools and configuring project guidelines were involved. The deployment strategy involved creating directories, and repositories, setting up environments, and assigning access rights, following a predefined plan. Initially, deployment took about three to four hours, but now, for regular deployments, it typically takes 30 minutes to an hour, depending on project stability. 

For the initial deployment of Azure DevOps, gathering information from various resources is essential, but typically, only one person is needed to handle deployment through the web interface. Maintenance involves regular tasks like backups and occasional updates, requiring minimal effort.

The pricing for Azure DevOps may be higher compared to other tools, but overall, I find it reasonable.

In my experience, integrating reporting and analytics into Azure DevOps enhances project visibility and decision-making processes. We can easily generate reports online to track project status and task progress. Additionally, I have integrated Azure DevOps with other tools like SQL Server, enabling us to gather data for generating Power BI reports.

The most beneficial integrations with Azure DevOps are integration with other project management tools for seamless collaboration and APIs for importing data into applications. Additionally, integrating with personal models allows for enhanced analytics and reporting on resource performance and other project metrics.

The source control management features of Azure DevOps, particularly Azure Repos, are highly effective. We can easily track and manage code changes, commit updates, and maintain a complete history of changes for our applications.

I would recommend Azure DevOps to others. Before choosing Azure DevOps, I would advise considering the need for better project management, consolidation of management tools, and streamlining deployment processes.

Overall, I would rate Azure DevOps as an eight out of ten.

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.

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.

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.

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.

We have been working with it for the last five years.

The system is exceptionally robust and reliable,  and we rarely encounter any performance issues. I would rate it eight out of ten.

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.

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.

The initial setup was quite intuitive. I would rate it eight out of ten.

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.

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.

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.

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.

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.

I work in a consulting firm responsible for adding, managing, and deploying government projects. We are using Microsoft Azure DevOps in one of the projects for backlog management, test planning, test execution, sprint planning, bug fixes, and enhancement requests. We use the solution for anything related to development testing.

The solution's most valuable features are backlog management, build release pipeline, and testing. They're easy, intuitive, and increase productivity. Usually, if you don't use such a solution, you end up using Excel. Then, you won't have shared documents, and there'll be no single source of growth. Everybody will keep a different document somewhere, and you will spend a lot of effort reconciling the latest status.

Using Microsoft Azure DevOps makes it really easy for us. Anytime you can see how many bugs are open, you can directly get it out of the tool. The solution's reporting is really easy. You can create ad hoc reports based on management requirements. If you are sitting in a meeting and somebody asks you the number of chain requests, bugs, or enhancements, you can create quick queries and show them the status. I think this directly affects productivity.

Microsoft Azure DevOps doesn't have an ITSM tool compared to its competitors. We also use Jira for another project, and Jira supports ITSM or ticketing. Since Microsoft Azure DevOps doesn't have this feature, we have to depend on another solution for service request management for support tickets.

The solution should include ITSM tools and security. DevSecOps are third-party security plug-ins that you can integrate with DevOps. Azure DevOps itself doesn't have anything out of the box. Enabling security so that the solution automatically starts checking things would be a really handy feature.

I have been using Microsoft Azure DevOps for three years.

We haven’t faced any issues with the solution’s stability.

I rate the solution a nine or ten out of ten for stability.

Since it's a SaaS solution, we haven't faced any scalability or performance issues, and we haven't struggled when we had a lot of users. We have gone through a curve. We started with around ten users. At the peak of the project, we had almost 50 users. Since we are in maintenance, we have come down to 10 to 15 users.

We use 100% of Microsoft Azure DevOps for our project. Everything is within Azure DevOps. If anybody says that we need to work on a feature, the first thing we do is create a DevOps item. So, we don't do anything outside DevOps.

The tool provides the features, but we haven't been able to onboard end users. We are a consultancy firm that works with system integrators and also engages with the end client. We have been able to onboard the system integrators, and we are also using it.

However, the end users still prefer sending emails and documents. If you send them a link to run a test script, they won't do it. So, the end users still prefer the old ways, such as emails and documents.

I rate the solution's scalability a nine or ten out of ten.

So far, we haven't faced any issues in terms of technical support. There is good documentation available if you are looking for support for configuration. So, you usually end up resolving your issues yourself. Since this tool is widely used, you can find help online. People are writing content about this solution, and Microsoft itself has good documentation.

On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup a nine out of ten. The solution's initial setup is pretty easy, and the rollout is pretty quick. You can enable it and then keep on modifying and updating it.

It took us less than a week to deploy Azure DevOps. Since we were using a cloud environment, there was no infrastructure requirement. We went on Azure DevOps, created an organization, and then created a project. Inside the project, we selected the type of project.

There are different templates that you can follow, including the CMM-level approach or the basic approach. We selected one of the templates and copied the template. We made some modifications to the template for the project because that template is used for governing steps.

Then, we created depositories, which is pretty quick. In a week's time, we were up and running with backlog management. It took a couple of weeks to complete the automated build and deployment pipelines.

We needed one person to set up the project and one knowledgeable about the build and deployment pipelines. If you have a person who knows how to do the pipelines, you can also configure the project. So, one person is good enough to set up the entire project.

We have seen a return on investment with Microsoft Azure DevOps in terms of productivity because it really helps with the amount of time you need to consolidate reporting and planning. The status is always up to date, and the deployment is very streamlined. You can do the entire thing in Excel, but the overhead would be too much, and you would lose out on things. So, team synchronization and productivity are the return on investment with the solution.

I rate the solution’s return on investment a nine out of ten.

The solution's pricing is pretty cheap. The best part of the Azure DevOps and SaaS model is that there's no upfront cost. The tool has a per-user license. It's free for five users, and there is a price above five users. The solution's deployment and licensing costs are very cheap compared to those of its competitors.

The solution's pricing is not fixed. The solution's testing license is $50 per user. It's $15 for normal users who use backlog management. We have two people from the test team and seven from the other team. This is in maintenance.

Since we had a big testing team, we had 15 people in testing and 30 people in backlog management during peak time. You can say it has a 70:30 ratio. Most of the cost is in testing, and the backlog management is really cheap.

On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a three out of ten.

Before choosing Microsoft Azure DevOps, we evaluated other options like Jira and HP ALM. Jira is good at ITSM and backlog management, but it is dependent on third-party tools for pipeline deployment.

It's too complex to do product management with HP ALM. It's a good ITSM tool, but the process it follows for product management is very stringent, which is not very flexible for sprint planning. There is too much overhead in HP ALM to do quick sprints.

We are working with the SaaS (Software as a Service) version of the solution, which is on the cloud. Since Microsoft provides the latest upgrades and patches, it should be the latest version.

We start by creating backlog items. Whenever we get a requirement, we log it into Azure DevOps and plan the backlog. The backlog includes what features we need to develop and what tasks we need to assign to each developer. Each developer is part of the DevOps. Once you have created that backlog, we assign it to different developers based on a sprint.

Suppose we are going to run a four-week development cycle. So, we plan the development cycle, pick a few items from the backlog, assign them to that sprint, assign them to the developer, and then manage the execution of that development cycle. Once that's completed, we will transfer it to the test team so they can test it in Azure DevOps.

They have test scripts that are documented in Azure DevOps. They run tests, record videos, and capture screenshots in Azure DevOps. After the test verification, we deploy the solution. In addition to backlog management and product management, we use Azure DevOps for build and release deployment. We don't manually go and build the software.

Our code repository is also part of DevOps. As soon as we check in the new code, Azure DevOps automatically builds the solution and then deploys it in the development environment. Once it's confirmed, the same is deployed to quality and production. We use the solution to do everything end to end, other than ITSM.

Specifically, Azure DevOps is integrated with deployment for us. When we manually deploy a solution, it's prone to errors. We use Azure for website deployment and Azure DevOps for Apple app or Google app deployment.

As soon as the approval is done in Azure DevOps, apps are automatically published. It will publish an app on the Google Play Store, Apple Play Store, and Azure, which we use for web hosting. So, it is integrated with web hosting, Apple Store, and Google Play Store.

The solution does not really need any maintenance. Once you enable the testing solution, you can start creating your test plans and test scripts directly. Every time you do a deployment, you just need to run those test scripts, which is pretty easy. It's more about creating your test script than configuring the tool. Even if I do it in Excel, I need to spend time on that.

The solution's analytics and reporting are pretty easy. We use them very often on an ad hoc basis whenever we discuss and plan what to deploy and what the next steps are. It's pretty easy, and we haven't faced an issue where we weren't able to take out any reports just by doing it on an ad hoc basis. It's pretty easy, and you don't need to write code or anything.

The tool is pretty flexible and easy to use. I suggest starting with the cloud version because you can create your project easily. Since it's free for five users, organizations with budget constraints can start playing with limited users. I would say start with the cloud-based version and start playing with it. Once you get comfortable with it, you can expand it for other projects. The tool serves a wide variety of use cases.

The biggest key trend these days is fast deployments or quick releases. Given how competitive the market has become, you need to keep on adding features to your product. Azure DevOps supports the sprint methodology, which supports fast deployment.

On top of that, it supports automated build release deployment. That was a headache when I started working. Sometimes, you forget a file when deploying in production, and your system will go down. The solution's features support the latest fast or quick deployment trend.

Overall, I rate the solution a seven out of ten.