What is your primary use case for Microsoft Azure DevOps?

We are mostly using Microsoft Azure DevOps for the development dashboard and for CI/CD pipelines. We also use it mainly for Git repository management.

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.

Azure DevOps helps us automate building, testing, and deploying our code through CI/CD pipelines.

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.

We use Microsoft Azure DevOps as a code repository, for task and work management, software tests, and documentation.

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

With Azure DevOps, I plan and track my project using Azure Boards, manage my code with Azure Repos, and automate build, test, and deployment processes using Azure Pipelines. This streamlines my development workflow and ensures efficient collaboration and project management.

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.

We use the solution mostly for automation, deployment, generating build, and creating virtual machines.

We use it for automating our code builds, significantly enhancing collaboration, and accelerating our release cycles. By reducing release times, we're able to ship our product faster, thereby increasing productivity and efficiency.

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.

My clients use Azure DevOps primarily for managing code deployment pipelines. We follow a structured process of pushing code from the development environment to testing and then to production, and Azure DevOps is crucial in this workflow. We leverage its version control capabilities to maintain and track our codebase efficiently. Additionally, we make use of its dashboard service to monitor and manage employee hours, helping us keep a close eye on project timelines and resource allocation.

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.

The main use of this solution are to combine software development and IT operations. Also, we use it for automation with version control and microservices. Automation is a core principle for achieving DevOps success and CI/CD is a critical component. The application of continuous delivery and DevOps to data analytics has been termed DataOps. DevOps focuses on the deployment of developed software, whether it is developed via Agile or other methodologies. ArchOps presents an extension for DevOps practice, starting from artifacts, instead of source code, for operational deployment.

We produce multiple different software for different markets in different countries. It's really for everything you can possibly think of, from online games to financial systems, to payment gateways, to APIs, to service desks, back-office analysis tools, admin tools, et cetera. We use it for anything and everything really.

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.

We use Microsoft Azure DevOps for CICD, and to organize it in order to visualize the ongoing work.

I use it to, for example, build applications. Not just Subnet - also Java or in OGS. I deploy Windows applications and also mobile applications with Visual Studio App Center and Azure DevOps.

There are two versions of Azure DevOps: the cloud version and the on-premises version. We use the cloud version in very few situations, but most of our software is based on Azure DevOps on-premises. We are a software house, and we develop software. We use it to store our source code; that is, it is the repository for our source code. We have different teams working on different products, and each one uses a different methodology and a different process. Azure DevOps helps with that. For instance, one group may be using Scrum as a methodology to develop their software. The other group could also be using Scrum but with CDCI (continuous development, continuous integration), which helps a lot when you have to develop, test, and deploy the solution.

Microsoft Azure DevOps is used for source code versioning, issue tracking, documentation storage, and sharing.

We use it for requirements, development work, and testing. We're doing an implementation at the moment with the client. So, it is the latest version that would've been uploaded.

We manage the full scope of all our projects on Azure DevOps, including all of our kits, bags, and user storage. DevOps encompasses the CI/CD process of every build as well as the customer requirements, QA, and deployment.

We use Microsoft Azure DevOps for applications that analyze data and the data scientist creates the test data for the manual and automatic application tests. Here in Europe, we need anonymous synchronization of all data for testing. We create special applications for creating data for direct tests.

Our only use case with DevOps was for integration with ReadyAPI.

We provide this solution to our clients. The company we're currently assisting has had a lot of issues using Jenkins and decided to move the CI/CD pipelines to Azure DevOps. I'm a solution architect and we are partners with Microsoft.

We use Azure DevOps for the entire lifecycle of software development, starting with requirements analysis. After that, we use it to continue the process of development and deployment.

We use it for planning, pipeline management and testing, as well as using it as a CI/CD tool.

We have a number of use cases. One of them is development, which includes several development teams that use source code control and testing support, as well as the entire software development toolset. I only use the front end, which is the project task management part.

The purpose is for development and testing from the vendor side. Our company works as a vendor, client, and implementation partner. The vendor provides the product, and we make sure that it's implemented correctly for the client. The vendor uses it for the development and tracking of the requirement and the test cases, executions, and building storage. My access to these tools is very limited because the DevOps pipeline and DevOps is mainly used by the engineering team of development, but the QA is also part of it. Once those people are established, then we are the extended hands or extended part of that for usage. Once they have the stories and features, they start the test cases and link on it. From that point, we just take it forward and once they have a code pull, then we would pull it and build it and deploy it into some QA enrollment. There are around 20 people using DevOps in my company.

