On 18th December 2013 I presented at DevOps Summit in Bangalore (organised by Unicom Learning Pvt), speaking about the improvements in software operability which DevOps can bring:
One of the goals of DevOps is to make software systems work better in Production, and this characteristic of ‘working well in Production’ is known as operability. Here are the slides I used (available from http://www.slideshare.net/matthewskelton/software-operability-and-run-book-collaboration-29511196):
I presented at DevOps Summit, Amsterdam on 14th November 2013 on Software Operability and Run Book Collaboration, and facilitated some of the sessions. Here are the slides from my talk, and the closing Q&A slides:
I recently presented a webinar on What Does DevOps Culture Feel Like? in which I attempted to characterise what it feels like to work within a DevOps culture (part of the Experience DevOps workshop series).
Update (2022): my company Conflux now offers consulting and training around DevOps topologies and related practices like Team Topologies.
Update (2019): I have co-authored a book – Team Topologies – that adds brand new material to these (original) DevOps Topologies patterns. In the book we cover dynamic organization evolution, team interaction patterns, the strategic use of Conway’s Law, monolith decomposition, and many more topics.
See teamtopologies.com and follow us on Twitter at @TeamTopologies for updates. The book is published by IT Revolution Press (Sept 2019).
Update (2016): A new version of these DevOps team topologies is now here: devopstopologies.com
The new version has many new topologies that we’ve encountered in the wild and we’re taking pull requests on Github for additions and changes.
The primary goal of any DevOps setup within an organisation is to improve the delivery of value for customers and the business, not in itself to reduce costs, increase automation, or drive everything from configuration management; this means that different organisations might need different team structures in order for effective Dev and Ops collaboration to take place.
So what team structure is right for DevOps to flourish? Clearly, there is no magic conformation or team topology which will suit every organisation. However, it is useful to characterise a small number of different models for team structures, some of which suit certain organisations better than others. By exploring the strengths and weaknesses of these team structures (or ‘topologies’), we can identify the team structure which might work best for DevOps practices in our own organisations, taking into account Conway’s Law.
Continue reading What Team Structure is Right for DevOps to Flourish?
The run book (or system operation manual) is traditionally written by the IT operations (Ops) team after software development is considered complete. However, this typically leads to operability problems being discovered with the software, operational concerns having been ignored, forgotten, or not fully addressed by the development (Dev) team. If the software development team writes a draft run book or draft operation manual, many of the operational problems typically found during pre-live system readiness testing can be caught and corrected much earlier. Because the development team needs to collaborate with the operations team in order to define and complete the various draft run book details, the operations team also gains early insight into the new software. Channels of communication, trust, and collaboration are established between the traditionally siloed Dev and Ops teams, which can help to establish and strengthen a DevOps approach to building and running software systems.
I…
View original post 1,295 more words
Matthew Skelton 