TrustRadius Insights for Azure DevOps Server are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Efficient Task Management: Users have found Azure Boards fast and easy to use once a good structure is established, enabling quick creation or modification of task types. This reduces administrative overhead and facilitates the creation of numerous smaller tasks.
Simplified Setup Process: Reviewers appreciate Azure Repos for its simplicity in setup compared to other solutions, with most options readily available including user management. The out-of-the-box features streamline the onboarding process.
Powerful CI/CD Pipelines: The Pipelines tool within Azure stands out for its robust capabilities, allowing users to swiftly create pipelines, automate workflows, and easily track their progress effectively throughout the development cycle.
Azure DevOps Server makes integration between different areas with the agile process, in my case I use Kanban to guide a hardware design team and Azure lets me create several features for each part of our PCB design process, and I can manage how each person on the team is going on, review cases are much easier. I can link all tasks from the first requirement to the reports from the qualification tests. Each project has an epic structure that lets us navigate over all projects and create multiple teams in the same workspace. I can bring a lot of metrics showing who is delaying, effort by project, and much more info that helps my board to understand if the critical tasks are being managed as requested.
Pros
multiple team management
one server for all types of team connected
version control is easy
scripts to automate simple tasks
Cons
integration with CADs for hardware design
improve the link management for child/related/parent work items
template for several common work flow
Likelihood to Recommend
For an agile team, DevOps is great. Using scrum, Kanban fits perfectly into the project structure. The web interface lets anyone, anywhere, interact with work items.
The version control is great if you code, but if you design with CADs, it still lacks some link features that could help non-code documents.
It is being used for complete ci/cd process, used to create pipelines and manage project with ado board.
Pros
Continuous integration
Continuous development
Project management
Cons
Ease of usage
More integration with open source
Navigation
Likelihood to Recommend
It is well suited for creating build pipelines to automate the complete release process and to create testing pipelines. Create and assign different task on ado board. It is also used for code analysis by integrating it with sonar . But it is less user friendly then hira board to mage the scrum and kanban board
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.
Pros
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.
Cons
Azure test plans can be improved to be more automated, existing generic templates can be added to create more test plan in different languages.
Likelihood to Recommend
In our case it was best suited when we started working remotely, we were able to track everything in out projects easily, able to share our codes, give reviews for the codes and also create integration and deployment CI/CD plans for the release and testing. 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.
VU
Verified User
Engineer in Engineering (Computer Software company, 10,001+ employees)
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.
Pros
End to end tracing of released artifacts
Scaled Agile Framework implementation with Azure DevOps backlog
Versatile and powerful pipelines as code
Cons
Ability to automatically link automated tests executions to Test Cases
A better file editor (like VS code) in the git repo UI
Likelihood to Recommend
Well suited:
Large teams developing heterogeneous applications
Following SAFe process / Multiple Agile Release Trains (ARTs) / Portfolio management
Company undergoes regular external audits of their SDLC practices
Comprehensive reporting is required
Pipeline templating is required
Many git repositories are needed having to link to a unified backlog
Access to backlog work items and reporting is required for business stakeholders
TFS is used across the organization as an Application Lifecycle Management tool. This addresses the problem of needing a central way to demonstrate the status of projects/applications.
Pros
Security
Reliability
Scalability
Cons
TFS templates are not as flexible as the business requires
Likelihood to Recommend
Well suited for any IT team. Great way to track and manage the software lifecycle for projects, whether for one team or many teams.
VU
Verified User
Contributor in Information Technology (Computer Software company, 201-500 employees)
Team Foundation Server (TFS) is used by the development and test teams at Peppermint Technology. It is used for management of our source code and we also take advantage of the automated build functionality. We also use it for storing all of our release user stories, tracking enhancements and bugs as well as taking advantage of the project management tools to support our agile development process.
Pros
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
Cons
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
Likelihood to Recommend
TFS is a really good tool for managing small to medium-sized development teams. The ability to customize it to suit your own processes means it should be suitable for any business, though I have to confess I do not have any experience of using it within a large enterprise sized development team split across disparate locations.That said we do have developers spread across the UK and they manage to work remotely with no problems at all.
We use Team Foundation Server as a hub for our in-house software development. It allows the development team to centralise software issues, feature requests and testing.
Apple Trailer Download:
Pros
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.
Cons
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.
Likelihood to Recommend
For a software development team, Team Foundation Server definitely ticks a lot of boxes. We use the Scrum methodology and Team Foundation Server enables us to manage current sprints and plan for future sprints. Even for 'pet projects' that some developers have, Team Foundation Server is a useful tool to submit their code for archiving and creating tasks to work on those projects.
Team Foundation Server (TFS) is being utilized by many different departments within our organization. We personally use it to track tasks, user stories, bugs, releases, and test cases. Developers associate specific check-ins with bugs/user stories within TFS which, when pushed to our staging environments, are then assigned to QA/UAT for review. User stories and bugs are tracked as release scope for regular releases. The ability to associate releases/user stories/bugs in many different scenarios is priceless. It allows us to create different metrics/queries to measure success and potential failure, as well as to analyze what went well or what went wrong. TFS can be confusing for those new to the field or those who are older and used to other programs, but once the learning curve is achieved, the user tends to take well to the program.
Pros
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.
Cons
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.
Likelihood to Recommend
TFS is well suited for a team looking for structured requirements, projects, test cases, bugs, user stories, etc. It works well for planning things out and coordinating with others to see the "bigger view". TFS is great in scenarios where paper trails and other auditable data is needed to keep people in check and accountable. The search and query functionality allows users to search for past issues that may have been resolved previously and have crept back, and can provide history and context surrounding project functionality/decisions.
TFS might not work as well for a team truly looking for a scrum experience. Although my companies have both claimed scrum, they both planned out releases at least a few weeks in advance. If you're changing things on a daily basis it might not be as great of a tool.
Team Foundation Server is used by the entire company across the globe. Development uses it for obvious reasons in developing new software and fixing bugs that are found and logged into Team Foundation Server by our quality assurance analysts. Support uses Team Foundation Server to log issues from clients and professional services uses it to make minor changes while in the field with clients. Sales uses it to demonstrate new features to clients and to set up environments when holding trade shows.
Pros
Allows a great deal of history detail on every issue found or new feature added. It keeps a detailed history of any code changes by developers so you can always see who changed what portion or code.
You can adjust users permissions down to a group of users (i.e. testers vs. developers vs. managers) and can get very technical with permissions for each group. The permissions can also be set based on certain portions of the code base not just on the entire thing.
The information that is tracked is great. When you find an issue and you log it in Team Foundation Server you have many options for fields to utilize and edit to make sure you get the correct team of developers to look at it. You can also have different requirements for each issue or when checking in code such as changes made, priority level, area and iteration (these are used for internal development purposes usually).
Cons
Simplify the permissions interface and navigation. Permissions are great but sometimes finding the correct screen is difficult.
Make the interaction between different versions easier. Sometimes you can run into issues when trying to use an older Team Foundation Server server with a new Team Foundation Server Build server. This occurs when you don't have the resources to upgrade all servers at once.
Likelihood to Recommend
This is more suited for a larger corporation or development team as the cost of acquiring the software/hardware might be too large for a smaller company. Setting it up can also be hard for a small team if there is no experience with it. Finding experience can be hard because of this fact but the Team Foundation Server wizards are generally helpful and provide adequate help in setup and administration.
