Azure DevOps Services vs. Zenhub

ADO is well suited for the visibility of day-to-day tasks and responsibilities as well as things such as Features, user stories, etc. Off the top of my head, I can't think of any scenario where it might not be well suited, as you can customize ADO to your liking to a degree.

Zenhub is incredible for the below areas: Burndown Charts, Release Reports, Velocity Tracking, Control Points Charts, Cumulative Flow Diagrams And if there is a bottleneck in your workflow, ZenHub identifies it. The most important aspect is serving as a collaboration tool for areas that are impeding implementation projects. For example when working with non-standard ERPs and having to document ERP integrations this tool is very helpful

Incentivized

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

Incentivized

• ZenHub continually adds to its reporting suite-- that truly allows you to track forward motion and see what issues may be the cause of any delays.
• Both our technical and non-technical staff can understand and use the functionality.
• We like the flexibility of being able to provide labels to our stories that can be customized to the way our company does things--- such as knowing if an epic is part of a module or a stream.
• We also like the flexibility of the number and labeling of the pipelines--- again, very adaptable to our organization.
• The filtering is very useful--- with and/or conditions, and allows people on different projects, doing different functions, an easy way to view what is important to them.

Incentivized

• Need to make the changes so that it doesn't occupy most of the CPU utilization and memory
• Execution of Bulky SQl Queries leads to either the SQl being out of exception or the VS being unresponsive
• Integration with Microsoft products is easy, but with non-Microsoft products it is more difficult, and you have to make a lot of configuration changes to integrate
• With every upgrade of the Visual Studio, like from VS 2010 to VS 2013 , we need to upgrade our hardware/machine, as the VS hardware requirement also increases
• If code is getting compiled in one visual studio, like in VS 2010, that the same code could possibly give an error when compiled in VS 2013, due to certain changes in keyword, data format, etc., with the VS upgrade

Incentivized

• Sometimes, updates to a GitHub project can get lost if they're made through ZenHub. You do need to open the GitHub project occasionally, as you don't have exactly the same ability to modify issues and milestones from within ZenHub.
• It's great to be able to see your projects from within ZenHub, but sometimes you'll need to check in on the GitHub project itself, as well.
• I've run into some problems with updates getting lost on occasion. I think this happens when you do the update from within ZenHub instead of from GitHub itself. I also don't have quite as much control over my issues or milestones from within ZenHub.

Incentivized

I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.

Incentivized

Azure DevOps is a powerful, complex cloud application. As such there are a number of things it does great and something where there is room for improvement. One of those areas would be in usability. In my opinion it relies too much on search. There is no easy way to view all projects or to group them in a logical way. You need to search for everything.

Incentivized

Once it's up and running it's easy to use. It needs a little consideration to get set up perfectly for your own needs, but that is the same for any feature-rich software.

Incentivized

When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.

Incentivized

Support is good, but quite honestly, I haven't needed any support since 2015. As I remember, I was required to open a ticket and had to wait a few days for resolution. I give it a rating of 8 because of the lag in getting a solid resolution, but it was resolved adequately.

Incentivized

Was not part of the process.

Incentivized

Jira is fantastic for project management and customer facing portal. It is not good for pure development (no integration with Git, pipeline management, automated testing features). If DevOps were to integrate and adopt the project features of Jira as well as the customer facing interfaces, I feel it would be a complete project management system.

Incentivized

Way better than competition if you use github because it seamlessly integrates without doing anything. You don't need to duplicate your issues, etc. As long as your devs already use github and github issues this will be a no brainer and simple to implement. With JIRA or Trello we were doing everything twice, things got dropped, etc.

Incentivized

• Increased dev team efficiency through more streamlined development processes and task automation.
• Improved quality of software deployments due to better source control, automated testing, and release management options available in DevOps.
• Better collaboration between the dev team, business analysts, and agile project managers.

Incentivized

• We are now able to determine output potential from our development resources based on points assignment.
• We were able to successfully implement an Agile methodology in our department.
• We have been able to better track tasks.
• We have used the releases feature to group our task to business release expections and easily filter.

Incentivized