Overview
What is Azure DevOps Server?
AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server)…
Azure DevOps is a game change
Agile project management with automation and tracking.
Azure DevOps Server: All-in-one and High Performance Agile Tool
Azure DevOps Server- A Collaborative tool for productivity
A non-developer's thoughts
Manage and automate Software Development End2End.
Sure about Azure...DevOps
Engineering Based Toolset for Extreme Collaboration
All-in-one solution with stability
Software Management and Agile Project Management in One Package
Azure DevOps for a SAFe based, SOC2 Type 2 audited, heterogenous cloud microservices SDLC / ALM
Good Agile Management Tool
Still TFS to Me
TFS is an excellent tool to support the full ALM
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
What is Azure DevOps Server?
AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine…
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
37 people also want pricing
Alternatives Pricing
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.
What is CircleCI?
CircleCI is a software delivery engine from the company of the same name in San Francisco, that helps teams ship software faster, offering their platform for Continuous Integration and Continuous Delivery (CI/CD). Ultimately, the solution helps to map every source of change for software teams, so…
Product Details
- About
- Tech Details
- FAQs
What is Azure DevOps Server?
Azure DevOps Server Technical Details
Operating Systems | Unspecified |
---|---|
Mobile Application | No |
Frequently Asked Questions
Comparisons
Compare with
Reviews and Ratings
(282)Attribute Ratings
Reviews
(1-25 of 28)- Simple tracking of progress throughout the project.
- Perform project management duties with superior ability to set priorities and approve work.
- In order to ensure that all of the project's requirements are met, a thorough test plan is necessary.
- It doesn't work well with tools from other companies.
- Improvements can be made to the user interface to make it more natural to use.
- I also think capacity planning may use some fine-tuning.
- You can integrate it effortlessly with almost all Microsoft products
- Supports Agile and can be used for version control
- Bug tracking
- Ease of use
- I feel that because it's a Microsoft product, it integrates better with other Microsoft products too. Since mine is more of a Microsoft-based company, it's not a problem for me, but for others, you might want to consider this before making any decision
- The user interface could have been better
- Agile boards can be better
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.
- Reporting Integration- Azure boards provides Kanban and other dashboard, their templates for easy management of project.
- Project Pipeline- easy integration and development of CI/CD pipelines, helped in testing, releasing project artifacts.
- Version Control- Integration with Git and code IDE made it easy to share, review our code, fix bugs and do testing.
- Azure test plans can be improved to be more automated, existing generic templates can be added to create more test plan in different languages.
It helped our team members with the productivity, early prototyping and release. Create summarised reports of different aspect of our projects.
Even in other scenarios it is one of the best tools to use for collaboration and project management. I haven't found any specific scenario where it is not appropriate.
Manage and automate Software Development End2End.
- Integration and Extensibility Features.
- Pipeline automations.
- Configuration and flow of change requests workflows.
- Configuration of Boards (backlogs).
- Flexibility and ease of use of dashboards.
- Change logs of items.
- Expand automation options for iOS pipeline (include further triggers).
- Mass handling of backlog items could be improved.
Engineering Based Toolset for Extreme Collaboration
- Version control
- Requirements definition
- Secrets library management
- Continuous integration and deployment
- Wiki Markdown customization
- Better Syntax Highlighter in Repository
- Improvements in Requirements Definition Customization
All-in-one solution with stability
- All-in-one product (don't need a bunch of separate connected products)
- Integrates easily with other Microsoft products
- Can use git or its own version control with less steep learning curve
- More stable than Atlassian products
- No clear-cut way to track items in a release, especially if they are not code change related
- Agile boards still lag behind Jira in terms of functionality
- Bamboo and Confluence have nice features over DevOps Build and Sharepoint
- Azure DevOps easily handles our source code and works seamlessly with Visual Studio (our main development environment).
- Our business analysts use its features to document and assign user stories for Agile-based projects.
- Our deployment team uses Azure DevOps to push code from development to main to user acceptance and finally production.
- For managing Agile projects, web-based navigation is terrible. There's no easy drop-down menu system you have to hunt and peck around to try and find pages to manage your hours.
- Our management needs the ability to predict when development may finish a project. Azure DevOps fails here because it doesn't easily provide a feature to let you predict an end date and it doesn't easily provide you with a feature to export the data to Excel so you could plug-in a formula to calculate an end date.
- The menu options for code management are sparse. It would be great if they had a feature to let you simply drag and drop folder structures.
TFS is an excellent tool to support the full ALM
- Linking together all aspects of the application life cycle, from requirements to code to builds and test.
- Trace-ability of all application life cycle via reports and queries.
- Automated testing.
- Flexibility of source code management. Centralized or distributed.
- Upgrade paths could be handled better. Very difficult to upgrade with customization in place.
- Capacity planning could be improved.
- Dot Net framework 260 character path limit is ridiculous.
Azure DevOps Server a great choice
- Ease to manage code.
- Compatible with several services.
- Version control.
- Need more templates.
- Can be confusing to use at first.
- Reporting could be better.
ADS/TFS Offers Integration and Automation
- It allows you to view the history of any piece of code. Shows the differences. If you are a good 'code archaeologist' you can figure out why things were changed and when.
- It provides a repository of your code so you can reconstruct it in case of a catastrophe. With code history, you can restore the code as it was before some change that didn't work, was made.
- The tickets it creates can be linked to the changes in the code. This adds an important element showing causation. This code change resolves or is associated with this ticket which includes the purpose of the change.
- The way it uses workspaces is non-intuitive. I required help from our resident expert to get TFS set up initially.
- Don't forget to refresh again and again. Yes, of course, you want the latest changes - you shouldn't have to remember to keep hitting that button.
- Even though it uses a Microsoft SQL Server database to store its data, it uses the database in a non-standard way. Don't try to do the usual MS SQL backups - let TFS handle the backups.
Azure DevOps Server -What it offers
SDLC Management (SDLC – Software Development Life Cycle):
- Software Team Collaboration
- Source Code Management
- Supports Agile, Scrum, CMMI
- Bug Tracking
- Integrated Test Tools
- Automated Builds
- SDLC Management (SDLC – Software Development Life Cycle).
- Software Team Collaboration.
- Supports Agile, Scrum, CMMI.
- Bug Tracking.
- Reporting
- Code integration
- Project Management integrations
Azure DevOps server is a great product
- Git integration has been fantastic.
- Provides a convenient UI for managing the SCRUM process.
- Built-in Code Review feature and completion policies.
- I wish I could default to a specific dashboard on load.
Take an advantage of Microsoft TFS for easy integration with other Microsoft family products
- TFS makes it easier to build technical features and acceptance criteria that different team members of Product Manager, Engineering, Quality Assurance, and Release Management.
- It enables the product managers to review technical backlog, prioritize features and go to market that helps improve key performance indicators.
- It provides seamless integration with Microsoft products like SharePoint, IIS, Visual Studio that helps integrate and exchange data.
- TFS UI could improve like some of its major competitors with fewer options on the same UI page. TFS tries to offer too many options on the same UI.
- Development in branches is hard to achieve and TFS has a room for improvement.
- Integration with non-Microsoft is difficult. TFS could provide easier integration with other product lines to improve acceptability.
- Easier to build a technical backlog.
- Create user stories, features, EPICs, assign tasks and acceptance criteria, etc.
- Make a Product Manger's and engineering teams' life easier in meeting and tracking.
- Project managers can easily track the work and create reporting.
Code versioning tool with room for improvement
- Integration with Microsoft products, like SharePoint, IIS, Visual Studio
- Users are able to access via desktop client, web browser and through Visual Studio
- Code version control
- Bad UX and UI in the web interface
- Merging code is a very hard task
- Development in branches is also hard to achieve
- Not so easy to upgrade server version
Project Management made easy!
- The environment is easy to use.
- It is very easy to track progress of various work items.
- Project management is made really easy.
- There is no ability to work offline.
- There is a learning curve involved which is little hard to get when you are using the tool for the first time
- The UI can be little more organized.
- Version Control
- Track Bugs, Change Requests, Tasks
- Compare versions of SSIS can be improved
- Merging of the SSIS Code can also be improved
I like to work with Team Foundation Server
- I like the Team Foundation Source Control Management much more compared to other Systems like GIT, because:
- - Perfect Integration into Visual Studio
- - Easy and direct checkout/check-in
- - Perfect branching and merging
- - Workflow Support with autmated Reminders
- The Build System is just great. Since Version 2017 its very easy to integrate self made tools into the build process.
- Easy Managament of Users and User Rights.
- Team Foundation Server could be improved in the Task and Backlog Managment for smaller Teams. E.G.: It's hard to quickly write down Tasks during a meeting because you have to fill in lots of Fields per WorkItem. It is hard to push the Items around.
Manage with order software deployment
- No data loss
- Multiple deployments
- Deployment without problems of versions
- You must avoid getting stuck with check-in
- Developers must avoid overwriting
- The developers must be at minimum coordinated among themselves during the developments
TFS is great for a Microsoft Shop
- Continuous integration when the team is using azure is really easy.
- It's fairly intuitive to use.
- Azure or IIS deployment is very easy.
- The project management/scrum piece is hard to learn.
- The Wikipedia functionality it provides isn't very useful for lack of features.
- It takes a REALLY long time to check in a large number of newly added files.
- If your file paths get too long, TFS gives you errors.
You could use some other source control with .NET but it integrates so well with the rest of the Microsoft family and is so reasonably priced, there'd be no need to.
TFS - The complete Development Tool
- Work Item tracking - The ability to define the flow of your work items to match your development/test process is really valuable
- Version Control - The ability to easily track changes between every checked in version of source code can be a life saver
- Project Management - The project management dashboards showing things like burndown enables us to easily track whether we are on target for a release
- Integration between our help desk system and TFS was possible but not as easy as I would expect considering both are Microsoft products
- Advanced reporting for dashboards could be made easier
Team Foundation Server, making the development process just that little easier to manage
Apple Trailer Download:
- Source code management - Team Foundation Server handles our source code and makes examining check-ins and changes nice and easy.
- Project Management - Keeping the thousands of feature requests and bug submissions under control and in the right place is simple enough in TFS.
- Administration - As with most Microsoft products, administration is not a difficult affair. Familiar interfaces and tight integration with other Microsoft products make most tasks intuitive.
- Web interface - While the web interface is certainly very feature rich, there's just no substitute for a good desktop interface sometimes. The test side has Microsoft Test Manager as a desktop application counterpart, but almost everything else is done via the website. Some project management tasks could be simpler in a desktop environment.
Is TFS the right tool?
- TFS has an excellent interactive UI for all users to make source control easy to use.
- TFS has the backing of a major company, Microsoft. Updates and the way it is used gets regular updates.
- TFS integrates into Visual Studio.
- TFS has many tools for many different areas in the development life cycle.
- There is no real ability to work offline. You need to be actively connected to it in order to see history.
- Having many hands in the same project/file can cause conflicts that can be hard to resolve.
- having a "master" branch is difficult in TFS, it can be done but it is slow and cumbersome and not an intuitive process.
TFS = meh
- Project management
- Scrum
- Integration with visual studio
- Not a user friendly implementation of Git
- TFS version control is not widely used in favor of Git
TFS - Code and Testing and Tracability Review
- Tractability, Code to defects, Test cases to Requirements
- Metrics - Reworks on development, test cases to change, Defect by root cause
- Single source for all to pull data, business and IT
- Simplify automation testing, too much repetitive code with recording
- Easier access to Code reviews - our development team struggles with this
- Shelving and un-shelving details - development struggles in this area
Great Project Tracking Software
- Field customization is a feature TFS has that I particularly like. We have a very specialized customization of TFS running so that I can query for specific iteration/release paths that are relevant to our metrics. We also utilize a unique workflow structure for bugs and user stories as the process from creation to close is unique within our company.
- TFS does their web view really well, especially with newer versions of the product. Often times, I feel that very little is lacking when I am logged into the web view of TFS. I am able to bulk edit items in the newer version of TFS, and at my old job we even set up the ability for QA to push checked in code to stage environments through TFS.
- Finally, I feel TFS does a very good job of keeping historical track of actions performed to tickets. If someone has edited a ticket in any way, I can review and identify who made the change and when. This helps give me context when a developer contacts me to ask me a question related to the wording of a ticket. This also helps hold people accountable if tickets are written incorrectly or incompletely and prevents people from passing blame to others.
- The older versions of TFS are more lacking in the web version-- if you aren't updated to 2015 or above I believe, a lot of the web features are not available (like bulk update). You really have to keep up to date with TFS for the best features, and it's no simple task to migrate your entire instance of TFS from an older version to a newer version.
- VSTS is supposed to be a virtual version of TFS that we've been looking into, but it severely limits customization options for ticket templates and workflows. It would be nice for VSTS to eventually carry that customization over so we could feel more comfortable switching to "the cloud" so to speak.
- Queries are a very powerful tool, but normal business users struggle to understand how they can best utilize this tool to analyze tickets. Because of the permissions structure in all companies I have been a part of, I've never been able to save my custom queries to a public folder in TFS for business/project users. Instead, I have to take time to train these users and give them guidance on how to best create queries for their needs. This is admittedly a business process issue, but it could potentially also be resolved with some good training/guidance around queries provided by TFS themselves.