Azure DevOps Server vs. Teamwork.com

Azure DevOps is good to use if you are all-in on the Microsoft Azure stack. It's fully integrated across Azure so it is a point-and-click for most of what you will need to achieve. If you are new to Azure make sure you get some outside experience to help you otherwise it is very easy to overcomplicate things and go down the wrong track, or for you to manually create things that come out of the box.

Incentivized

Teamwork is awesome for teams who need a flexible tool that supports all types of projects. Since it supports kanban it makes visualizing the work to be done and the work in progress very easy. The Gantt chart support is decent and helps to understand how a team is doing when it comes to getting work done in a given time frame. Teamwork isn't a great option for companies that have a bunch of projects going simultaneously due to the way Teamwork structures their billing based on a number of active projects.

Incentivized

• Reporting Integration- Azure boards provides Kanban and other dashboard, their templates for easy management of project.
• Project Pipeline- easy integration and development of CI/CD pipelines, helped in testing, releasing project artifacts.
• Version Control- Integration with Git and code IDE made it easy to share, review our code, fix bugs and do testing.

Incentivized

• I am a believer that simple and easy should be the key to create great opportunities.
• Teamwork has helped me to turn simple task management into the execution of large, massive projects.
• It has certainly worked great in helping to maintain workflow in my department.

Incentivized

• Can add more build templates for specific technology requirements
• Can have more features in dashboards which can help dev teams stream line their tasks and priorities
• Can have raise alarm feature in case of any sort of failure in devops pipeline execution

Incentivized

• Visualization needs to be improved, charts graphs are limited
• Value stream mapping should be available to determine and prioritize the work.
• Documentation should be available stepwise with export and printable facility.
• It should be configurable like ERP with cross functionalities of different users, where users login, assign and approve the work, job or project details, where it should be collectively effected on a project.
• Add many examples, little more AI, Machine learning required for suggestion and recommendation. It would be a plus point

Incentivized

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

We are already at an annual contract, and have been for the past 5 years; so far the system has delivered, and our personal is already trained in it. A major overhaul of our entire infrastructure (as in moving everything to a single, unified platform) might change the current continuity of Teamwork Projects on our organization, but that's not feasible in the near future.

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 give it a 9 out of 10, because there is a bit of a learning curve when you first start using Teamwork Projects because there is a lot to learn & recognize where to find it. They do offer a good range of tools that can be applied to every project - So say you're working on an internal project and don't need Milestones or Billing, you can shut those modules off. This can help simplify the interface for beginners. Once you've had a few days in Teamwork Projects, I think it's a 10/10 usability. It's very easy to accomplish your tasks and keep track of what you're managing.

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

We've been able to meet with the customer success team on multiple occasions to discuss the roadmap and learn about the company culture. Being based in Ireland, we occasionally have to wait until they wake up to get support requests handled in the states and larger conversations about big enhancement requests were politely collected but not followed up on

Incentivized

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

Incentivized

In my opinion, DevOps covers the development process end to end way better than Jira or GitHub. Both competitors are nice in their specific fields but DevOps provides a more comprehensive package in my opinion. It is still crazy to see that the whole suite can be used for free. The productivity increase we realized with DevOps is worth real money!

Incentivized

I spoke about this quite a bit before, but as far as usability goes, Microsoft Projects is totally useless for me, so I avoid it at all costs. Basecamp was just a task management app and had very small feature set beyond that. We had to rig it to do other things for us, but it failed at that. Asana was a very nice app to trial, but it lacked many of the features that we were looking for.

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

• Teamwork was a great starter into project management software. We were WAY more organized and efficient than we ever were with Trello boards and the PM software included with our accounting system.
• Clients were mostly pleased with interacting with Teamwork, and appreciated the ability to track their comments and requests in one place.
• Ultimately, we stopped using Teamwork after about 6 months because we need something more focused on web development projects specifically

Incentivized