How to choose tools for DevOps and Continuous Delivery - #doxlon

•

4 likes•3,764 views

With an ever-increasing array of tools and technologies claiming to 'enable DevOps', how do we know which tools to try or to choose? In-house, open source, or commercial? Ruby or shell? Dedicated or plugins? It transpires that highly collaborative practices such as DevOps and Continuous Delivery require new ways of assessing tools and technologies in order to avoid creating new silos. Matthew Skelton shares his recent experience of helping many different organisations to evaluate and select tools to facilitate DevOps; the recommendations may surprise you. A talk given at DevOps Exchange (#doxlon) meetup group on 24th July 2014: http://www.meetup.com/DevOps-Exchange-London/events/194288152/

How to choose tools
for DevOps and
Continuous Delivery
Matthew Skelton, Skelton Thatcher Consulting
DevOps Exchange meetup group,
24 July 2014, London, UK
#doxlon

Collaboration
Learning
Singleton tools
Conway’s Law

Matthew Skelton
•15 years building &
operating software systems
•Cybernetics + Neuroscience
• control engineering
• psychology
• ‘network’ interactions
@matthewpskelton

PIPELINE
Conference
London Continuous
Delivery meetup
group (#londoncd)

Help orgs to adopt and sustain
good engineering practices
Interim CTO/Head of X, tech strategy,
architecture, workshops, delivery

Recent clients
•Tourism
•Betting & gambling
•Travel booking
•Financial data & reporting
•Healthcare

Common themes
•Online since ~1999
•Successful in their sector
•Large, central core database(s)
•Non-aligned goals
•Need to adopt DevOps and
Continuous Delivery

Common needs
•Technology selection ticklists
•Team interactions
•Collaboration opportunities
•Tools as catalysts

Continuous Delivery
•A scientific approach to
changing software systems
(Dave Farley)
•Regular, rapid, repeatable,
reliable changes

Continuous Delivery
•Quality
•Safety
•Reliability
•Psychology
•Effectiveness

DevOps
“Highly effective, daily collaboration
between software developers and IT
operations people to produce
relevant, working systems” *
*also QA/Testing, IT Service Desk,
Programme Management,
Commercial, Marketing, etc.

Not DevOps
“Automation”
“Build & Release”
“Infrastructure Development”
“System Administration”

Challenges were:
•Limited Git skills in Service team
•Manual deployments
•‘Snowflake’ servers
•No CI
•Risks: security, automation, etc

http://bit.ly/thetrainline-weekly-deploy

What we did
•Built a walking skeleton pipeline
•Modelled security roles and stages
•Included manual steps (at first)
•Walked people through steps
•Finally: opened firewall so
everyone could see the UI

Results
•Security: happy
•Service team: relieved (& happy)
•Developers: won over (& happy)
•Business: surprised (& happy)

LogStash
•ElasticSearch+ LogStash+ Kibana
•ELK
•In Production, Pre-Prod, Test
•On developer machines!!!

http://rashidkpc.github.io/Kibana/images/screenshots/searchss.png

Collaboration
& tool choice
Value collaboration as
a key criterion
Orthogonal to main purpose (?)
“How does [the use of] this tool
help people to collaborate?”

Learning & tool choice
Bring people with you
Appreciate current skills
Prefer achievable gains now
Avoid fear of too-scary tools

Singleton tools
(or the ‘Prize Bull’ approach)

Singleton tools
•Special database server
•Costly log aggregation
•Costly monitoring
•Server configuration

http://www.walpapershddownload.com/highland-cattle-wallpapers/

“Better features”?
Optimise globally across the
teams that need to collaborate

Singleton tool
Breaks feedback (learning) loop
from Production
Makes CI/CD more difficult
Underestimates value of
collaboration and learning

Mel Conway, 1968
“organizations which design
systems ... are constrained to
produce designs which are copies
of the communication structures
of these organizations”
http://www.melconway.com/Home/Conways_Law.html

Conway & Tool Choice
See the organisation as a system
Separate tools for separate teams
Shared tools for collaborative
teams
http://bit.ly/DevOpsTopologies

Conway’s Law
•Allan Kelly - @allankellynet
•https://vimeo.com/channels/londoncd

How to choose tools
for DevOps
Value collaboration aspects
Avoid a learning mountain:
evolve tooling
Avoid Production-only tools
Consider Conway’s Law
(this list is incomplete!)

Further reading
HighOps Operability eBook
bit.ly/OperabilityEbook
Build Quality In
buildqualityin.com

Thank you
matthewskelton.net / @matthewpskelton
skeltonthatcher.com
HT: @Squire_Matt, @alan_parkinson

Autonomous empowered cross-functional product teams. Sounds like a dream team, doesn’t it? So what does this mean for software delivery teams? Do we expect such a team to set up their CI/CD tooling and pipelines, automate infra, test and secure *all the things*, and, of course, run and monitor their product live? Oh wait, there’s more: they need to actually understand who their customers are, what they need from the product, what is causing friction, and what is the viability of our product as a net positive for the organization. Sounds familiar? Congratulations, you’re already playing Tetris with cognitive load! Want to know more about team cognitive load and how we can make use of effective team topologies and interactions to balance and minimize the cognitive load across an ecosystem of teams. Join this talk and climb up the cognitive load Tetris ranking with the help of one of the co-authors of the book Team Topologies: Organizing Business and Technology Teams for Fast Flow!

Business and Technical Agility with Team Topologies, Jun 2021

Manuel Pais

Organizations that do not adapt rapidly to the modern, highly-changeable business and technical environment are failing, and failing in large numbers. Increased regulation, pressures from climate change, shifting of energy sources, digitalization, cloud-native, and (recently) the COVID-19 pandemic are all driving a need for business and technical agility in organizations of all sizes. In this talk, we’ll explore how the patterns and principles from Team Topologies promote true business and technical agility through a rapid flow of software change, fast feedback from running systems, a strong drive for loose coupling, and awareness of sociotechnical mirroring. Combined with a product mindset and techniques from Domain-driven Design, the Team Topologies approach is helping organizations around the world to adapt to the “new normal” and achieve true business and technical agility.

Product Teams Need a Family Too! @ Stockholm Engineering Leadership Meetup, J...

Manuel Pais

Beyond Agile with Team Topologies

Rich Allen

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

Conflux

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 by Matthew Skelton of Conflux at NAV, Oslo on 2020-01-23

Product Teams Need a Family Too! @ Product Camp Brazil, Dec 2021

Manuel Pais

Continuous Delivery at scale - Matthew Skelton - NHS Digital agile CoP - Marc...

Matthew Skelton

Continuous Delivery practices have increasingly become “table stakes” for effective software delivery since the publication of the book Continuous Delivery by Jez Humble and Dave Farley in 2010. The combination of sound technical practices and a scientific approach to testing and feature development has led to significant success with software delivery with organisations around the world. However, in large organisations with many teams and many different suppliers, there are also many ideas about what Continuous Delivery is. This variety of approaches and assumptions can lead to conflicts around deployments, testing, releasing, and operations, resulting in a macro-level sub-optimal flow of change. In this talk, Matthew Skelton will share some insights from his time spent as Engineering Lead at a large GOV.UK department during most of 2018. There he championed Continuous Delivery practices across 70+ teams and 7 locations, helping to raise standards for software operability, Developer Experience (DevEx), testing, deployments, and inter-team communications. He will share some practical techniques for getting Continuous Delivery working at scale.

Business agility with Team Topologies - NatWest Group - 2021-01-19

Matthew Skelton

Organizations that do not adapt rapidly to the modern, highly-changeable business environment are failing, and failing in large numbers. Increased regulation, pressures from climate change, shifting of energy sources, digitalization, and (recently) the COVID-19 pandemic are all driving a need for business agility in organizations of all sizes. In this talk, we’ll explore how the patterns and principles from Team Topologies promote true business agility through a rapid flow of software change, fast feedback from running systems, a strong drive for loose coupling, and an awareness of sociotechnical mirroring. Combined with a product mindset and techniques from Domain-driven Design, the Team Topologies approach is helping organizations around the world to adapt to the “new normal” and achieve true business agility. Matthew Skelton, co-author of Team Topologies, shares insights from organizations in several different industry sectors including banking, financial services, insurance, retail, and leisure.

Organizations that do not adapt rapidly to the modern, highly-changeable business and technical environment are failing, and failing in large numbers. Increased regulation, pressures from climate change, shifting of energy sources, digitalization, cloud-native, and (recently) the COVID-19 pandemic are all driving a need for business and technical agility in organizations of all sizes. In this talk, we’ll explore how the patterns and principles from Team Topologies promote true business and technical agility through a rapid flow of software change, fast feedback from running systems, a strong drive for loose coupling, and an awareness of sociotechnical mirroring. Combined with a product mindset and techniques from Domain-driven Design, the Team Topologies approach is helping organizations around the world to adapt to the “new normal” and achieve true business and technical agility.

Monoliths vs Microservices is the Wrong Question; Start with Team Cognitive L...

Manuel Pais

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 I explain how and why. Key takeaways: - What is team cognitive load and why that matters - Using team cognitive load as the guiding principle for sustainable ownership and evolution of software systems - What are the fundamental topologies and interaction modes that help reduce cognitive load

Team Topologies at Parts Unlimited, The Unicorn Project Book Club, Jan 2020

Manuel Pais

Business Agility with Team Topologies @ Digital Transformation London meetup,...

Manuel Pais

 Organizations that do not adapt rapidly to the modern, highly-changeable business and technical environment are failing, and failing in large numbers. Increased regulation, pressures from climate change, shifting of energy sources, digitalization, cloud-native, and (recently) the COVID-19 pandemic are all driving a need for business and technical agility in organizations of all sizes. In this talk, we’ll explore how the patterns and principles from Team Topologies promote true business and technical agility through a rapid flow of software change, fast feedback from running systems, a strong drive for loose coupling, and an awareness of sociotechnical mirroring. Combined with a product mindset and techniques from Domain-driven Design, the Team Topologies approach is helping organizations around the world to adapt to the “new normal” and achieve true business and technical agility.  Manuel Pais is co-author of Team Topologies: organizing business and technology teams for fast flow. Recognized by TechBeacon as a DevOps thought leader, Manuel is an independent IT organizational consultant and trainer, focused on team interactions, delivery practices and accelerating flow. Manuel is also a LinkedIn instructor on Accelerating Continuous Delivery in the Enterprise. https://www.linkedin.com/in/manuelpais/

Business and technical agility with Team Topologies - QCon Plus - 2021-05-26

Matthew Skelton

Organizations that do not adapt rapidly to the modern, highly-changeable business and technical environment are failing, and failing in large numbers. Increased regulation, pressures from climate change, shifting of energy sources, digitalization, cloud-native, and (recently) the COVID-19 pandemic are all driving a need for business and technical agility in organizations of all sizes. In this talk, we’ll explore how the patterns and principles from Team Topologies promote true business and technical agility through a rapid flow of software change, fast feedback from running systems, a strong drive for loose coupling, and an awareness of sociotechnical mirroring. Combined with a product mindset and techniques from Domain-driven Design, the Team Topologies approach is helping organizations around the world to adapt to the “new normal” and achieve true business and technical agility. From a talk at QCon Plus on 2021-05-26

Avoiding the CI/CD Monolith with Team Design & Evolution @ London CD meetup, ...

Manuel Pais

We often talk about monoliths at the application and database level. However, there are many other manifestations: monolithic tooling, monolithic infrastructure, monolithic releases, monolithic testing, and even monolithic thinking. In my experience, more than legacy technology or architecture, the emergence of monoliths often comes down to a lack of purposeful team design and evolution. Conway’s Law - the mirroring effect between team structures and dependencies and the resulting system design - is no stranger to CI/CD. Once we acknowledge the socio-technical nature of software delivery, we consequently recognize the need for a team-centric, not tool-centric, approach for sustainable CI/CD. We start asking questions like: should every application team own and maintain their own instances and flavors of the CI/CD tooling (since it’s all codifiable now, right)? Or do we need a CI/CD team to handle the tooling and infrastructure for everyone else in the org so teams only have to worry about their own pipelines? Or something in between, like a CI/CD platform providing out-of-the-box solutions that can be customized by application teams to fit their specific needs? Just like we are advancing our tools to become easier to install, run and update, we also need to think about clarifying team interactions and responsibility boundaries for effective ownership and evolution of both the CI/CD system (it’s actually a product) and the application pipelines. Manuel Pais is co-author of Team Topologies: organizing business and technology teams for fast flow. Recognized by TechBeacon as a DevOps thought leader, Manuel is an independent IT organizational consultant and trainer, focused on team interactions, delivery practices and accelerating flow.

What is platform as a product? Clues from Team Topologies - WTFinar with Cont...

Matthew Skelton

From a webinar on 29 April 2021 https://info.container-solutions.com/wtf-is-platform-as-product-2nd-edition 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.

Playing Tetris with Cognitive Load @ QEDx internal conference (keynote), Jan ...

Manuel Pais

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

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.

Best Practices for Accelerating Continuous Testing

Sailaja Tennati

DevOps is all about Continuous Testing. Without CT there is no continuous delivery. This talk explained how CT affects the success of DevOps and enumerates seven best practices that are essential for acceleration of Continuous Testing which include: 1. Team and culture specific to CT 2. CT System stability and metrics 3. Test tools integration 4. Accelerated test execution 5. CT-Ready tools 6. Fast and relevant test case analytics 7. Orchestration of test topologies

What Is Platform as a Product - Clues from Team Topologies @ AXA, Sep 2021

Manuel Pais

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, 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 - Manuel explains how organisations like Uswitch have successfully used the platform-as-product model to accelerate and simplify the delivery of software at scale.

Fast Flow & Organizational Evolution with Team Topologies @ Masters of Softwa...

Manuel Pais

Traditional vs Modern Internal Platforms @ Humanitec webinar, Jun 2021

Manuel Pais

What are some of the key differences between traditional and modern internal platforms? Many organizations have built large internal “platforms” over the years, but never achieved the benefits in speed and reduced cognitive load for their development teams that more nimble organizations increasingly showcase. Why is that? What kind of behaviors and mindset drive modern Internal Developer Platforms (IDPs) and platform teams? There is hardly a more competent DevOps thought leader on this subject than Manuel Pais, co-author of the book Team Topologies. During the webinar we will answer questions like: How do you define core goals of modern internal platforms? What are typical consumption patterns of IDPs? How can you balance between platform stakeholders vs customers?

Practical operability techniques for teams - Matthew Skelton - Agile in the C...

Skelton Thatcher Consulting Ltd

In this talk, Matthew Skelton (Skelton Thatcher Consulting) explores five practical, tried-and-tested, real-world techniques for improving operability with many kinds of software systems, including cloud, Serverless, on-premise, and IoT. Logging as a live diagnostics vector with sparse event IDs Operational checklists and 'run book dialogue sheets' as a discovery mechanism for teams Endpoint healthchecks as a way to assess runtime dependencies and complexity Correlation IDs beyond simple HTTP calls Lightweight 'User Personas' as drivers for operational dashboards These techniques work very differently with different technologies. For instance, an IoT device has limited storage, processing, and I/O, so generation and shipping of logs and metrics looks very different from the cloud or 'serverless' case. However, the principles - logging as a live diagnostics vector, event IDs for discovery, etc - work remarkably well across very different technologies. From a talk at Agile in the City Bristol 2017 http://agileinthecity.net/2017/bristol/sessions/index.php?session=44

Rethinking enterprise architecture for DevOps, Agile, and cloud native organi...

Michael Coté

Current application theory says that all responsibility for software should be pushed down to the actual DevOps-style team writing, delivering, and running the software. This leaves the EA role in the dust, seemingly killing it off. In addition to this being disquieting to EAs out there who have steep mortgage payments and other expensive hobbies, it seems to drop out the original benefits of enterprise architecture, namely oversight of all IT-related activities to make sure things don’t go wrong (e.g., spending, poor tech choices, problematic integration, etc.) and that things, rather, go right. As presented at the O'Reilly Software Architecture Conference in Berlin, November 2019.

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

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.

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

Matthew Skelton

Frozen DevOps? Team Topologies Comes to the Rescue! @ DevOpsDays Poznan, Oct ...

Manuel Pais

Why are so many organizations stuck in the "middle" of DevOps evolution? What's preventing them from achieving higher levels of organizational performance despite all the automation, tooling, and good practices in place? Puppet's State of DevOps Report 2021 provides important research-based clues to answer these questions, supported by the patterns and recommendations in Team Topologies. In this talk we cover the self-imposed limitations of blindly following some “myths” around DevOps. Almost 80% of organizations are stuck in the "frozen middle" of DevOps evolution because of lack of organizational sensemaking abilities. The margin for growth for these organizations is tremendous, but they need to think beyond technical capabilities to unlock the potential of their teams to deliver with more autonomy and a sense of purpose. The data shows that Team Topologies provides the necessary organizational and team interaction patterns that help organizations achieve performance metrics such as delivering a new customer change request to live in under one hour, or diagnosing and recovering from a serious issue in production in under an hour. Get the State of DevOps Report 2021 here: https://puppet.com/resources/report/2021-state-of-devops-report To learn more about Team Topologies: https://teamtopologies.com/learn https://academy.teamtopologies.com

5 practical operability techniques for teams - Matthew Skelton - SQUID meetup...

Matthew Skelton

In this talk, we explore five practical, tried-and-tested, real world techniques for improving operability with many kinds of software systems, including cloud, Serverless, on-premise, and IoT: - Logging as a live diagnostics vector with sparse Event IDs - Operational checklists and ‘Run Book dialogue sheets’ as a discovery mechanism for teams - Deployment Verification Tests as a way to assess runtime dependencies and readiness for service - Correlation IDs beyond simple HTTP calls - Lightweight ‘User Personas’ as drivers for operational dashboards Based on work in many industry sectors, we will learn how to improve the operability of software systems using these team-friendly techniques. Matthew Skelton is Head of Consulting at Conflux (confluxdigital.net) where he specialises in Continuous Delivery, operability and organisation design for software in manufacturing, ecommerce, and online services, including cloud, IoT, and embedded software.

Team Topologies in action - early results from industry - DOES Las Vegas 2020...

Matthew Skelton

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: - Footasylum gives fashion-focused youth a multi-branded retail experience mixing global sportswear household names with emerging brands and its own stable of in-house labels. Founded in 2005, Footasylum now has 70 stores across the UK and a thriving ecommerce platform, with revenue of £260m per annum and over 2500 employees. Footasylum used Team Topologies patterns to revolutionize their ecommerce platform. - 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 - 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.

How to choose tools for DevOps and Continuous Delivery - DevOps Manchester me...Matthew Skelton

How to choose tools for DevOps and Continuous Delivery - DevOps Cardiff

Matthew Skelton

What's hot

Business and Technical Agility with Team Topologies @ WTF Is Cloud Native, No...

Manuel Pais

Organizations that do not adapt rapidly to the modern, highly-changeable business and technical environment are failing, and failing in large numbers. Increased regulation, pressures from climate change, shifting of energy sources, digitalization, cloud-native, and (recently) the COVID-19 pandemic are all driving a need for business and technical agility in organizations of all sizes. In this talk, we’ll explore how the patterns and principles from Team Topologies promote true business and technical agility through a rapid flow of software change, fast feedback from running systems, a strong drive for loose coupling, and an awareness of sociotechnical mirroring. Combined with a product mindset and techniques from Domain-driven Design, the Team Topologies approach is helping organizations around the world to adapt to the “new normal” and achieve true business and technical agility.

Monoliths vs Microservices is the Wrong Question; Start with Team Cognitive L...

Manuel Pais

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 I explain how and why. Key takeaways: - What is team cognitive load and why that matters - Using team cognitive load as the guiding principle for sustainable ownership and evolution of software systems - What are the fundamental topologies and interaction modes that help reduce cognitive load

Team Topologies at Parts Unlimited, The Unicorn Project Book Club, Jan 2020

Manuel Pais

Business Agility with Team Topologies @ Digital Transformation London meetup,...

Manuel Pais

Business and technical agility with Team Topologies - QCon Plus - 2021-05-26

Matthew Skelton

Organizations that do not adapt rapidly to the modern, highly-changeable business and technical environment are failing, and failing in large numbers. Increased regulation, pressures from climate change, shifting of energy sources, digitalization, cloud-native, and (recently) the COVID-19 pandemic are all driving a need for business and technical agility in organizations of all sizes. In this talk, we’ll explore how the patterns and principles from Team Topologies promote true business and technical agility through a rapid flow of software change, fast feedback from running systems, a strong drive for loose coupling, and an awareness of sociotechnical mirroring. Combined with a product mindset and techniques from Domain-driven Design, the Team Topologies approach is helping organizations around the world to adapt to the “new normal” and achieve true business and technical agility. From a talk at QCon Plus on 2021-05-26

Avoiding the CI/CD Monolith with Team Design & Evolution @ London CD meetup, ...

Manuel Pais

What is platform as a product? Clues from Team Topologies - WTFinar with Cont...

Matthew Skelton

Playing Tetris with Cognitive Load @ QEDx internal conference (keynote), Jan ...

Manuel Pais

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

Matthew Skelton

Best Practices for Accelerating Continuous Testing

Sailaja Tennati

What Is Platform as a Product - Clues from Team Topologies @ AXA, Sep 2021

Manuel Pais

Fast Flow & Organizational Evolution with Team Topologies @ Masters of Softwa...

Manuel Pais

Traditional vs Modern Internal Platforms @ Humanitec webinar, Jun 2021

Manuel Pais

Practical operability techniques for teams - Matthew Skelton - Agile in the C...

Skelton Thatcher Consulting Ltd

Rethinking enterprise architecture for DevOps, Agile, and cloud native organi...

Michael Coté

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

Matthew Skelton

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

Matthew Skelton

Frozen DevOps? Team Topologies Comes to the Rescue! @ DevOpsDays Poznan, Oct ...

Manuel Pais

5 practical operability techniques for teams - Matthew Skelton - SQUID meetup...

Matthew Skelton

Team Topologies in action - early results from industry - DOES Las Vegas 2020...

Matthew Skelton

What's hot (20)