This is a Leanpub book. Leanpub empowers authors and publishers with the Lean Publishing process. Lean Publishing is the act of publishing an in-progress ebook using lightweight tools and many iterations to get reader feedback, pivot until you have the right book and build traction once you do.
Conflux Books
Books for technologists by technologists
Our books help to accelerate and deepen your learning in the field of software systems. We focus on subjects that dont go out of date: fundamental software principles & practices, team interactions, and technology-independent skills.
Current and planned titles in the Conflux Books series include:
- Build Quality In edited by Steve Smith and Matthew Skelton (B01)
- Better Whiteboard Sketches by Matthew Skelton (B02)
- Internal Tech Conferences by Victoria Morgan-Smith and Matthew Skelton (B03)
- Technical Writing for Blogs and Articles by Matthew Skelton (B04)
Find out more about the Conflux Books series by visiting: confluxbooks.com
Acknowledgements
We would like to thank the following people for their help and involvement in the writing of this book: Calum Loudon at Metaswitch; Rik Still and Mark Barnes at FT; Andrew Betts at EdgeConf for his experience and advice on running panel discussions; Thurston Tye & Michael Huniewicz at FT (photography); James Hamill and Ben Morgan-Smith for editorial assistance; Ben Maraney, Case Taintor, Kim Oberg, and Matthias Feist at Klarna; Rich Haigh (formerly of Paddy Power Betfair); the PIPELINE Conference team (Amy Phillips, Anthony Green, Beccy Stafford, Chris ODell, Inka Howorth, and Steve Smith).
Wed like to extend special thanks to Manuel Pais for editing the original InfoQ article Internal Tech Conferences in 2016 and including it in the 2017 InfoQ eMag Scaling DevOps.
We also give a big thank you to our reviewers: Ben Maraney, David Legge, Emily Webber, Mark Dalgarno, Portia Tung.
Some icons are made by made by Freepik from www.flaticon.com - icons used in accordance with the Flaticon license terms
Introduction
Internal tech conferences can make a significant impact on anorganisations level of sharing, learning, and communication byaccelerating multi-team learning across technology departments. Anincreasing number of enlightened organisations are using this powerfulapproach to spread and embed new ideas and practices.
In this book we share practical advice on how to prepare, run, andfollow-up on an internal tech conference, together with some casestudies from several organisations showing the approaches in common andthe adaptations for each situation.
How to use this book
This book is for people involved in technology leadership in some form:people in official positions of leadership (CIO, CTO, Head ofEngineering, IT Operations Manager, etc.) and those in more informaltechnology leadership positions, such as team leaders, senior engineers,and people who simply like to lead by example. Having been in suchpositions ourselves, we (Victoria and Matthew) want to help othertechnology leaders to devise and run successful internal techconferences to act as a key strategic differentiator for organisationsbuilding software systems.
- gives an overview of internal tech conferences and why you might want to run such an event. Read this chapter if you have never run or experienced an internal tech conference before to help you understand the purpose and the things involved.
- explains how to prepare for an internal tech conference. Read this to understand what is involved, how long the preparation takes, and what kind of team you will need to make the conference happen.
- covers the conference day itself. Read this chapter to understand all the operational aspects of the conference and to see what kind of help you may need on the day.
- deals with the weeks and months following the conference. Read this chapter to see how to get the most out of the day by following up on talks and panel sessions and how to ensure that the conferences are an opportunity for learning and growth.
- contains detailed case studies from a selected group of organisations. This chapter is different from the others in that the material is presented in a more linear, retrospective fashion (more like a story). Read this chapter to get a feel for how real organisations have run internal tech conferences and what they learned.
- The at the back of the book contains tools and templates for planning and running an internal tech conference; these can be used and adapted as needed.
Chapters 1 to 4 deliberately read as how-to guides with quite specificrecommendations. Chapter 5 has a more narrative flavour, befitting thecase study stories. The Toolkit provides some templates and quick-start guides for getting results quickly.
Why we wrote this book
We met (appropriately) at a conference in 2015 where Victoria gave atalk about some early changes at Financial TImes to create a learningorganisation. We realised that we both had some similar experience oforganising and running internal tech conferences and decided to write anarticle, published by InfoQ in 2016 .
Since the article was published, we have been happy to see several newonline articles covering internal tech conferences, and we know fromspeaking to people in the industry (at least in the UK) that theapproach is becoming more widespread. We therefore decided to write thisbook to provide a template and set of guidelines for not just runningthe conference itself but how to go about preparing for one and how toget the most strategic and tactical value out of a series ofconferences.
About the authors