Sustainable Continuous Delivery: Patterns for rapid and reliable Releases @ DevOpsCon Berlin

•

3 likes•344 views

Today we pay close attention to scaling our systems, testing for chaos, and reducing MTTR in production. Yet our delivery pipelines don’t get nearly as much love. This talk presents tried and tested patterns for increasing accelerating delivery of changes in a safe manner. We’ll also try to solve the mystery of what is sustainable Continuous Delivery. Everyone wants to go faster but also safer, so we’re cramming more and more activities in the pipeline, from security controls to database changes, to compliance approvals, soon networking… How can we do this AND still move fast AND avoid burning out teams with all this cognitive load? Join this session to find out! After this talk, you will have learned about: * patterns to ensure the reliability of your pipelines and make application changes safer * smart patterns to accelerate delivery, such as continuous pruning and short path to production * how to sustain your CI/CD adoption growth with key practices like immutable delivery system.

Technology

Sustainable CD -
Patterns for Rapid &
Reliable Releases 1
Manuel Pais

About me
Manuel Pais
MS Software Eng
@manupaisable
me@manuelpais.net
http://manuelpais.net
DevOps Consultant & Trainer
Co-author of “Team Topologies”
Focused on teams and flow
2@manupaisable | manuelpais.net

@manupaisable | manuelpais.net 3
Today
1. Intro to boring releases
2. Patterns for reliable releases
3. Patterns for rapid releases
4. Patterns for sustainable delivery

@manupaisable | manuelpais.net 4
Today
1. Intro to boring releases
2. Patterns for reliable releases
3. Patterns for rapid releases
4. Patterns for sustainable delivery

8
Outcomes
@manupaisable | manuelpais.net

@manupaisable | manuelpais.net 9
Today
1. Intro to boring releases
2. Patterns for reliable releases
3. Patterns for rapid releases
4. Patterns for sustainable delivery

“ability to get changes of all types,
into production, or into the hands of
users, safely and quickly in a
sustainable way”
–Dave Farley & Jez Humble
continuousdelivery.com
@manupaisable | manuelpais.net 10

Patterns for reliable releases
12@manupaisable | manuelpais.net

Patterns for reliable releases
1. Map value stream in the pipeline
14@manupaisable | manuelpais.net

Patterns for reliable releases
17@manupaisable | manuelpais.net

Patterns for reliable releases
1. Map your value stream to the pipeline
2. Measure key metrics
19@manupaisable | manuelpais.net

Speed lead time
Quality failure rate
Operability MTTR
20@manupaisable | manuelpais.net

Flow efficiency =
“generally flow efficiencies are
around the 15% mark”
http://leankanban.com/flow-efficiency-a-great-metric-you-probably-arent-using
@manupaisable | manuelpais.net 22

issue is not how long it takes to do
something, it's how long we're
waiting for it to get done
@manupaisable | manuelpais.net 23

Patterns for reliable releases
24@manupaisable | manuelpais.net

Patterns for reliable releases
1. Map your value stream to the pipeline
2. Measure key metrics on speed,
quality & operability
3. Put in the groundwork
26@manupaisable | manuelpais.net

Automated build in clean environment
Ephemeral prod-like test environment
Health checks and fast smoke tests
Automated acceptance tests (BDD)
Everything as code (one truth)
Single path to production
27@manupaisable | manuelpais.net

Patterns for reliable releases
1. Map value stream in the pipeline
2. Measure key metrics
3. Put in the groundwork
29@manupaisable | manuelpais.net

@manupaisable | manuelpais.net 30
Today
1. Intro to boring releases
2. Patterns for reliable releases
3. Patterns for rapid releases
4. Patterns for sustainable delivery

@manupaisable | manuelpais.net 32
Build Test Deploy

@manupaisable | manuelpais.net 33
FixMonitorRun
CI
Peer
review
Infra Security Comply
Database Accept UX Deploy

@manupaisable | manuelpais.net 34
can’t auto-
scale people
How to cope with
ever increasing
cognitive load on
teams to build and
run applications?

