Boost cross team learning and engagement with internal tech conferences

•

0 j'aime•340 vues

Internal tech conferences can make a significant impact on an organisation's level of sharing, learning, and communication by accelerating multi-team learning across technology departments. An increasing number of enlightened organisations are using this powerful approach to spread and embed new ideas and practices. In this talk, the authors of the book Internal Tech Conferences - Victoria Morgan-Smith and Matthew Skelton - share practical advice on how to prepare, run, and follow-up on an internal tech conference, together with some case studies from several organisations showing the approaches in common and the adaptations for each situation. What makes a good internal tech conference? What are the key success factors? What things should be avoided? And what works best for online conferences versus in-person conferences? Find out in this talk from the people who have literally written the book on internal tech conferences! Key Takeaways - What makes a good internal tech conference? - What are the key success factors? - What things should be avoided? - And what works best for online conferences versus in-person conferences? Audience Anyone involved in creating and sustaining a learning culture within the technology division: - Team Leads - Architect - Team Manager - Project Manager - HR - L&D - Head of Department - CTO/CIO

Technologie

Boost cross-team learning
and engagement with
Internal Tech Conferences
Victoria Morgan-Smith and Matthew Skelton
Authors of Internal Tech Conferences
InternalTechConf.com | @IntTechConf

What we’ll cover in this talk
What makes a good internal tech conference?
What are the key success factors?
What things should be avoided?
What works best for online conferences
versus in-person conferences?
2

Who we are
Victoria Morgan-Smith
Director of Delivery,
Internal Products at
Financial Times
@Victoria_JMS
3
Matthew Skelton
Director and Head of
Consulting at Conﬂux
@matthewpskelton

Introducing:
Squiggle
Victoria’s new co-worker
😻
4

“An internal tech conference is a
technology conference run by and for
the staﬀ of a single organisation.”
6
Internal Tech Conferences, p.2

“...a shared celebration and
examination of the current practices
and approaches within the
organisation, accelerating learning at
a time of rapid technological change.”
8
Internal Tech Conferences, p.2

11
Photo by Daniele Levis Pelusi on Unsplash
Remote-ﬁrst

What makes a good
internal tech
conference?
19

What are the key
success factors for
an internal tech
conference?
31

56
DON’T:
leave speaker
selection too late

Online vs in-person
conferences - what
is diﬀerent?
60

73
LEVEL UP WEEK 2020: HOW
WE EVOLVED OUR INTERNAL
TECH CONFERENCE FOR A
REMOTE-FIRST WORLD
https://leadingagileteams.com/2020/12/15/level-up-week-2020-how-
we-evolved-our-internal-tech-conference-for-a-remote-ﬁrst-world/

74
Key learning from Red Gate:
1. We could deliver the conference content at a more sustainable pace
2. We could open the event up for our global Redgaters
3. We could record everything to allow people to catch-up at a time that
works best for them
4. We could provide something to suit a wider variety of learning styles
5. We could bring Redgaters together at a time when we really needed it
https://leadingagileteams.com/2020/12/15/level-up-week-2020-how-we-evolved-our-internal-tech-conference-for-a-remote-ﬁrst-world/

Buy the book!
Amazon / Bookshop.org /
BookDepository / Leanpub
and more ...
InternalTechConf.com
82

25% discount
for this WTFinar via
Leanpub!
https://leanpub.com/InternalTechConferences/
c/WTFinar25
83

Training:
4-hour live online / self-paced video
InternalTechConf.com
84

Praise for the book
“Running an internal tech conference has made a big
contribution to changes in culture and approach at
the Financial Times. ... if you want a practical guide to
how to do something similar in your organisation, this
book is for you!”
-- Sarah Wells, Technical Director for Operations and Reliability,
Financial Times
“... Victoria and Matthew’s book provides valuable,
practical guidance that will help you plan, run and
capitalise on your own brilliant conference”
-- Chris Smith, Head of Product Delivery, Redgate Software
86

Thank you!
InternalTechConf.com | @IntTechConf
Victoria Morgan-Smith and Matthew Skelton
88

Contenu connexe

Plus de Matthew Skelton

