Microsoft Azure DevOps Reviews

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.

It's part of my new role as a DevOps engineer and the cloud engineer. We're migrating our on-premises applications to the cloud-based M365 platform, built on Microsoft Azure. That's the primary use case.

Azure DevOps supported our agile project's sprint planning and management. It introduced automation, which is still a little bit immature. But our previously manual tasks are now automated, and we've transitioned from deploying ITFAX applications to containerized deployments using images. These are just a few examples.

Moreover, Azure DevOps facilitated our team collaboration and tracking of work items in our projects. We've got the backlog, the boards, the item backlog items, you know, you can see what's approved by the product owner, what's on hold, what's in progress, what's developed and deployed to whichever environment, nine product or product and stuff like that. 

So, it's been visible for all to see, from my manager to product owners, technical product owners, developers, and testers; every stakeholder has visibility.

Ever since we adopted Azure pipelines, we saw faster releases. Something that would take us two or three weeks to deploy; we can do it in a couple of hours now. So, the primary benefit is definitely faster development and deployment cycles.

It boils down to - increased customer satisfaction. Quicker releases to testing and production environments - that's the benefit, that's the impact.

After each commit, the code automatically goes to Azure DevOps. We can then manually trigger the pipeline if needed. Once the pipeline successfully passes all tests, it deploys the new container image to production, replacing the previous one.

While I'm just gonna stick to Docker, it has really helped developers to confidently commit whenever they feel the analytics are okay to work. On their machines, it records any environment, unlike the old way where we had to click on our machines and then involve the operational team, which sometimes didn't work. With containerization, we already know all the application dependencies needed on the image. It's just one, OS or environment independent.

Moreover, we've experienced the general benefits of Azure Test Plans. One major improvement is the automation of tests. Once automated tests pass, the code progresses to the next stage, minimizing human error inherent in manual testing. This automation extends to reporting as well, providing clear and readily available results. In terms of reducing human error and streamlining reporting, I'd rate Azure Test Plans a ten out of ten. 

Additionally, detailed logs allow us to pinpoint the exact cause of any issues, making troubleshooting efficient and accurate. So, for both error reduction and insightful reporting, I highly recommend Microsoft Azure DevOps.

There is only one key area of improvement for me. The new imaging thing is that there is DevOps, where security is important because it is always lasting. So, to integrate security in our DevOps, that would be nice.

I have been using it for more than a year.

It is a stable solution. However, there is always room for improvement. I would rate the stability a nine out of ten.

It is a scalable solution. There are over a hundred end users in my company. Every IT hub uses it. 

The customer service and support were quick to support. Usually, we don't need the support. We google our query and easily find the solution on official Microsoft page. So, we hardly need any support. 

In my previous jobs, yes, we did use different tools. We had a separate team for DevOps team. There was even a "deployment specialist" who dictated deployment times and windows, which could be quite restrictive. So, switching to Azure DevOps has been a massive improvement.

The initial setup is easy. Once the code is committed and the developers sign off, we just go to Azure DevOps, click on "Pipelines," and run the pipeline. That's all, pretty straightforward.

The deployment can be done in-house. However, I was not involved in the deployment process. I'm utilizing it, and so far, it's easy for me.

The pipeline itself can be managed by one person. But when it comes to the entire Software Development Lifecycle (SDLC), from data requirements gathered by the business analyst, system analysts, solution architects, and so on. That part is still manual, it's not automated, and you can't just throw technology at it and expect a one-person team to handle it. 

However, for running the pipeline end-to-end, from CI to CD, Azure DevOps allows a single person to manage it. However, developing the application from concept to reality still involves a lot of stakeholders across Azure.

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

Being a project manager, it is necessary to create sprint, and kanban boards for management decision-making and our product life cycle. We use the solution for sprint backlog creation and bug reporting for IT department fixation. The dashboard is an interesting feature with visibility on the pending due dates. 

Since using this software, we have revoked the usage of MS Office tools and prefer to instead use Azure.

Azure is one of the few project management software solutions that provide a clear view of project standing, and sprint of product backlog as well. 

As far as my organization is concerned, we use this software for managing the project life cycle where we raise change request forms here and the IT developer provides the solution and from there we can conduct the UAT and sign off for closure. 

The entire product life cycle is being managed with task assignments so broader and a clear understanding of scope is provided by this software and the organization can better understand its current progress.

The available Kanban board is the best feature for management decisions. The sprint capabilities of the product break down the feature and characteristics of the product into steps and if any step is pending we may forward it to the backlog. 

Microsoft Azure is an Agile methodology, so multiple steps can be performed by different user segments in order to achieve the scope smoothly. 