Patterns for rapid releases
1. Design intelligent pipelines
2. Evolve teams and interactions
3. Set up a self-service platform
35@manupaisable | manuelpais.net

Patterns for rapid releases
1. Identify & remove bottlenecks
2. Shorten path to production
3. Continuous pruning
37@manupaisable | manuelpais.net

Waiting for pipeline
@manupaisable | manuelpais.net 38

Waiting for pipeline
@manupaisable | manuelpais.net 39

Waiting for dependencies
@manupaisable | manuelpais.net 40

Waiting for dependencies
@manupaisable | manuelpais.net 41

Patterns for rapid releases
1. Design intelligent pipelines
2. Evolve teams and interactions
3. Set up a self-service platform
42@manupaisable | manuelpais.net

Patterns for rapid releases
1. Identify & remove bottlenecks
2. Shorten path to production
3. Continuous pruning
43@manupaisable | manuelpais.net

Risk-based activities (short & wide pipeline)
@manupaisable | manuelpais.net 44

Patterns for rapid releases
pipelines
1. Set up a self-service platform
45@manupaisable | manuelpais.net

Patterns for rapid releases
1. Identify & remove bottlenecks
2. Shorten path to production
3. Continuous pruning & fast feedback
47@manupaisable | manuelpais.net

48
“There are just two moments when
an automated test provides useful
information: the first time it passes
and when it subsequently fails.”
@manupaisable | manuelpais.net
Continuous pruning

Patterns for rapid releases
pipelines
Bonus!
Evolve teams and interactions
1. Set up a self-service platform
52@manupaisable | manuelpais.net

Patterns for rapid releases
1. Identify & remove bottlenecks
2. Shorten path to production
3. Continuous pruning & fast feedback
54@manupaisable | manuelpais.net

@manupaisable | manuelpais.net 55
Today
1. Intro to boring releases
2. Patterns for reliable releases
3. Patterns for rapid releases
4. Patterns for sustainable delivery

•CI tool
•CD tool (orchestration)
•Plugins / 3rd party tools
•Pipeline definitions
•Source repos
•Artifact repos
•CI + CD infrastructure
@manupaisable | manuelpais.net 59
Delivery (CI/CD) system

CI/CD Toolchain
Pipelines
Infra
App 1
App 2
CI/CD tool Artifact tool
Artifacts
Delivery (CI/CD) system

System Operability
Available (minimal downtime)
Scalable (no pipelines waiting to run)
Monitored (alerts on resources and errors)
Recoverable (focus on diagnosis & MTTR)
@manupaisable | manuelpais.net 61

Patterns for sustainability
1. Treat your pipeline as a product
2. Treat your pipeline as a product
3. Treat your pipeline as a product
62@manupaisable | manuelpais.net

Immutable infrastructure
Blue-green deployments
Monitoring & alerting
Aggregated logging
Pipelines-as-code
Auto-scaling
63@manupaisable | manuelpais.net

About me
Manuel Pais
MS Software Eng
@manupaisable
me@manuelpais.net
http://manuelpais.net
DevOps Consultant
Co-author of “Team Topologies”
Focused on teams and flow
64@manupaisable | manuelpais.net

@manupaisable | manuelpais.net 67
https://www.youtube.com/watch?v=MAFpuwB7-to

Today, we pay close attention to scaling our systems by testing for chaos and reducing MTTR in production. However, our delivery pipelines don’t get nearly as much love. This talk presents tried and tested patterns for increasing an accelerated delivery of changes in a safe manner. We’ll also try to solve the mystery of sustainable Continuous Delivery. Everyone wants to go faster but also safer. As a result, we’re cramming more and more activities in the pipeline, from security controls and database changes to compliance approvals and even networking. How can we do this AND still move fast AND avoid burning out teams with all this cognitive load? Key takeaways: - learn patterns to ensure the reliability of your pipelines and make application changes safer - learn smart patterns to accelerate delivery, such as continuous pruning and short path to prod - understand how to sustain your CI/CD adoption growth with key practices like immutable delivery system