Savvy organisations are discovering the value of treating their internal platforms as products. But what does it mean to treat a “platform as a product”? What benefits does this give, and why would an organisation adopt this approach? In this talk, [Matthew Skelton] [Manuel Pais], co-author of the book Team Topologies, explains why the platform-as-product approach can be a game-changer for organisations building and running software-enabled products and services. Using ideas & patterns from Team Topologies - including Thinnest Viable Platform, team cognitive load, and the evolutionary team interaction modes - [Matthew] [Manuel] explains how organisations like adidas and Uswitch have successfully used the platform-as-product model to accelerate and simplify the delivery of software at scale.

What is platform as a product? Clues from Team Topologies - Puppetize 2020 - ...

Matthew Skelton

From a talk at Iris Software Group in September 2020 We know that team-based software delivery can be very effective but how can we promote and enable team-based approaches for organisations that are fully remote? What should teams think about and what patterns can teams adopt to be effective when no-one is in the office? Based on the ideas from the book Team Topologies, authors Manuel Pais and Matthew Skelton will present some useful approaches to clarify and evolve inter-team interactions and communication in this remote-first world.

Remote first team interactions with Team Topologies - Iris Software Group - 2...

Matthew Skelton

A talk given at DevOps Enterprise Summit Virtual 2020 --- Since the book Team Topologies was published in 2019, organizations around the world have started to adopt Team Topologies principles and practices like Stream-aligned teams, modern platforms, well-defined team interactions, and team cognitive load as a key driver for fast software delivery and operations. We will look at examples from these organizations: * Gjensidige Insurance, a leading Nordic insurance company with 4000 employees and business in the Nordic and Baltic countries, uses the four fundamental team types to clarify team responsibilities and interactions and is moving towards several “thinnest viable platforms” with Stream-aligned teams as internal customers * PureGym is Britain’s largest gym chain - the first to gain over 1 million members. As PureGym expanded, so did the need for software to enable their members to book and manage gym sessions. Since 2019, PureGym has re-aligned its teams and team interactions based on Team Topologies patterns, helping to scale the engineering teams and improve flow. * uSwitch / RVU, one of the UK’s leading consumer price comparison websites, has grown a modern platform from scratch, allowing stream-aligned teams to focus on consumers needs, offloading infrastructure provisioning concerns to the platform which also provides cross-cutting services around scalability, security and data management * Visma is one of the leading software development companies in Europe with nearly 1 million customers in 21 countries. Team Topologies has helped to define and accelerate a transformation begun in 2015 to improve service ownership and speed of changes. * Wealth Wizards is a UK company making financial advice affordable and accessible to everyone through online tools and apps. The engineering division at Wealth Wizards has used the Team Topologies ideas around team cognitive load to help right-size their teams and align teams to the most important flows of business change. For each of these examples, we explore how the ideas and patterns in Team Topologies were useful to the organization and the results of the changes.

Team Topologies in action - early results from industry - DOES London Virtual...

Matthew Skelton

Who designs the architecture of your software systems? Conway's Law suggests that HR may be strongly shaping software architecture by deciding how teams are composed and interrelate. Do you want HR designing your software architecture? Organization architecture and software system architecture need to be co-designed to avoid friction from Conway's Law. --- From a talk given by Matthew Skelton at Elabor8- 2020-05-27

Accidental Architects - how HR designs software systems - Team Topologies - e...

Matthew Skelton

From an online meetup at SEAM with Matthew Skelton and Manuel Pais Remote-first work is the "new normal" for companies around the world. There is no shortage of advice on how individual teams can bond and work effectively remotely. However, there is not much on how to address remote interactions between different teams that need to collaborate remotely, as part of the same value stream. Moving from the physical to the online world can further expose pre-existing interaction problems, increase wait times and slow down delivery and possibly response to incidents. Based on the ideas from Team Topologies, Manuel Pais will present some useful approaches to clarify and evolve inter-team interactions and communication in this remote-first world. Designing Team APIs and virtual communication channels that promote relevant team interactions while minimizing communication overhead will help modern organizations keep a fast flow of delivery once they're past the initial adaptation to teleworking. Following well-defined interaction patterns and architecting for team-first software boundaries will also help reduce communication overhead, clarify expectations on teams, and increase visibility of on-going work and support.

