Azure DevOps Server (formerly TMS) vs Digital.ai Agility (formerly VersionOne)

• The consolidation of issues is extremely useful for us. Having one place where all bugs are entered has helped our business process immensely.
• Being able to query data regarding user stories, bugs and code is extremely helpful. As well, using the visual tools built into the system can help with messaging regarding the status of a project.
• Being able to monitor code deployments is extremely helpful. Since we are managing multiple environments, this tool makes it easy to see what is happening where.

Read full review

• Automated saving of changes, no records can be lost because all items are saved in real-time.
• The watch function, optional but beneficial when managing multiple teams or projects.

Read full review

• 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.

Read full review

• Saving of changes is inconsistent. Sometimes the changes appear to save automatically and other times the user needs to click the "Apply" button. Until the user is familiar with when this needs to happen, work can easily be lost.
• This may be a setup configuration issue, but it would be good to be able to set the default team when creating stories. Too often stories are created and the user forgets to enter the team and they need to search the entire database for the story that was just created.

Read full review

• Time to completion for projects has significantly gone down by 15% and that number changes as more people are trained and are comfortable with TFS.
• Change Management and Approvals are easier to access.
• More projects are implementing SCRUM methodologies for applications

Read full review

• I came in near the end of our use of VersionOne (we are migrating to Jira), and I don't operate or think at the business return (ROI) level. I'm not the one to comment on this!
• I suspect that V1 added much clarity to the prioritization of work, and added visibility across entire teams. So I assume that it had a positive impact on returns.

Read full review