Introduction the dev ops world

VishwasN6

Agile Gurugram 2016 | Conference | Demystifying DevOps | Uday Kumar

AgileNetwork

The Future Present of Scrum (Agile Tour Dublin 2016)

Gunther Verheyen

From Continuous Integration to Continuous Delivery and DevOps

Luca Minudel

Introduction to DevOps

João Miranda

Continuous is great

Daniel Breston

ScrumDay Germany - The Future Present of Scrum

Gunther Verheyen

Scrum has been around since 1995, for more than two decades. Since the release of the Agile Manifesto in 2001, Scrum gradually become the most applied method for Agile software development. Depending on the source, 70-90% of all Agile teams worldwide say they use Scrum. Can we say we’re Done with Scrum? Or is the key for future success still Scrum – meaning we are not yet Done with Scrum? The key to employing Scrum professionally is creating Done Increments of product, where “Done” actually means “releasable in production.” It might take another two decades to actually get there.

More and more teams are turning to DevOps as a way of working together to improve the efficiency and quality of software delivery and start adding more value to the business. But without having someone on the team with experience of putting it into practice, it's sometimes difficult to know how to get started. Redgate Software invited Steve Thair, CTO at the DevOpsGuys, to deliver a one-hour training session on 'How to get started with DevOps'. Steve gave practical tips on how you can start implementing DevOps in your own organization. The recording can be found here - https://youtu.be/ZioF58drwcA For more information about services from the DevOpsGuys visit www.devopsguys.com To find out about extending DevOps practices to the database visit www.red-gate.com/solutions

DevOps(1) : What's DevOps - (MOSG)

Soshi Nemoto

Caution: Live Subjects! Lean Experiments for Services

Lean Startup Co.

Lauren Braun, gravitytank , @another_lauren Testing apps, websites and digital services is pretty well-documented territory. But running lean experiments for services without a screen can seem daunting. In-person services are holistic experiences with lots of moving parts, which can easily make testing costs and timelines balloon. The biggest challenge is figuring out which parts of the service to make real and which parts to fake. At gravitytank, we work with organizations big and small to run lean experiments that focus on the most uncertain and risky element of a new service. Like any good test, our experiments generate useful quant data (i.e. throughput, sales, user preferences), but we also leverage them to collect meaningful qualitative feedback. We’ve used this approach to lean service MVPs for restaurant startups, huge CPG companies, global hotel chains and others. Across the board, the learnings have had significant impact on development. Caution: Live Subject! will take you through a few examples, offer some ‘pro tips’, and together, we’ll run a rapid-fire service experiment to bring it to life.

5 Steps for a High-Performing DevOps Culture

JumpCloud

¿Qué es DevOps y por qué es importante en el Ciclo de Software? por michelada.io

Software Guru

DevOps - Right Tool for Right Phase

Dalibor Blazevic

DevOps overview 2019-04-13 Nelkinda April Meetup

Shweta Sadawarte

Understanding DevOps in simpler way with Continuous Delivery

Swapnil Jain

How to implement DevOps in your Organization

Dalibor Blazevic

Delivery patterns for rapid and reliable releases (All Day DevOps 2018)

Manuel Pais

Continuous Delivery Patterns for Boring Releases @ DevOps Porto meetup - July...

Manuel Pais

In today's world, we need not only to maintain our systems running 24x7 in production but we must also be able to keep them releasable 24x7. We can only do that with modern infrastructure and software delivery practices. Releases should be even more boring than doing your supermarket shopping. Make a code change, see it go through the pipeline, get green or red result. If red, fix or rollback. If green, deploy. If deploy fails, rollback. Monitor forever. Because everyone wants to go faster but also safer, we're cramming more and more activities in the pipeline, from security controls to database changes, to compliance approvals, soon networking... How can we do this AND still move fast AND avoid burning out teams with all this cognitive load? I will talk about how to ensure that your delivery system serves its core purpose of quickly and safely progressing our client-facing systems from commit to production. You'll also hear about key practices for software releasability like pipeline-as-code, short and wide pipelines, build and release from zero to production, blue-green deployments, and more!