More features can be included. We'd like to see better Kanban templates and an audio-video chat facility. 

The bug reporting facility can be enriched; there is nothing to mark "passed" "failed" the test cases. 

The dashboard can be enriched. 

Related links must be visible on the dashboard for integration purposes. 

I've used the solution for the last two years.

The stability is good.

The scalability is good.

Customer service and support are good. 

Positive

We did not use a different solution previously.

The initial setup is a little bit complex.

We worked with the vendor.

We have witnessed a good return on investment. 

This is good software for a reasonable price.

We did not evaluate other options. 

I work for a telecommunication company that offered television via IPTV. 

IPTV is an internet protocol television, such as AT&T U-verse or Fios from Verizon.

All of the IPTV systems are proprietary, meaning that's not open to the customer, only to the infrastructure. Before Microsoft Azure DevOps, customers only use what are called set-top boxes. When you are deploying Microsoft Azure DevOps, you don't need the set-top box anymore. You only need a client that can go in, but you have to deploy it. You have to understand what the customer has and what they needed to have in place for on-premise, hybrid, or in production.

Microsoft Azure DevOps does not use the set-top boxes. You have something else that is called OTT or over the top. What that means is the deployment that you're going to do depends on the client the customer is going to use. The deployment has to be tested, and that's why we have the different deployments available, on-premise, cloud, and hybrid.

The most valuable features of Microsoft Azure DevOps are high-level protection. The protection is very important to the customers to prevent eavesdropping. eavesdropping is when a hacker tries to get into the solution. With this solution is it difficult for them to do it.

In the hybrid deployment, you can test everything. The customer was perfectly happy that developed the code, and when they put it in the hybrid Microsoft Azure DevOps and tested it as if it were in real production. That's the part that I've really enjoyed the most, is seeing how a product that was developed by the customer was tested perfectly. If something is wrong, we come back to Microsoft Azure DevOps for whatever they need to do. If they need to go deeper, they can use TFS which is part of DevOps and show it to the program manager or developer.

Microsoft Azure DevOps needs to be updated in my time. In the application that I was managing myself in the deployment and support, it was updated every six weeks. The customer had new features or new batches. Batching is an update of the software. Unfortunately, some of the DevOps or some of the people that were working on that part, do not have the final experience from what customers have. This is something that I did with several teams in Microsoft. We told the product unit manager if you want to understand what is happening from a customer standpoint you need to start from the beginning. Having customers find a problem can not be the only way to find issues to resolve them. 

Testing is very important. Microsoft Azure DevOps tests very well. However,  DevOps teams need to be aware of what they are impacting when someone updates anything on the system.

I have been using Microsoft Azure DevOps for approximately 

It's important to know what kind of DevOps you are going to have. If they're going to work with Microsoft Azure DevOps, they need to understand the solution very well. They cannot just start doing things because they wanted to try and do them.

Microsoft Azure DevOps is scalable if you have everything in place, such as the service map and processes. Before you do anything, you have to understand what the impact will be on the customer.

We had over 10 million people using this solution worldwide. I have worked in many countries, such as the Americas, Canada, and Chile. Many of our product groups were in China, India, France, and Israel.

I have used Amazon AWS previously.

When I compare when Microsoft Azure with Amazon AWS. The two of them offer the same features. You have the storage, performance, connectivity, et cetera. However, on the hybrid, Microsoft Azure DevOps is a lot better than Amazon AWS because you can emulate it perfectly. The hop counts matter, which is how many times one communication connects on its travels from one device to another.

There are three ways to deploy Microsoft Azure DevOps. To set up all three deployments is very similar but different. The on-premise deployment is where the customer owns the code. What Microsoft Azure DevOps does lets you develop your code, and when you have finished your code, you have to put it in the cloud for the hybrid. Then you can test it in an environment that is similar to production. I was in charge of making sure that everything was set up correctly.

I was involved from the beginning of the implementation. I'm a project manager myself too. I don't have certification, but I've been doing project management all my life. One important element when doing the implementation is the voice of the customer. No matter what you're configuring or setting up, if the voice of the customer is not there, but the voice of the business and the employees is, that is only two-thirds of what you have to do.

For example, I want my customers to run this application even if they are in the jungle. If they have access to WiFi, cellular signal, or hotspots, they can have access to anything that Microsoft Azure DevOps can give to them. Except they need a client, and that's the other part. You need to understand what clients the customers are going to need. The clients depend on three things. You need to know the infrastructure of the customers, their immediate needs, and the needs of their customers. We're developing something for the customer who has customers. Unfortunately is not only DevOps, it's everything. DevOps is only one part.