Remote-first team interactions with Team Topologies - SEAM - 2020-05-13

Matthew Skelton

From a meetup run by Agile Yorkshire on 30 April 2020. Remote-first work is the "new normal" for companies around the world. There is no shortage of advice on how individual teams can bond and work effectively remotely. However, there is not much on how to address remote interactions between different teams that need to collaborate remotely, as part of the same value stream. Moving from the physical to the online world can further expose pre-existing interaction problems, increase wait times and slow down delivery and possibly response to incidents. Based on the ideas from Team Topologies, Manuel Pais and Matthew Skelton will present some useful approaches to clarify and evolve inter-team interactions and communication in this remote-first world. Designing Team APIs and virtual communication channels that promote relevant team interactions while minimizing communication overhead will help modern organizations keep a fast flow of delivery once they're past the initial adaptation to teleworking. Following well-defined interaction patterns and architecting for team-first software boundaries will also help reduce communication overhead, clarify expectations on teams, and increase visibility of on-going work and support.

Remote-first team interactions with Team Topologies - Agile Yorkshire - 2020-...

Matthew Skelton

From a webinar run by IT Revolution Press on 29 April 2020. Remote-first work is the "new normal" for companies around the world. There is no shortage of advice on how individual teams can bond and work effectively remotely. However, there is not much on how to address remote interactions between different teams that need to collaborate remotely, as part of the same value stream. Moving from the physical to the online world can further expose pre-existing interaction problems, increase wait times and slow down delivery and possibly response to incidents. Based on the ideas from Team Topologies, Manuel Pais and Matthew Skelton will present some useful approaches to clarify and evolve inter-team interactions and communication in this remote-first world. Designing Team APIs and virtual communication channels that promote relevant team interactions while minimizing communication overhead will help modern organizations keep a fast flow of delivery once they're past the initial adaptation to teleworking. Following well-defined interaction patterns and architecting for team-first software boundaries will also help reduce communication overhead, clarify expectations on teams, and increase visibility of on-going work and support.

Remote first team interactions with Team Topologies - IT Revolution webinar -...

Matthew Skelton

Remote-first work is the "new normal" for companies around the world. There is no shortage of advice on how individual teams can bond and work effectively remotely. However, there is not much on how to address remote interactions between different teams that need to collaborate remotely, as part of the same value stream. Moving from the physical to the online world can further expose pre-existing interaction problems, increase wait times and slow down delivery and possibly response to incidents. Based on the ideas from Team Topologies, Manuel Pais and Matthew Skelton will present some useful approaches to clarify and evolve inter-team interactions and communication in this remote-first world. Designing Team APIs and virtual communication channels that promote relevant team interactions while minimizing communication overhead will help modern organizations keep a fast flow of delivery once they're past the initial adaptation to teleworking. Following well-defined interaction patterns and architecting for team-first software boundaries will also help reduce communication overhead, clarify expectations on teams, and increase visibility of on-going work and support.

Remote-first team interactions with Team Topologies

Matthew Skelton

The “monoliths vs microservices” debate often focuses on technological aspects, ignoring strategy and team dynamics. Instead of technology, smart-thinking organizations are beginning with team cognitive load as the guiding principle for modern software. In this talk we explain how and why, based on material from the book Team Topologies by Matthew Skelton and Manuel Pais. From a talk at Dept Manchester sponsored by Commercetools https://www.deptagency.com/en-gb/event/architecting-the-modern-digital-experience/

Forget monoliths vs microservices - focus on Team Cognitive Load - Team Topol...

Matthew Skelton

How to break apart a monolithic system safely without destroying your team - ...

Matthew Skelton

From a talk at OIO15 The way in which many (most?) software teams use logging needs a re-think as we move into a world of microservices and remote sensors. Instead of using logging merely to dump out stack traces, our logs become a continuous trace of application state, with unique-enough identifiers for every interesting point of execution. We also use transaction identifiers to trace calls across components, services, and queues, so that we can reconstruct distributed calls after the fact. Logging becomes a rich source of insight for developers and operations people alike, as we 'listen to the logs' and tighten feedback cycles to improve our software systems.