La La Land of DevOps Integration (Continuous Lifecycle London 2018)

Manuel Pais

DevOps is about culture and practices, not tools, right? Well, what if the tools we chose are keeping us away from good practices? Adopting a “DevOps one-stop solution” often means you are trading knowledge of your toolchain (and the adequate tool boundaries for your delivery) for ease of setup. Yes, you’ll go faster at the start. But you will inevitably slow down over time, as technology changes and new practices emerge. A flexible toolchain standardizes on practices, not tools, so it’s important to understand the trade-offs we’re making when selecting tools, especially if we’re driven only by familiarity and ease of setup, an anti-pattern we’ve seen across several of our clients.

Treating Your Pipeline as a Product - Full Day Workshop

Manuel Pais

Everyone Is Part of Continuous Delivery (Agile Portugal)

Manuel Pais

Ncerc rlmca202 adm m1 ssm

ssmarar

Mastering Complex Application DeploymentsIBM UrbanCode Products

Continuous delivery best practices and essential tools

DBmaestro - Database DevOps

Power Platform ALM with DevOps

Christopher R. Barber

Automated testing 101

Tabitha Chapman

DevOps ci/cd with Microsoft vsts and azure

Murughan Palaniachari

When agility meets software quality

Babak Khorrami

Software life cycle

kingseif

What's hot

How to get started with DevOps

Red Gate Software

DevOps(1) : What's DevOps - (MOSG)

Soshi Nemoto

Caution: Live Subjects! Lean Experiments for Services

Lean Startup Co.

5 Steps for a High-Performing DevOps Culture

JumpCloud

¿Qué es DevOps y por qué es importante en el Ciclo de Software? por michelada.io

Software Guru

DevOps - Right Tool for Right Phase

Dalibor Blazevic

DevOps overview 2019-04-13 Nelkinda April Meetup

Shweta Sadawarte

Understanding DevOps in simpler way with Continuous Delivery

Swapnil Jain

How to implement DevOps in your Organization

Dalibor Blazevic

What's hot (9)

How to get started with DevOps

DevOps(1) : What's DevOps - (MOSG)

Caution: Live Subjects! Lean Experiments for Services

5 Steps for a High-Performing DevOps Culture

¿Qué es DevOps y por qué es importante en el Ciclo de Software? por michelada.io

DevOps - Right Tool for Right Phase

DevOps overview 2019-04-13 Nelkinda April Meetup

Understanding DevOps in simpler way with Continuous Delivery

How to implement DevOps in your Organization

Similar to Sustainable Continuous Delivery: Patterns for rapid and reliable Releases @ DevOpsCon Berlin

Delivery patterns for rapid and reliable releases (All Day DevOps 2018)

Manuel Pais

Continuous Delivery Patterns for Boring Releases @ DevOps Porto meetup - July...

Manuel Pais

La La Land of DevOps Integration (Continuous Lifecycle London 2018)

Manuel Pais

Treating Your Pipeline as a Product - Full Day Workshop

Manuel Pais

Everyone Is Part of Continuous Delivery (Agile Portugal)

Manuel Pais

Ncerc rlmca202 adm m1 ssm

ssmarar

Mastering Complex Application DeploymentsIBM UrbanCode Products

Continuous delivery best practices and essential tools

DBmaestro - Database DevOps

Power Platform ALM with DevOps

Christopher R. Barber

Automated testing 101

Tabitha Chapman

DevOps ci/cd with Microsoft vsts and azure

Murughan Palaniachari

When agility meets software quality

Babak Khorrami

Software life cycle

kingseif

Engineering DevOps Right the First Time

Marc Hornbeek