I primarily use the solution on projects often. We use it for our Git repository and the CI/CD.

We use Microsoft Azure DevOps for our source control, change request management, and a small amount of Wiki.

We primarily use the solution for our internal development and we have some clients that require some consulting around some DevOps functionality. We use the product for the development process for the repository, for the tracking of the tasks in the boards, and for the pipeline for CINCD.

We're using Azure DevOps Services for three things: First, for project management, second, for storing the source code, similar to GitHub Repository, and finally, we use it as our CICD build server or build environment, which builds for us and runs tests and so on. In general, these are the three main use cases for this product. We are large customers of Microsoft and we're on a corporate level with them. We pay extra for support. I'm a software engineer manager.

I primarily use the solution for more of an end-to-end pipeline.

It is used to manage our projects. We basically maintain what would be the equivalent of our project schedules for various projects. So, we capture or create user stories to identify elements that need to be accomplished for the delivery of a project and to track who is responsible for it and the level of effort. We aggregate that within the tool and report out to leadership about the status of when we anticipate completion. We are using its latest version.

Currently, we are using it for the continuous integration and continuous deployment of the CI/CD pipeline available for our projects.

We are using the tools in this solution mostly for planning our software projects by implementing Scrum. We use repositories, and create timelines for continuous deployments and integrations.

The solution can be used for immutable infrastructure or for microservices.

We use Microsoft Azure DevOps to maintain our project. We create a project in a good DevOps, and then we add the backlog items. The product owner adds the backlog items, and then the development team. The repository is also built into that. We have a private Git report for the project. Under reports, we can create a repository for the big projects and maintain the source code. Developers can commit and make a full request. For example, configure Jenkins, reconfigure Jenkins with the repository credentials, and then use it for linking. We don't use the pipeline available to us, and we use Jenkins for CSC.

The company that we were working with was in development using a Microsoft platform. We used Azure to integrate the complete project management and DevOps work.

We are an agile shop. We use it to build our sprints and for our user stories. We have everything aligned in epics and we track all of our requirements and our velocity.

I am using it as a developer in the agile scrum area.

We use this solution for cloud administration, cloud infrastructure, the database, as an application server, development, and more.

Broadly speaking, we use the product for .net websites, APIs, data integration, migration, data analysis, job orders, and workflows.

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.

We use Azure DevOps as a way to organize our development. As a means of facilitating application deployment from pre-production to production. We use it to organize our environment and identification systems. If you don't have the power or permission to do something, you can't do it. With Azure DevOps, we can create profiles that developers can use right away to go from pre-production to production.

We are exploring this solution. There is not enough protection in the environment at the moment. It's been almost six months since we started the process of exploring the DevOps environment in Microsoft Azure DevOps. We have a customized development methodology so that it is easily marked to our existing environment. Currently, we required that all these systems blend easily in this one environment. We can actually use all the large frameworks within DevOps properly and automate most of our support, starting from planning through support to deployment.

I used Azure DevOps for work item management, sprint planning, source code repository, continuous integration, continuous build, and continuous release. I build whole chains.

It is used for development and life cycle management within the company. We use the SaaS version. It is called Azure DevOps services.

We use the solution to store all our source codes. It's a solution that stores everything. We are an in-house development and we produce a lot of codes. We also use it to control our development process. We follow some methodologies. Every every team has a different methodology, for instance, Chrome, Agile, et cetera. The whole process from the planning process until we deploy the solution, everything is controlled by DevOps.

We use it to manage the project. We create the product backlog, and we put our tasks into the DevOps schedule.

My team uses this solution for the CI/CD deployment, and code check-ins. We are also using Azure Boards for tracking our work, all of the requirements, the backlogs the sprints, and the release planning.

We use Microsoft Azure DevOps to store our code, manage our code, and publish it.

We are a reseller of solutions and provide maintenance to our customers. Azure DevOps is one of the products that we have experience with. Our customers use this product when they want to enter the DevOps space and integrate or consolidate all of their existing tools. It allows them to communicate seamlessly between development, their operations, and other team members.