Un-broken logging - the foundation of software operability - Operability.io -...

Matthew Skelton

Forget monoliths vs microservices - focus on team cognitive load - Team Topol...

Matthew Skelton

Who designs the architecture of your software systems? Conway's Law suggests that HR may be strongly shaping software architecture by deciding how teams are composed and interrelate. Do you want HR designing your software architecture? Organization architecture and software system architecture need to be co-designed to avid friction from Conway's Law. --- From a talk given by Matthew Skelton at NAV, Oslo - 2020-01-23

Accidental Architects - how HR designs software systems - Team Topologies - N...

Matthew Skelton

A talk given at Oslo Software Architecture meetup https://www.meetup.com/Oslo-Software-Architecture/events/267904102/ For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes. This talk will cover the basics of organization design using Team Topologies, exploring a selection of key team types and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on the forthcoming 2019 book Team Topologies and first-hand experience helping companies around the world with the design of their technology teams.

Beyond the Spotify model - Team Topologies - OSWA Oslo - 2020-01-22 - Matthew...

Matthew Skelton

Monoliths vs microservices is missing the point - start with team cognitive l...

Matthew Skelton

Key takeaways: Why using the “Spotify Model” of team design is not enough The four fundamental team topologies needed for modern software delivery The three team interaction modes that enable fast flow and rapid learning How to address Conway’s Law, cognitive load, and team evolution with Team Topologies For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes. This talk will cover the basics of organization design using Team Topologies, exploring a selection of key team types and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on the forthcoming 2019 book Team Topologies and first-hand experience helping companies around the world with the design of their technology teams. About Team Topologies Team Topologies is a clear, easy-to-follow approach to modern software delivery with an emphasis on optimizing team interactions for flow. Four fundamental types of team – team topologies – and three core team interaction modes combine with awareness of Conway’s Law, team cognitive load, and responsive organization evolution to define a no-nonsense, team-friendly, humanistic approach to building and running software systems. Devised by experienced IT consultants Matthew Skelton and Manuel Pais, the Team Topologies approach is informed by the well-known DevOps Team Topologies patterns (also authored and curated by Matthew and Manuel). Matthew and Manuel have worked with many organizations around the world to help them shape their teams for modern software delivery, and Team Topologies is the result of that experience. teamtopologies.com

Beyond the Spotify model - Team Topologies - DevTestNorth - 2019-09-25 - Matt...

Matthew Skelton

This talk covers the basics of organization design using Team Topologies, exploring a selection of key team types and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on the forthcoming 2019 book Team Topologies and first-hand experience helping companies around the world with the design of their technology teams. From a talk given at Leeds DevOps meetup group: http://www.leedsdevops.org.uk/post/2019-09-08-monday-16th-september-2019-at-the-odi-node-in-leeds/

Beyond the Spotify model - Team Topologies - Leeds DevOps - 2019-09-16 - Matt...

Matthew Skelton

Monoliths, microservices, and team cognitive load - Team Topologies - DOES EU...

Matthew Skelton

The book Accelerate shows that Continuous Delivery (CD) practices are essential to high organizational performance. Many cloud-native CD practices can be applied to emerging digital sectors like healthcare and manufacturing for increased reliability and effectiveness. In this talk, Matthew Skelton reviews the current state-of-the-art for Continuous Delivery practices for cloud-native software and explores how these approaches are influencing emerging practices for software in healthcare and manufacturing.

The future of Continuous Delivery - cloud-native, healthcare, manufacturing -...

Matthew Skelton

For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes. This talk will cover the basics of organization design using Team Topologies, exploring a selection of key team types, and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on the forthcoming 2019 book Team Topologies and first-hand experience helping companies around the world with the design of their technology teams. Key takeaways: 1. Why using the “Spotify Model” of team design is not enough 2. The four fundamental team topologies needed for modern software delivery 3. The three team interaction modes that enable fast flow and rapid learning 4. How to address Conway’s Law, cognitive load, and team evolution with Team Topologies From a keynote talk at Jax DevOps 2019, London.

Beyond the Spotify model - Team Topologies - Keynote at JAX DevOps 2019-05-16...

Matthew Skelton

Plus de Matthew Skelton (20)