Overall Satisfaction with Azure DevOps Server (formerly Team Foundation Server)
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.
- Extensive and very powerful Pipelines
- Customizable backlog management (capable of following SAFe natively)
- Comprehensive customizable reporting
- End to end released artifacts tracing (audit friendly)
- We were able to retire tools in the Repo Mgmt, Pipeline Mgmt and Backlog Mgmt space
- Unified approach to SDLC leads to accumulated internal knowledge and proficiency
- Vibrant ecosystem of extensions available which speed up process improvements
Azure DevOps has a
- backlog module which is a substitute for Jira / Trello
- pipeline module which is a substitute for Jenkins / TeamCity
- artifact management module which is a substitute for Artifactory
- test case management module unmatched by the above
- dashboards and reporting module unmatched by the above
Do you think Azure DevOps Server delivers good value for the price?
Are you happy with Azure DevOps Server's feature set?
Did Azure DevOps Server live up to sales and marketing promises?
Did implementation of Azure DevOps Server go as expected?
Would you buy Azure DevOps Server again?
- 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