Azure DevOps with SAFe
We are following SAFe practices by using Azure DevOps starting from PI planning to retrospective. We are using all features starting from …
Starting at $2 per GB (first 2GB free)
View PricingOverview
What is Azure DevOps Services?
Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
Recent Reviews
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Reviewer Pros & Cons
Pricing
Azure Artifacts
$2
Cloud
per GB (first 2GB free)
Basic Plan
$6
Cloud
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
Cloud
per extra parallel job (1 free parallel job with unlimited minutes)
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Product Demos
Azure Pipeline Tutorial | Azure Pipeline Deployment | Azure DevOps Tutorial | Edureka Rewind - 3
YouTube
Product Details
- About
- Tech Details
- FAQs
What is Azure DevOps Services?
Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities, along with the basic plan which includes:
- Azure Pipelines: automatically builds and tests code, combines continuous integration (CI) and continuous delivery (CD)
- Azure Boards: Work item tracking and Kanban boards
- Azure Repos: Unlimited private Git repos
- Azure Artifacts: 2 GB free per organization
Azure DevOps Services Video
Introduction to Azure DevOps
Azure DevOps Services Technical Details
| Deployment Types | Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Unspecified |
| Mobile Application | No |
Frequently Asked Questions
Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
Reviewers rate Support Rating highest, with a score of 8.1.
The most common users of Azure DevOps Services are from Enterprises (1,001+ employees).
Comparisons
Compare with
Reviews and Ratings
(453)Attribute Ratings
Reviews
(51-66 of 66)Companies can't remove reviews or game the system. Here's why
January 15, 2018
All under one umbrella
It is used across the organization. We use it for tracking tasks as well as for CICD.
- Task management
- Capacity Management
- CICD
- Once you add a new sprint, it does not automatically reflect in the left panel of work items. You have to select the iteration under default teams settings. This is a bit confusing and difficult to figure out if you don't know.
- When a task is marked as Resolved, the remaining time does not become 0 like it happens when you close the task. It may be a good idea to reset it to 0 for resolved tasks as well.
- The system allows you to close a user story which has open tasks under it. A warning mentioning this while closing the user story will be good.
November 20, 2017
Good experiences of VSTS in test automation
VSTS is used across the whole organization. It is the backbone of the software development process in our company. Agile testing activities are planned and implemented with it.
- Easy to implement continuous integration and build automation.
- Easy to take in use and learn usage.
- Offered in cloud environment, so it can be used everywhere.
- TFS based build environment is a bit unstable.
- Builds could have more e.g. Bamboo style configuration options.
November 14, 2017
VSTS as development team companion
We use VSTS as source repository for all the web projects. We also manage and assign the tasks of the development team.
The continuous integration and the continuous deployment are provided with a mix of on premise installations and Azure instances.
The project management monitor the projects advancement with customized reports.
The continuous integration and the continuous deployment are provided with a mix of on premise installations and Azure instances.
The project management monitor the projects advancement with customized reports.
- Easy to install.
- Full integrated: source control, task management, report tools.
- Plugin for VS, Eclipse, Rider and many others.
- Backup and restore is really slow.
October 23, 2017
VSTS just keeps on giving!
VSTS is our ALM tool of choice, we use it to plan, collaborate and test.
Over the years we have slowly rolled access out further to stakeholders and developers alike to ensure everyone is working from one tool which has ultimately resulted in shipping products much faster than before.
- Source control - this is the primary reason we moved from in-house TFS to the online offering. It's fast and robust.
- Feature rich - there are a lot of useful features in VSTS that have become our go to tools. Test manager for bug reporting being a key one outside of the source control functionality.
- User Interface isn't that intuitive - I think more could be done to make the User Experience much better. We have lost countless hours trying to do the simplest of things such as creating new iterations and making them visible in the UI.
October 17, 2017
New guy on the VSTS block.
We are moving our entire code base from on-prem TFS to Visual Studio Team System(VSTS) with GIT repositories. We are taking the opportunity to move to a complete continuous integration solution. We also feel that moving to GIT will improve code quality with the way that branches are lightweight and how code reviews are a fundamental part of the way you do things in GIT.
- Integration with Visual Studio
- Option to use GIT or TFS repositories.
- Plugins galore.
- I think the documentation lags too far behind the actual product.
- Troubleshooting could be easier.
- There are some glaring pieces missing or are just obscure to use. The way you publish a built website is pretty bizarre.
October 06, 2017
VSTS - a polished project management tool
Microsoft Visual Studio Team System was used to manage projects by my team for easy access to the health status of the entire project. It was used for issue tracking, version control, build status and statistics, code analysis and planning delivery.
- It shows the health status of the entire software development pipeline with easy access to information.
- Work items templates are customizable as needed.
- The work items can be moved around from one type to another easily if needed.
- 255 character path limitation.
- Dependency on the internet means source control needs to be off when offline.
- Agile support is not good and hard to maintain.
September 22, 2017
VSTS for Agile Dev Shops
Microsoft Visual Studio Team System (VSTS) is currently being used by Development, QA, Support, Production Operations, Development Operations, and is being slowly rolled into our business unit that practices Agile for business. We are using it to track epics, bugs, feature requests, and tasks. VSTS has greatly improved our workflows, tracking, metrics gathering, and reporting.
- Bug, Feature Request and User Story Tracking
- Reporting
- Workflow planning
- Integration with ZenDesk could be improved and expanded. Especially the ability to create VSTS ticket from ZenDesk using custom fields.
- Ability to add custom workflows steps to the completed column could be added.
September 12, 2017
A Solid Tracking and Deployment System
VSTS is used across the organization for the full breadth of its features. It is used for bug and feature tracking, continuous integration builds, deploys, and automated testing. Every portion of development uses it, developers, quality assurance, product owners, etc. Everyone is in the system multiple times throughout the day to manage their workflows.
- Integration of version control/pull requests to bug tracking.
- Multiple views of team work - lists, kanban boards, etc
- Supports the full product lifecycle from planning to deployment
- The website has a tendency to log out, and the sign-in is a popup that bypasses password managers.
- All instances look the same. If you need to use multiple versions, it can be hard to tell which you are in.
- The security/permission system is strange and is not simply the sum of your roles.
May 09, 2017
VSTS brings your codebase to life!
It is being used across the development team department and is responsible for integrating, managing and deploying code bases to our companies' systems. The fact that our codebase is available outside our company boundaries via VSTS' servers, running independently of physical problems that could afflict our local servers bring us another level of comfort since most of the issues are actually solved from home.
- Has a very low cost for micro (free up to 5 users) teams.
- Integrates flawlessly with TFS, bringing all its known features together with a minimum level of expertise.
- Is available online, everywhere.
- The Agile support in the VSTS dashboards is cumbersome, not-so-easy to deploy, and not easy to maintain
- Older versions of Visual Studio may suffer from older bugs, such as the 255 character path-limitation.
- The fact that it is served online means that, in the (very rare) occasions when it goes offline, it means your entire team must plug the source control off, and wait for its return to reunite the changes made.
February 17, 2017
Easily integrated source control for Visual Studio
We use VSTS for software development for source control and issue tracking.
- Source control
- Issue tracking
- Test automation
- Customization
- Permissions difficult to configure
November 21, 2016
TFS review as ALM solution
[Microsoft Visual Studio Team System is] Used as source control, and complete continuous integration solution and ALM product.
- Agile ALM with ease.
- Flexible work item types.
- Great query engine, large API set.
- Team dashboards not in par with others like JIRA.
- Quite expensive.
October 05, 2016
Visual Studio for database management
Microsoft Visual Studio is heavily used by our organization. We perform data maintenance on millions of data lists, and Visual Studio makes it very easy to do that. Data files of various formats can be imported into Visual FoxPro. SQL is then used for queries on the data set.
- Easy to use. I began my career as a data analyst without any prior knowledge of Visual Studio, and with very little training, I am a completely independent worker.
- In the business of database management, it is important to have a software that can handle millions of records effectively.
- My company uses Microsoft Visual FoxPro for database management for clients. It would be helpful if FoxPro fully supported SQL. It currently accepts some SQL commands, but it is not fully compliant.
Visual Studio Team System was used by myself in our local development team, and much wider in the company for most development teams. When working on most products within the company Visual Studio Team System was the development platform of choice. Visual Studio Team System provides an excellent all-in-one solution for development which is why it stood out at the best solution for most projects we worked on.
- Coordination of development between local and remote teams
- Centralized build process with a particular good focus on test driven development
- Good selection for technology platforms from a single IDE
- More support for non-Microsoft development languages
- Wider integration with build tools (such as Jenkins)
Our development team uses Microsoft VSTS/TFS for a variety of use cases. Some of those use cases include creating/tracking requirements, managing source code across teams, creating test cases, etc. The main business problems it addresses is providing a centralized place for planning, project tracking, and monitoring of all aspects of our application.
- Excellent reporting/analysis tools - customized dashboards and reports aid in project planning, monitoring, and execution.
- Ease of use in managing change requests in codebase.
- Customizable - not a one size fits all solution. Easy to customize to fit individual developer needs as well as overall needs/preferences of the team.
- If server goes down, you are essentially blocked from development. You can't check out files and edit them until communication with server is re-established.
- Work must be done within confines of Visual Studio. It doesn't play well with external files.
- Version control could be improved.
The bulk of our development is written using Visual Studio. I have used Visual Studio for my personal business as well as my current contract at a large company. We use it with SVN to manage our codebase. It has the options for each developer to customize it to fit their development preferences.
- Organization of Codebase.
- Works with other technologies for good development collaboration.
- Customization.
- The large amount of features can make it feel like overkill and loses elegance.
- When using with other technologies the ease that it integrates.
- More front-end and UI features would be very helpful for me.
August 25, 2014
VSTS - It's Not Your Mother's SDLC Management Tool
Visual Studio Team System (VSTS) is used as a software development lifecycle (SDLC) management tool for our entire company. All projects use VSTS/TFS version 2010 at this point and we are looking at upgrading to 2012, too. As a Capability Maturity Model Integration (CMMI) Level 3 company, VSTS/TFS provides the MSF structure for Process (which also allows tailoring of our processes) and VSTS allows us to create work items to track our requirements, change requests, tasks, test cases, burn down of work, conduct meetings, and capture artifacts related to following our processes as well as providing proof that we follow those processes. We can create queries to help us find data/information related to requirements and their area paths, bug rates and resolution time periods, build status, etc. VSTS/TFS has a SharePoint module that allows us to store/link documents to work items as well, which makes it an excellent tool for SDLC management as it helps us plan, execute, monitor, track, and deliver our products consistently and with quality.
- The Excel reports provided within VSTS 2010 help provide visual information in the form of Excel pivot tables and charts that are easily tailored and modified to provide valuable feedback on burn-down slope for development, bug rates that tie to milestones, build status and quality, and other Project Management activities such as unplanned work, requirements development/progress, and backlog development.
- We use Work Item Templates within the SharePoint server, so that we create consistent/correct work items such as Requirements, Change Requests, or Bugs that take our process requirements into account and ensure that the work items meet quality standards. We embed the text of our process within these Templates to help me (and others on the Team) make sure that our Work Items aren't missing any information, that artifacts are correctly captured, and there is accuracy in the information captured, presented, and used by the Team when reviewing, validating, baselining (with our customer), and then triaging work into an iteration.
- The Team Project Portal allows a Project Manager (or any other Team Member) the ability to create customizable dashboards using the Excel Reports and the charts created when pulling in VSTS/TFS data related to an iteration, a build, the issues or risks associated with a project. These dashboards are fairly easy to create and provide a wide variety of widgets that can be used to present pictures, charts, lists, links, whatever you need to help the team establish a focal point for finding status, learning about milestones, sharing issues, etc. I particularly found this module useful when I was a Project Manager for several Teams and could use the dashboard to present information on our burn-down, bugs, and risks to management just by creating a useful dashboard.
- Creating SQL Queries is very easy too, once you learn how to structure a SQL query. VSTS/TFS is essentially a database of work items that document the work planned, work in progress, what was delivered and when. You can filter the data by dates, by who the work item was assigned to, who created it, the state changes that occurred and when, and on and on. I have found the query ability enormously useful when combing through the data to find answers I need related to creating requirements, tracking tasks, determining when bugs were resolved and fixed, etc.
- Lastly, I really like being able to export the information (in the form of Work Items) provided within a TFS database query to MS Project or MS Excel where I can filter the information, view hours assigned to each developer (to help with capacity/velocity planning), create other excel reports/charts, or plan an iteration using MS project using the tasks and hours to determine the timebox of a particular iteration.
- I don't have any recommendations for improvement myself as I use the tool for specific reasons and for all my own uses, it works very well. However, I AM looking forward to the upgrade to the 2012 version because I'm excited about improved graphics tools and improvements in reports, etc.