Companies with high-performing IT organizations are twice as likely to exceed their profitability, market share and productivity goals. These are impressive results which every business would like to accomplish before competitors beat them to it. Only a minority of enterprises are achieving high-performance DevOps implementations. Many are struggling to realize DevOps at all, at the level of business units and enterprise. An engineering approach for businesses and enterprises to implement DevOps, at the business or enterprise level meets specific business transformation goals in the fastest time with the least cost and without false starts. An engineering approach which leads to DevOps success quickly and without false starts will be presented. A unique one-of-a-kind physical model of an electro-mechanical DevOps machine and results of DevOps pipeline software simulations will be displayed and used to demonstrate the principles of DevOps stage optimizations.

Everyone is Part of Continuous Delivery @ All Day DevOps (Oct 2017)

Manuel Pais

StarWest2016_T24_ExploratoryAutomation_DawnJardine_FinalDawn Jardine

Lean UX

Chester Yiu-Lam Ip

Standardmahtabsiddiqui

Promise and Challenge of Runtime Presentation(summary)

Joon ho Park

1 rapid prototyping modeldelaco

Similar to Sustainable Continuous Delivery: Patterns for rapid and reliable Releases @ DevOpsCon Berlin (20)

Delivery patterns for rapid and reliable releases (All Day DevOps 2018)

Continuous Delivery Patterns for Boring Releases @ DevOps Porto meetup - July...

La La Land of DevOps Integration (Continuous Lifecycle London 2018)

Treating Your Pipeline as a Product - Full Day Workshop

Everyone Is Part of Continuous Delivery (Agile Portugal)

Ncerc rlmca202 adm m1 ssm

Mastering Complex Application Deployments

Continuous delivery best practices and essential tools

Power Platform ALM with DevOps

Automated testing 101

DevOps ci/cd with Microsoft vsts and azure

When agility meets software quality

Software life cycle

Engineering DevOps Right the First Time

Everyone is Part of Continuous Delivery @ All Day DevOps (Oct 2017)

StarWest2016_T24_ExploratoryAutomation_DawnJardine_Final

Lean UX

Standard

Promise and Challenge of Runtime Presentation(summary)

1 rapid prototyping model

More from Manuel Pais

Accelerating Flow with Team Topologies & Friends @ Wroclaw Kanban, Lean & Cof...

Manuel Pais

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.

Beyond Engineering: The Future of Platforms @ CraftConf, May 2023

Manuel Pais

While we have made great strides in the last decade to break down silos in Engineering, in most organizations when you look outside there is still an abyss of understanding between teams sitting in different divisions in the organization. This can significantly slow down the flow of value to our customers, directly and indirectly. You’ve likely experienced at least one of these in your professional career… Not being allowed to use the right tool for the job because of a strict procurement process. Spending half a day to get a 20€ expense approved and reimbursed. Or a much anticipated employee onboarding portal that ends up being just a UI on top of the 73 steps and 14 approvals required to set up an employee workstation. None of this happens in bad faith, it just turns out traditionally teams and groups are incentivized for outputs, the more cycles you can run and the faster you can close requests the better. So we end up optimizing internal processes at the cost of company outcomes. I posit that, ultimately, this happens because teams don’t see each other as customers. You might be thinking “But they’re not our customers, they’re our colleagues!”. Also true. The key here is that every team, every division in an organization can adopt a platform mindset in which they treat what they offer to other teams as an internal product. That means other teams become your customers. Certainly there are particular dynamics at play when your customers are your peers as well but fundamentally the core principles of the “platform as a product” approach translate well across the organization. We have seen this work well inside engineering, and we start to see it in other domains of the business as well: data science & business intelligence, but also leadership, marketing, legal, HR, etc. We will cover some early examples during this talk and think ahead to what the future holds for platforms beyond engineering.

Product Teams Need A Family Too! @ Iberia SWE Fest, Mar 2023

Manuel Pais

Business and Technical Agility with Team Topologies @ CAS 2022

Manuel Pais