DevOps has one issue. There are components that are produced and supported by other teams somewhere else. Service maps are very important to develop with DevOps teams. When we develop the service map, they know what to do. However, some DevOps do not like to have service maps, because they say that they know what to do. That's what the problem is, they need to understand that they're not alone.

I have worked with integrators, vendors, resellers, consultants, and in-house teams.  

You have to be a very good project, delivery, and program manager, in order to understand how to work with vendors.

For example, you need to know how to work with people who, are going to cable a house, building, or something similar. You need to understand specifically what are the requirements that they have as a company. Additionally, you need to understand the company to know the requirements of the customers. If you are not familiar with any one of those, the deployment is going to be a total fiasco. You have to know what is going on. 

You have to know the vendor. The vendor can tell you a lot. For example, when the materials are available, if there is a problem with the supply chain, what do in this circumstance. The vendor knows about the RMS or the return of the devices. You have to know everything from the deployment, such as RMS to return back, refunds, purchase orders, and goods received.

The return on investment from Microsoft Azure DevOps depends on how many customers you have and how fast are you going to be able to have something ready for your customers.

I have a customer who wanted to start quickly on the cloud. They have about three million customers working in one area, and only when 100,000 started did they receive a return on investment. It was not immediate but in approximately a year or a year and a half, they had a return on investment with every single customer.

The reason that customers are going to the cloud is that it provides the ability to reduce the license cost. For example, when purchasing Office 365 it is bundled with Word, Excel, PowerPoint, Access, and many other applications. In the past, purchasing a license was approximately $600. Today it's only $35 or $45 per customer, per client, or per user, plus the storage. It's less expensive for companies today, to use something, such as Microsoft Azure DevOps, and provide the software to all the employees needing a license. It's better to go with the cloud than just to buy the licenses by themselves.

There are some additional costs. You pay for how much space you are using. If you don't use too much space, then the price will be very little. If you use a lot of space, you have to pay for it. Additionally, they offer readiness training. It is not included directly in what is called a statement of work when you are doing business with customers. This is when things can be a little more difficult because it can be expensive for customers if they want to change deployments from on-premises to cloud or hybrid.

The voice of the customer is very important. Develop the software based on the voice of the customer.

I rate Microsoft Azure DevOps 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.

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.

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.

We are using it for the source-code repository, automated bill process, very limited automated testing, and tracking trouble tickets or feature requests. We are using its latest version.

The automated bill feature is most valuable. As with most software developers, I can build code on my machine, but if one of my coworkers can't build the same code on theirs, there are always issues in trying to track it down. The automated bill process makes it a lot easier to track down where the issues are and find out what bugs aren't being included for whatever reason.

They should expand it from just a PC, software, or server development platform to other kinds of software or engineering systems so that it is not necessarily built around a normal PC with a server.

I would like to see the ability to write my own scripts in my own compiled program or online. Right now, there are things that you can do in the user interface, but you can't do them programmatically and vice versa. I want to see them both. If I can do it in a script, I should be able to do it from the user interface, and if I can do it in the user interface, I should be able to do it in a script.

I have been using this solution for a total of four years.

From what we've used it for so far, I have not seen any problems.

We're using perhaps 10% of what it is capable of doing. It is far more capable than what we are using right now. With further experimentation and training, I'll probably go from 10% utilization of its capabilities to about 50% or 60% in the next couple of months. We'll never use 100% of what it is capable of doing, but it should handle 95% of everything we need to do. We can always write our own plugins to handle the side things that we need.

Scalability is not really applicable with the code that we write, but the build times and things like that typically take under 15 seconds before we get our responses back. So, it works extremely well.

In terms of the number of users, there are six of us who are software developers. Some of the managers might also partially use the reporting capabilities.

I haven't called them up.

I've used JIRA and a number of different systems going back almost 20 years. We were doing our development using Microsoft tools, and it just made sense to use what they integrate with. Azure DevOps is the perfect environment because we're using Microsoft technology for other stuff. It is always going to have slight favoritism towards the other Microsoft tools.

The basic setup works very quickly, but there are so many things and options.

We did it ourselves, which is one of the problems. We don't know what we're doing.

I don't know what we pay, but I do know what I've seen online. If we switched to JIRA, we will basically have to double our costs because we still have to pay for the DevOps licensing. We're probably spending $100 a month on it. It has only standard licensing fees.

It is a really complicated product. All DevOps stuff is complicated. The advice that I would give to anybody doing DevOps is to have a goal in mind of what you want to do. Then the product will do what you wanted it to do. 

I would rate Microsoft Azure DevOps a four out of ten because I don't know it enough to rate it.