We are a small product team and we do software development. I'm part of the testing team and I use Azure DevOps to manage all of my test activities. This includes my test plan, where I create my test cases, write test scripts, execute them, and publish the results using the dashboards.

The first time I used the solution was to create a build for an Oracle application called SOA. We generated all the features in Azure DevOps to create the build and then we created a workflow. We are partners of Microsoft and I'm head of technology.

We are using this solution for CI/CD projects, for Scrum, Agile planning, testing, and business management system solutions. We are also using it for continuous integration, and continuous delivery of DevOps. I am also using the Git Repositories, which is the main source control for me in the organization. We were using it on-premises and now planning to move it to the Cloud. They are calling it repository and they are supporting an old protocol, which is a popular protocol called Git repository.

We primarily use the solution for our Agile teams, however, we started off using it with our executive suite. Our executive team now meets in sprints every day. Sometimes it's a short 15 minutes, other times it can be up to an hour. We have two-week sprints and daily scrums associated with it. We've also rolled that down from the executive. We've got seven formal Agile teams running throughout the organization across our businesses. We probably have at least 40% of our staff now trained in Agile and using DevOps to execute the projects.

We use Azure DevOps to place our corporate servers into the cloud. We perform evaluations in the cloud for clients. Occasionally, we provide a hybrid solution in a specific cloud. For corporate work, we usually use a different cloud. With Microsoft Azure DevOps, as with any DevOps, it is not always possible to identify specific use cases. How do you identify a specific feature from a hundred requirements into a specific use case? It is very easy to lose detail. Traditional teams and ways of working methodically for safety-critical systems are not always prepared to handle that. It is important to be able to handle hundreds of detail-oriented requirements.

We are using this solution for workflow management, especially when using a Kanban board to monitor the small assignments. Also, some programming for some of the disciplines. It's still in its infant stages.

We are using Microsoft Azure DevOps for tracking the requirements and tracking the issues. Any issues that we have, are tracked and logged. Also, we check the developer's workload. It can be used for different purposes as well. For example, it can be used by software companies and different software teams for collaboration.

We primarily use Azure DevOps for the early phase of software development projects. We don't use it for building the software. Rather, it is for development support. It handles management of the features, the composition, the definition of requirements, and checking our requirements against the use cases.

I am a consultant and this is one of the tools that I use to help develop solutions for my clients.

We are a software development company and we use DevOps practices to manage our application development lifecycle. This is our primary use case. We don't have a production environment for the applications that we develop. Rather, they are given to our customers when they are production-ready. The management includes service requests, incidents, issues, etc.

We normally use DevOps. On the application, everything has gone DevOps, however, we don't use the functions. All applications developed there have gone under Azure or AWS. We normally develop them to be able to not be dependent on anything, so if we want to deploy them in another environment, we can deploy them easily. If we want to use it in Azure, we use it in Azure. If we want AWS, we use it in AWS.

I took a part-time job doing a mentorship to guide the students on how to use cloud computing on the AW and Azure cloud resources. For that project, we go through each and every service on cloud computing that is part of the service platform. The new technology is called server-less technology. The goal of the mentorships is showing students how to fundamentally use these resources and explain the advantages and disadvantages of cloud computing over on-premises solutions.

We use Azure DevOps for managing our workflow, as well as the CI/CD.

We are a manufacturing company and I am a technical consultant who is responsible for managing the software applications that are outsourced for development. In this role, I have gained experience using Microsoft Azure DevOps. I have also used it as a software developer in companies that I previously worked for.

We are currently involved in a financing exchange project, and we use this solution to keep track of the exchange activities within the backlog. We are not taking advantage of the repository and the code stuff at this stage.

Building fast and reliable, amplified feedback loops in all stages of our software delivery and operations lifecycle. The business strives for built-in quality to ensure that everyone have correctly done their job. I trust my team with peer reviews of our designs, code, test and infrastructure.

Full DevOps suite.

* Source code management * Git repository management including a visualizing for the pull requests process * Build automation * Continuous integration * Project management * Test management * Release automation * Deployments automation * Artifacts management * Package management * Agile planning * Dashboards and reports * Requirement management * Work estimation * Capacity management * Backlogs and Kanban boards for different teams * Load test * Integration test automation and unit test projects with status reports on the test results.

Agile scrum project management of a software product in a start-up company. We are a team of 11 people located in different countries.