Las organizaciones que no se adaptan rápidamente al entorno empresarial moderno y altamente cambiante están fracasando en gran número. El aumento de la regulación, las presiones del cambio climático, la digitalización y (recientemente) la pandemia de COVID-19 están impulsando la necesidad de agilidad empresarial en organizaciones de todos los tamaños. En esta charla, explicaremos cómo los patrones y principios de Team Topologies promueven una verdadera agilidad del negocio a través de un flujo rápido de cambio de software (soportado por prácticas modernas de ingeniería), feedback rápido desde los sistemas en vivo, bajo acoplamiento sistémico y una visión de la arquitectura sociotécnica. Team Topologies está ayudando a las organizaciones de todo el mundo a adaptarse a la "nueva normalidad" y lograr una verdadera agilidad empresarial. Miraremos ejemplos concretos de cómo han evolucionado algunas empresas bajo estos patrones y principios.

Playing Tetris with Cognitive Load @ Chile Ágil meetup, Oct 2022

Manuel Pais

Equipos de productos interfuncionales autónomos y empoderados. Suena como un equipo de ensueño, ¿no? Entonces, ¿qué significa esto para los equipos de entrega de software? ¿Esperamos que un equipo así configure sus herramientas y canalizaciones de CI/CD, automatice la infraestructura, pruebe y asegure *todas las cosas* y, por supuesto, ejecute y supervise su producto en vivo? Oh, espera, hay más: necesitan entender realmente quiénes son sus clientes, qué necesitan del producto, qué está causando fricción y cuál es la viabilidad de nuestro producto como un beneficio neto para la organización. ¿Suena familiar? ¡Enhorabuena, ya estás jugando al Tetris con carga cognitiva! Quiere saber más sobre la carga cognitiva del equipo y cómo podemos hacer uso de topologías e interacciones de equipo efectivas para equilibrar y minimizar la carga cognitiva en un ecosistema de equipos. ¡Únase a esta charla y ascienda en el ranking Tetris de carga cognitiva con la ayuda de uno de los coautores del libro Team Topologies: Organizing Business and Technology Teams for Fast Flow! Del expositor: Manuel Pais es coautor de Team Topologies: Organizando equipos de negocios y tecnología para un flujo rápido. Reconocido por TechBeacon como un líder de pensamiento de DevOps, Manuel es un consultor organizacional de TI independiente y trainer, centrado en las interacciones del equipo, las prácticas de entrega y la aceleración del flujo. Manuel también es instructor de LinkedIn en Continuous Delivery. Twitter: @manupaisable LinkedIn: https://www.linkedin.com/in/manuelpais/

Keynote: Frozen DevOps? The not-so-technical Last Mile @ DevOpsDays Portugal,...

Manuel Pais

Why are so many organizations stuck in the “middle” of DevOps evolution? What’s preventing them from achieving higher levels of 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. Fundamentally, we need to supercharge the fundamental principles of DevOps: fast feedback loops, minimal waste, removing bottlenecks, and continuous learning & improvement.

Remote-first Team Interactions with Team Topologies @ Team Topologies Confere...

Manuel Pais

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 or hybrid? What should teams think about and what patterns can teams adopt to be effective when most people are not in the office? Based on the ideas from Team Topologies book and the new Remote Team Interactions Workbook, co-author Manuel Pais 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 @ DevOps Perth Meetup, Ju...

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 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 for Business and Technology Teams @ Berlin CTO...

Manuel Pais

Conway's Law is Out to Get You! @ Large Financial Group, Apr 2022

Manuel Pais

What is Platform as a Product? Clues from Team Topologies @ DevOps Porto meet...

Manuel Pais

Savvy organizations 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 organization 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 organizations 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 organizations like Uswitch and Adidas have successfully used the platform-as-product model to accelerate and simplify the delivery of software at scale.

Frozen DevOps? Team Topologies Comes to the Rescue! @ DevSecOps - London Gath...

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

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

Manuel Pais

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.

Accelerating Flow with Team Topologies & Friends @ Adaptive Organizations Wee...

Manuel Pais

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.

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/

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

Manuel Pais

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.

Organizational Trends and Patterns with Team Topologies @ LPCx Meetup, July 2021

Manuel Pais

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.

More from Manuel Pais (20)