Azure DevOps Services vs SpiraPlan

• Flexible Requirements Hierarchy Management: AZDO makes it easy to track items such as features or epics as a flat list, or as a hierarchy in which you can track the parent-child relationship.
• Fast Data Entry: AZDO was designed to facilitate quick data entry to capture work items quickly, while still enabling detailed capture of acceptance criteria and item properties.
• Excel Integration: AZDO stands out for its integration with MS Excel, which enables quick updates for bulk items.

Read full review

• Flexible requirements organisation structure. I'm able to group and sub-group requirements as I see fit.
• Competitive product pricing. Paying by active use instead of registered user was the winning point.
• UI is straightforward and easy to use.

Read full review

• Column sorting when in filtered states.
• A way to show cross-team dependencies.
• A customized "From" field for notifications. Sometimes when a mail comes from Azure DevOps the teams do not realize that I am sending it
• A way to do online poker that doesn't require a plug-in.

Read full review

• Access from South East Asia is rather sluggish. Could be due to server location.
• Complimentary phone app to do simple tasks (e.g. create tasks, create requirements, add comments) offline would be beneficial because access to the internet can be an issue at the customer's environment.

Read full review

• When I first VSTS it was with a team of developers who always work on their own. This project was the first one at the company that used six developers all work on the same product at the same time. Integrating someone else code into the system was an unknown entity. VSTS really helped move this new collaboration forward. The staff who were on this team then moved on work together on other teams because they knew how to handle this type of work.
• The learning curve on VSTS is quite large so make sure you have some of your best starting anew VSTS project. They will fail a few times but after a few mistakes they will get how to do things and your build, tests and deployments will all be automated.
• The user integration into VSTS is very good. As long as you developers can use Team Foundation Server source control, either Microsoft's or git, then they already have the permission to have VSTS access source control. This is very good.

Read full review

• Allows us to manage simple IT requirements without major upfront costs. Allows us to expand our process complexity at our own pace.
• Slow UI response from a South East Asia country can make data entry a drag.

Read full review