Azure DevOps Server (formerly TMS) Formerly Team Foundation Server vs Trello

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

Read full review

• Easy color categorization of the "Cards" (which can represent anything from projects to tasks)
• Ease of use overall - you can divide work into columns and move it from column to column depending on status
• You can create multiple boards, which are spaces to store tasks (for different work contexts, or even private boards)
• You can easily share boards with another person
• You can easily assign tasks (Cards) to persons
• You can store information in cards, like files and short format text

Read full review

• 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

Read full review

• Swim Lanes - they are nonexistent. There is a third-party tool to add them but it's buggy as all get out
• View - I am not sure how to do it but I really wish I didn't have to pick between viewing all cards with no detail or one with all detail. Maybe the ability to collapse and expand?
• Integrations - It would be amazing if I could easily pop action items from Gmail over to Trello, but right now I can only copy text or upload screenshot attachments.

Read full review

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

Read full review

• The more time I put into developing our Trello systems, the more ROI we seem to get. We have to re-evaulate for each unique project, but it typically pays off.
• We managed post-production for 3 seasons of TV on Trello - breaking each scene down into cards and a list being an episode. Once the organization was done, this saved massive amounts of time for my post-manager as he was able to direct new editors to the board and very easily explain how to jump in the mix and get started. We managed to accomplish a massive amount of work with a small team with a very simple project management system.
• Trello has been difficult to implement in a broad-strokes sort-of way. For example - when onboarding a new project/client, we have to stop and think about how a given board needs to be set up, who needs to have permission to it, and where and how the information will be shared. We had to remove almost all conversation from Trello cards and move them to slack channels in order to keep up with all the conversation as it became far too convoluted. It's not as pre-defined or process-oriented as a basecamp, which doesn't always hurt, but it does often require more time to get started on a project.

Read full review