As informa??es desta p¨¢gina n?o est?o completamente dispon¨ªveis no seu idioma de escolha. Esperamos disponibiliza-las integralmente em outros idiomas em breve. Para ter acesso ¨¤s informa??es no idioma de sua prefer¨ºncia, fa?a o download do PDF ²¹±ç³Ü¨ª.
Atualizado em : Nov 10, 2015
N?O ENTROU NA EDI??O ATUAL
Este blip n?o est¨¢ na edi??o atual do Radar. Se esteve em uma das ¨²ltimas edi??es, ¨¦ prov¨¢vel que ainda seja relevante. Se o blip for mais antigo, pode n?o ser mais relevante e nossa avalia??o pode ser diferente hoje. Infelizmente, n?o conseguimos revisar continuamente todos os blips de edi??es anteriores do Radar.
Saiba mais
Nov 2015
Evite
In the last radar issue we advised against creating a separate DevOps team , as DevOps is about creating a culture of shared responsibility in delivery teams. We recommend embedding operations skills into delivery teams to reduce friction and deliver better outcomes. However where there is a need for significant investment in tooling and automation, we do see a role for a Delivery Engineering team. Rather than being a helpdesk, these teams build tooling and enable teams to deploy, monitor, and maintain their own production environments.
May 2015
Evite
Jan 2015
Evite
Jul 2014
Evite
Some companies with good intentions create a separate DevOps team, which misconstrues the definition of DevOps. Rather than a role, DevOps is a cultural movement encouraging collaboration between operations specialists and developers. Rather than create yet another silo and suffer the consequences of Conway's Law, we advise you to embed these skills into teams, improving feedback loops and communication pathways by removing friction.
Publicado : Jul 08, 2014
