Azure DevOps Services

Formerly VSTS

Less bugs.

Quicker resolution of issues.

Ability to meet strict security requirements for protecting company software projects.

Ability for a team of developers to work on the same project at one time and increase the speed of completion.

Increase in developer productivity. Prior to using the product, we were using a manual backup and copy process, which would take an additional 60-90 minutes a day for each developer causing a loss of productivity.

We have saved a ton of time not calculating metrics by hand.

We no longer spend time writing out cards during planning, it goes straight to the board.

We no longer track separate documents to track overall department goals. We were able to create customized icons at the department level that lets us track each team's progress against our dept goals.

Our many customer and government audits are streamlined due to the many roles and lifecycle phases integrated into one place with full history and traceability. Smooth audits translate to customer retention and repeat business.

Our release cadence of thousands of customized applications occurs rapidly due to Build and Release Pipelines. This equates to customer retention, repeat business and an increased rate of new customer acquisition.

All roles, development, test, project and design management, business analysts, DevOps, QA, and others all work more efficiently, in concert with each other and meet frequent release schedules consistently.

N/A

Azure DevOps has allowed us to be much more agile with our deployments allowing us to save lots of money by not having to involve numerous teams to do deployments.

This has been a positive ROI as it allows our developers to manage the full life cycle.

We can now do break fix immediately and not when other users can get to it.

We have now a better project management platform.

The communication between team members and project owner has been significantly improved.

Azure DevOps provides a code repository where you can store your code without worries.

We can easily manage a large set of containers and developers with little manual intervention.

We know what artifacts are deployed easily through the dashboard.

Easy orchestration to move code up landscapes.

We've reduced task switching to a minimum, allowing our teams to keep focus on their jobs

We're having great results from Azure DevOps Testing capabilities, allowing us to ship better products faster

Fast Data Entry: Our teams have been able to capture product requirements and specification data very quickly for a large number of products.

Cross-Org Collaboration: The ease of use has improved the speed at which product management users can onboard and become active with the tool.

Reports: The intuitive ability to create and share reports have reduced the amount of time creating extracts from previous tools.

It helps to improve the delivery of prioritized and most valued tasks, enabling us to get results early and keep people motivated.

The investments and ongoing costs were insignificant given the immediate collaborative environment that was established.

Positive: System development efficiency.

Positive: Process mapping made easier.

All positive so far. The automation mentioned previously has been a jump forward, freeing up department resources and time.

It has saved our development team a lot of time in organizing sprints and communicating within the team effectively.

It provides a great IDE to make things easier, clear, and compact. It has always been a positive ROI

It's worth the money. I don't think any other software could replace the VS. It has helped us a lot to making things ready on time

The only thing I dislike is that it takes a lot of memory space when in an idle state

Positive impact:- They have good features that are very crucial for the organization's development and reporting team.

Positive impact:- Every developer is already familiar with Visual Studio's features, so in this sense return of investment is also good.

Negative impact:- This technology is becoming obsolete and more advanced technologies are coming onto the market.

The management of the development department of the organization has improved considerably

It has allowed programmers to grow professionally which is reflected in improvements in terms of the quality of the staff that works in the organization

As a negative point, licensing costs are high, however, being more efficient as an organization allows for a greater number of challenges

When I first VSTS it was with a team of developers who always work on their own. This project was the first one at the company that used six developers all work on the same product at the same time. Integrating someone else code into the system was an unknown entity. VSTS really helped move this new collaboration forward. The staff who were on this team then moved on work together on other teams because they knew how to handle this type of work.

The learning curve on VSTS is quite large so make sure you have some of your best starting anew VSTS project. They will fail a few times but after a few mistakes they will get how to do things and your build, tests and deployments will all be automated.

The user integration into VSTS is very good. As long as you developers can use Team Foundation Server source control, either Microsoft's or git, then they already have the permission to have VSTS access source control. This is very good.

Via acquisition, we had some Atlassian tools including JIRA, Bitbucket, and Confluence licenses. Total cost for 25 users was close to $5000. Migrating the team to VSTS would net savings of close to $2500.

If you're running TFS, you can save costs on: server licenses (you'll have at least 2 - one TFS, one build server). Save time on maintenance and upgrades of TFS.

It has provided some visuals that are helping my team improve on sprint focus and getting done what was committed for a given week/sprint.

VSTS has significantly reduced our build and release steps and time

Status meeting PowerPoint presentations are easier to make because of the progress tracking feature

Time saved due to little or no confusion on who is assigned which task

One-stop-shop for all project management activities

Collaboration tools cut down on discrepancies between codebases. Time saver.

Prohibitive cost. An open source alternative would be a great way to discover the benefits of the full version of VSTS.

Hard to get acquainted with starting out, but makes sense after a few days. Obviously the Visual Studio IDE integration is top-notch.

Streamlined development workflows

Helped the integration of Agile/Scrum in all pockets of the company

Allow for more robust code from a holistic view, not just developer to developer

Allow for better test approach

The code version control, tasks, capacity all are in one place. So we don't have to move between tools to get the overall state of the project

It allows adding users based on their email addresses, so if tasks are outsourced, it is very easy to include members external to the organization in the project team

It can be shared with the client which leads to more transparency