We worked with the vendor.

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.

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 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.

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

For deployment, assistance from Microsoft or a system integrator is essential. Customizing templates and processes requires their full support to tailor them to our specific requirements. Since it's a cloud-based solution, the need for managers is minimized as management becomes simpler. A team of two to three individuals is sufficient for configuring it effortlessly.

We implemented through an in-house team. 

The implementation was done in-house.

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

It was implemented in-house as we have a high level of in-house expertise in the ALM space.

Maintenance is essential due to occasional exclusivity with business connectivity, leading to various issues such as data rate problems and database availability issues.

It is a third party that sets it up. I don't know about its maintenance because I'm not that close to it.

The installation was undertaken by a consultant. 

There was a team of, perhaps, five engineers involved. 

We implemented on-premise as a hybrid solution, and on the cloud.

Smaller tasks like deploying a prepared code for a single service wouldn't require additional engineers. Many workflows can be handled by one person. 

Architecture is different, as the architect designs the infrastructure, which needs to be followed.

It was implemented internally.

We did the implementation ourselves.

I'm working on the high-level design and the low-level design so I know where we're going to start, and whether we've got a blank slate. I've worked with many firms in the past and companies have their own design in place. Usually, some of these companies material is outdated and Microsoft will probably move the bar several times. We are Microsoft accredited so we stay in touch with the technology more recently than most. We've constantly been informed of the latest technology and the latest products that are evolving on the platform. That includes those that are in preview, which I hope will become available, as well as those that are going to be deprecated. We're basically in full harmony with Microsoft and their products.

Our internal DevOps team handled the implementation.

We managed everything on our own. It involved fitting other products with the existing product. If you don't encounter problems, you're not going to learn.

Our deployment took about three months, as we tracked it. Following that period, we needed another month to integrate a new component into the setup. We implemented it ourselves, with one of our team. We have about 10 users using Azure DevOps, but we have 2 people to provide the deployment out of those. These are developers. We have a small team for DevOps, including the manager. We need our staff to be flexible and agile in our team to take on various DevOps tasks.

We had a combination of both in-house and vendor help with the setup process. We've got enterprise agreements with Microsoft, so they always give us resources to assist with our deployments. We already had TFS deployed, so it was an upgrade, really.

We require a three-person team for the maintenance and support of the solution.

We did the implementation ourselves. I do most of the maintenance but it is mostly maintenance-free.

Our IT department installs this solution.

I did not use a vendor or an integrator, I did it on my own. It's a Microsoft product and we all use Microsoft.

I handled the implementation on my own.

The implementation and maintenance of the solution are done by our DevOps department.

We had some hands-on help from Microsoft engineers with deployment, so for us, it was straightforward. 

We have an in-house team for deployment.

I handled the installation myself. I did not need the assistance of a consultant or integrator. It was handled in-house.

I deployed this solution without any help.

I implemented Microsoft Azure DevOps by myself.

We had an expert that did the implementation of the solution for us. He did not face any problems.

I performed the setup myself, on my laptop.