Azure DevOps Services vs Chef Infra

• 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

• Chef is great at deploying code to both small and large groups of servers.
• We use chef to standup new servers as well as deploy updated code to existing servers and it does this very well.
• Being able to make a change and have it push manually or automatically to any subset of servers has changed the landscape of how our IT teams operate.

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

• Chef could do a better job with integration with other DevOps tools. Our company relies on Jenkins and Ansible, which took some development and convincing for plug-ins to be created/available.
• It would be nice if kitchen didn't only have a vagrant/virtual-box prerequisite. Our company one day stop allowing virtual-box to run without special privileges, and that caused a lot of issues for people trying to do kitchen tests.
• Chef could use more practice materials for the advanced certification badges. There was not a lot of guidance in what to study or examples of certain topics.

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

• Chef is a good tool for baselining servers. It will be a good ROI when there are huge number of servers. For less number of servers maintaining a master will be an over head.
• One good ROI will be that the Operations Team also gets into agile and DevOps methodologies. Operational teams can start writing scripts/automations to keep their infra more stable and their application stack more reliable.
• Implementation of Chef eliminates the manual mode of doing things and everyone aligns to automation mind set. It helps in change of culture.

Read full review