Azure DevOps Server (formerly TMS)

Formerly Team Foundation Server

We use Azure DevOps to manage the end-to-end lifecycle of our code. We use Boards to capture our backlog and manage the work through delivery, Pipelines for our code repository, and Pipelines for CI/CD.

The firm as a whole makes use of Azure DevOps Server for project management, with its efficient capability to prioritize and approve project needs. Our IT team uses this top-notch application to streamline project management tasks like code versioning and test script administration and to make sure all of our requirements are met through thorough testing.

We work according to Agile methodology and Azure DevOps Server (formerly known as TMS) helps us to track and follow the progress of our work efficiently. We use it for version control as well as to review backlog. As we are more of a Microsoft-based company, it helps us a lot since all Microsoft products can be integrated effortlessly with Azure DevOps Server which enhances user experience.

Azure DevOps Server is used across the entire organization to manage projects and with effective prioritization and approving capabilities to our project's requirements. Excellent product that is by our Information Technology department to manage projects with perfect code version control and test script management and empowers them with easy tools to track and ensure testing covers full requirement needs.

Azure DevOps Server is a collaborative project management tool we used in one of our projects while working from home to collaborate among team members, it helped us to track bugs, commit codes, create user story, and various forms of reports related to project. It allows integration with our existing IDEs, version control like Git, setup the CI/CD pipelines for code testing, release and deployments.
Azure DevOps Server was very helpful to our teams while we started working remotely, helped in increasing the productivity and prototyping the projects for release without any delay. Best part of using this tool is reporting, we were able to create Kanbans dashboards for integrated reports.

I work with an agile development team and we use DevOps for capturing and managing user stories and bugs. User stories are categorised into Epics and Features with ease, and it's a very valuable tool for planning and resource management.

Managing software development across several phases can be extremely difficult due two it’s complexity. DevOps and CI/CD can help to control this complexity. However, these methodologies need software solutions that suit this agile approach. In this case Microsoft DevOps is the best suite available at the moment. We use Microsoft DevOps end to end to manage the development of a cross-platform mobile application. As said we use the suite end to end. Starting with „Azure Boards“ to derive, document, and manage backlogs; „Azure Repos“ to manage repositories and changes/change requests; ending with automating testing and pipelines with „Azures Testing“ and „Azure Pipeline“. Integration and extensibility features are used for productivity purposes as well. In this way, Azure DevOps brings together all levels of information at code in one single tool. Especially the automation options in the pipeline Tier helped us to automate delivery processes for both platforms (iOS & Android).

Azure DevOps is a very good tool provided by Microsoft. It is very useful in terms of document version control and reporting point of view as I am using this in my project for the above two points.

We leverage Azure DevOps to manage the Agile backlog of one of our biggest internal platforms. The main functionality is leveraged to track stories and move things along from requirement drafting, to design and right through the development and QA. Some other functionality that is leveraged is the calendar to ensure that we are capturing the agile team's OOOs since most of us are from various orgs/teams throughout the enterprise.

One product to cover the most common engineering activities in tech irrespective of the domain. Whether the team is in medical tech, fintech, aerospace tech, or a business process outsourcing firm, this platform has all the common tools needed in an Agile workspace with extreme collaborations across DevOps, Product, and Engineering. This gives the best centralized toolset, especially if your organization is already a Microsoft-based firm.

We are using Azure DevOps [(formerly Team Foundation Server)] in our IT department to help us with Agile software development. It helps us to track code changes with various work items like Tasks and Bugs. It also helps to test, build and deploy those changes to multiple environments. It easily integrates with Visual Studio to create a seamless experience.

We use Azure DevOps to manage and store all our corporate source code and deploy our applications to a string of various environments from development to production. In addition, we use Azure DevOps on a daily basis to manage our agile-based projects. Azure DevOps is used to track and follow the progress of customer support tickets as well. Our business analysts use the Agile Project Management feature to log user stories.

We use Azure DevOps in our business unit as an end to end solution for our ALM / SDLC. We have several organizations with various projects, repos and pipelines. We are following Scaled Agile Framework (SAFe) which is well served by Azure DevOps backlog module. We are happy that we could back trace a cloud release through the pipelines back to the work items in the backlog.

The biggest and best use of Azure DevOps Server (formerly Team Foundation Server) is the gathering and management of user stories for development, coupled with the other elements of information sharing and the metrics it can provide. The ability to track bugs, and the fixes to those bugs, and generally track the evolution of your agile development group is a major plus. While primarily focused on the development organization, Azure DevOps Server (formerly Team Foundation Server) is used by the lines of business by product owners and their associates.

Our dev team uses [Azure DevOps Server] to receive requests for our site from all departments in the company. I have used it as a marketing user. It is being used across the entire organization. It helps to address the business problem of prioritizing the work that we need to be done on our website.

TFS is used for ALM of all in house supportive software, development of our flagship product and clinical studies for our latest version. TFS acts as a central hub for requirements, code, tests and reports. It links these facets of the product life cycle together.

Azure DevOps Server is being used across the organization as a defect/bug tracking system for IT projects similar to Jira. The business problems it addresses are mainly related to issue tracking and traceability. There is a multitude of IT deployments at our company, and hence, lots of QA/UAT testing. When defects are captured during these phases, they are logged in Azure DevOps Server and tracked.

Our IT department uses Azure DevOps Server to manage all our projects and for software development.

I am currently using Azure DevOps Server with a client on a scrum project to build a business application. In the company, Azure DevOps Server is mostly used by our specific project but does have other users and different projects. It helps manage the scrum process and provides organization and clarity to a project with many moving parts and members.

Source control for application code, for the most part. For database code, it integrates well with Red Gate software. Besides scripting out database schema, Red Gate will even script out static data so it can be source controlled as well within TFS/ADS. My previous employer used TFS/ADS to automate builds and as a ticketing system.

It was used as an Application Lifecycle Management (ALM) system that takes care of all aspects of software development from planning, requirements gathering to coding, testing, deployment, and maintenance. Also as a Source Code Control(SCC), Bug Tracking, Project Management, and Team Collaboration platform.
SDLC Management (SDLC – Software Development Life Cycle):

• Software Team Collaboration
• Source Code Management
• Supports Agile, Scrum, CMMI
• Bug Tracking
• Integrated Test Tools
• Automated Builds

Azure DevOps is being used by the entire company. We use that to build our build and release pipeline to continually release our deployment.
For our department, we build infrastructure with Terraform and deploy it to the Google Cloud Platform. It solves our problem of not having a CI/CD pipeline. It makes our development cycle much faster.

We use the Azure Dev Ops server throughout the IT department of our organization. It is utilized by Business Analysts, Scrum Masters, Developers, and QA. We have Git integration enabled and it has been an awesome experience with its integration to our source code. I especially love the built-in ability in the latest version to perform source code wide string searches. This makes it exceptionally easy to find code references and delve into new areas quickly. Aside from source control, it is our UI interface for all of our SCRUM project management needs. We create all of our tasks on the work items board and it makes it easy to see the progress of the overall team. Overall it's just been a great experience and I can't think of any complaints.

We have been using Azure as one of our cloud providers for a few months. Not all departments in my company are using it but a few of the critical applications that need multi-cloud for managing resilience are using it. How these departments use it is for an end to end infrastructure on the cloud and set up and launch an app in Azure.

The Azure DevOps server is used within our IT department. We use it to have simplified server management and improved connectivity with remote sites. It also allows us to save money, as we may have options to pay per use or month-to-month. It is also hosted on-prem, which is beneficial.