“We need to enable a culture of safety for experimentation”
Instead of a very simplistic approach, we need to look for collaboration and interaction patterns that work in different contexts. Collaboration comes with a cost but it produces very good results. However, sometimes it’s better to deliberately introduce a kind of boundary between teams. JAXenter editor Hartmut Schlosser talked to Matthew Skelton at DevOpsCon 2016 about the need for collaboration and what goes into good team structures.
Matthew Skelton has been building, deploying, and operating commercial software systems since 1998. Co-founder and Principal Consultant at Skelton Thatcher Consulting (http://skeltonthatcher.com/), he specialises in helping organisations to adopt and sustain good practices for building and operating software systems: Continuous Delivery, DevOps, aspects of ITIL, and software operability. Matthew curates the well-known DevOps team topologies patterns at http://devopstopologies.com/ and is co-author of the books Database Lifecycle Management (Redgate) and Continuous Delivery with Windows and .NET (O’Reilly). He has qualifications in Cybernetics, Neuroscience, and Music, and is a Chartered Engineer (CEng).