Azure DevOps Server vs. AgileBox by DevSamurai

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

Incentivized

Well suited:

• Estimation of user stories in agile team.
• Recording the estimations and events directly to JIRA.
• Estimations can be done without leaving JIRA.
• Best suitable in this pandemic situation as most of the people are working remotely.
• Different estimation scales are present to adapt as per the team norms for example Fibonacci, T-shirt sizing and custom estimations as well.

Scenarios where it is less suitable:

• Where only inbuilt chat box from DevSamurai is used. So synchronization is an issue there.
• And apart from that a consistent internet connectivity is required.

• Vast range of Template for Automated Build and Release Pipeline with option to have conditional triggers
• Code repository mechanism is aligned with GIT which is a well known public repository system
• Bug Management is also an integral feature of this tool
• Dashboard creation option of Build and Release pipeline is also available

Incentivized

• Usefull interface.
• Don't need any training for using guide.
• Challenging.

Incentivized

• Searching through code can be somewhat cumbersome. It would be nice if there was a way to do general searches in certain areas of the system.
• Without proper training, the system can be confusing to navigate. This issue can be prevented with good training but it is something to be aware of.
• Navigation can be clunky at times depending on where you are in the system. For power users, this is not a huge deal but it is a tad bit annoying.

Incentivized

• Live chat box feature need to be improvised as it still not robust.
• Integration module should be flexible enough to stick with other workflow tools.

Because we are a Microsoft Gold Partner we utilize most of their software and we have so much invested in Team Foundation Server now it would take a catastrophic amount of time and resources to switch to a different product.

Incentivized

For standard users the interface is friendly. but if you are a manager some tools are a little confusing to use, like the query system that you always need to create from scratch. Templates should be more helpful for queries and for standard procedures that you need to duplicate PBIs over time. The search history of Work Items is a little painful to use.

Incentivized

I have not had to use the support for Azure DevOps Server. There have never been any issues where I was not able to figure it out or quickly resolve. Our Scrum Master has used support before though, and the service has always been prompt and clear with a customer-focus

Incentivized

Do research beforehand and, if possible, do a trial run before implementing into production environment.

Incentivized

Azure DevOps is a fully integrated solution that solves all of the problems that our separate tools did in a much easier-to-use way. Before we implemented DevOps we had three different solutions that we had to integrate with each other and required a lot of manual intervention to make sure they worked correctly.

Incentivized

The only application we use in planning poker studies in the organization.

Incentivized

• It has streamlined the pipeline and project management for our agile effort.
• It has helped our agile team get organized since that is a new methodology being leveraged within the Enterprise.
• The calendar has improved visibility into different OOOs across the project team since we all come from different departments across the larger organization.

Incentivized

• Estimation of user stories and updating the JIRA is automated and hence resulted in reduced efforts in poker planning.
• No need to be present under same roof for estimation, and hence a flexibility which is much required in this scenario.
• Clients can have a clear and better picture of estimation at any time with all statistics and hence customer sees more transparency.