Matthew Skelton

OK
About Matthew Skelton
Matthew Skelton is co-author of Team Topologies: organizing business and technology teams for fast flow. Head of Consulting at Conflux (confluxdigital.net), he specialises in Continuous Delivery, operability and organisation dynamics for software in manufacturing, ecommerce, and online services, including cloud, IoT, and embedded software.
Recognised by TechBeacon in 2018, 2019, and 2020 as one of the top 100 people to follow in DevOps, Matthew curates the well-known DevOps topologies patterns at devopstopologies.com and is co-author of the books Continuous Delivery with Windows and .NET (O’Reilly, 2016) and Team Guide to Software Operability (Skelton Thatcher Publications, 2016), along with several key reports on SRE. He is also founder at Conflux Books which publishes books for technologists by technologists.
confluxdigital.net / @matthewpskelton
Customers Also Bought Items By
Are you an author?
Author Updates
-
-
-
Blog postI’ve been using deployment pipelines since 2011 starting with GoCD and then other tools. A few months ago, I joined DevOps experts Helen Beal of Ranger4, and Sam Fell & Anders Wallgren of Electric Cloud to discuss deployment pipelines for modern software delivery as part of the Continuous Discussions (#c9d9) series (episode 88).
(YouTube video segments below)
Key takeaways: The concept of the deployment pipeline was defined and popularised by the 2010 book Continuous Delivery2 years ago Read more -
Blog postRound-table discussions can be a really useful way to discover and share direct experience with peers and colleagues. A good round-table discussion is quietly facilitated by someone who knows the subject matter enough to include interesting questions and can ensure that everyone has a voice. Here is what I have learnt from facilitating round-table discussions … Continue reading Tips for facilitating round-table discussions3 years ago Read more
-
Blog postI founded and helped to run the first PIPELINE Conference in 2014 and I have been part of the team that has run 5 of these events to date. Here are my thoughts on how to run a good tech conference based on my experience with PIPELINE and with other events I have attended and spoken at.
tl;dr: fabulous team + great attendee experience.
PIPELINE Conference team – photo by Fabienne Jung Discover how to run a successful internal tech conference.
Buy the book!
4 years ago Read more -
Blog postI have been helping to promote greater diversity in tech conferences and tech meetups since 2012. Here is my thinking on how to promote diversity in tech events and why I think diversity is important.
Update: please first read this post from Trisha Gee: What Can Conferences Do To Attract More Women Speakers? and then this post by Jez Humble on How To Create A More Diverse Tech Conference. Trisha and Jez make many excellent points; in this post I try to offer some additional4 years ago Read more -
Blog postKey points:
Set up the organisation to ‘sense’ its environment Treat internal teams (almost) as external providers Conway’s Law should shape our organisation design Promise Theory is a useful approach to organisational agility I have been doing quite a bit of work recently with various organisations to help them develop new capabilities for building and evolving software-rich services. Part of this work involves thinking about the responsibilities of different teams and how these evol5 years ago Read more -
Blog postSummary: many people confuse continuous deployment (pushing changes to live systems many times per day) with Continuous Delivery (reliable software releases through build, test, and deployment automation). Here is why I think that Continuous Delivery is the more fundamental practice. (Update 1, 2017-11-02: clarified ‘continuous deployment’ and the on-premises context) I work with many organisations … Continue reading Continuous Deployment is a niche practice; Continuous Delivery is more fun5 years ago Read more
-
Blog postThis is part 4 of a 4-part series of articles based on discussions at the LondonCD meetup group on 12 June 2017. The other posts are linked at the end of this article.
Our 4th Open Space discussion challenged people to identify the things that they don’t like about the Continuous Delivery book: things that don’t work in practice, things that are plain wrong, etc. – a slightly cheeky session!
tl;dr: Jez Humble and Dave Farley – authors of Continuous Delivery – did not get anyth5 years ago Read more -
Blog postThis is part 3 of a 4-part series of articles based on discussions at the LondonCD meetup group on 12 June 2017. The other posts are linked at the end of this article.
Applying the principles and practices of Continuous Delivery for new software is fairly straightforward (at least, until you deal with data and databases). However, existing “legacy” systems that were built without many automated tests and without much concern for repeatable deployments of discrete functionality pose a5 years ago Read more -
Blog postThis is part 2 of a 4-part series of articles based on discussions at the LondonCD meetup group on 12 June 2017. The other posts are linked at the end of this article.
Continuous Delivery for web applications is (in 2017) largely a solved problem but where data and databases are concerned, Continuous Delivery becomes more difficult (I have written quite a bit about Continuous Delivery and Databases on the Redgate Simple Talk website – worth a read if you’re interested). In the meetup,5 years ago Read more -
Blog postThis is part 1 of a 4-part series of articles based on discussions at the LondonCD meetup group on 12 June 2017. The other posts are linked at the end of this article.
How do we continuously address security concerns with modern software development? That was one of the questions we discussed and tried to answer at LondonCD meetup group on 12 June 2017. “The yearly PEN test is dead!”, said one person, meaning that reliance on an infrequent, specialist test to address all security prob5 years ago Read more
Titles By Matthew Skelton
Team Topologies will help readers discover:
• Team patterns used by successful organizations.
• Common team patterns to avoid with modern software systems.
• When and why to use different team patterns
• How to evolve teams effectively.
• How to split software and align to teams.