Avoiding the CI/CD Monolith with Team Topologies @ DevOps Sydney meetup, Oct ...Manuel Pais
More than legacy technology or architecture, the emergence of monoliths often comes down to a lack of clear boundaries and responsibilities between teams.
Should every 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?
Or a CI/CD platform providing out-of-the-box solutions that can be customized by application teams to fit their specific needs?
Join me to find out what the answers to these questions have to do with cognitive load, team interactions, and the co-evolution of CI/CD boundaries and responsibilities.
Why You Need to Think About Team Design for CI/CD @Jenkins World Lisbon 2019Manuel Pais
At Jenkins World 2018, Kohsuke Kawaguchi talked about the need to move away from Jenkinsteins, those single-headed monsters that eat all our food (resources) and steal our peace of mind.
Jenkins X, Pipelines as Code, Configuration as Code, Evergreen, and Serverless Jenkins are all important initiatives to achieve modern, fast and reliable software delivery. However… there’s still something we need to talk about and that is team organization for effective continuous integration/continuous delivery.
Should every application team own and maintain their own instances and flavors of Jenkins, since it’s all code now? Or do we still need a Jenkins admin team to handle Jenkins for everyone in the department/org so they only have to worry about their own pipelines and nothing else? Or something else, like a CI/CD platform providing out-of-the-box solutions that can be customized by application teams to fit their specific needs? The answer, as you probably guessed, is: it depends!
But just like we are advancing our tools to become easier to install, run and update, we also need to think about how to design our teams and responsibilities for transparency and ownership of both the CI/CD system (it’s actually a product) itself and the application pipelines.
This talk draws on research and case studies from the book Team Topologies by Matthew Skelton and Manuel Pais (IT Revolution Press, 2019) together with first-hand consulting experience from the authors with organizations around the world.
Key takeaways:
1. Moving to fast, distributed, and reliable CI/CD systems is not just a matter of better tooling, but also clearer team design and responsibilities.
2. With “everything as code” for CI/CD, application teams can be empowered to own their CI/CD chains if they wish. But with great power comes great responsibility. We need to consider the teams’ cognitive capacity as well as organization size (which btw might change quickly).
3. By applying four fundamental topologies and three interaction modes from Team Topologies, we can describe different ways to split responsibility for our CI/CD system and decide which one best matches the organization and teams’ needs.
Forget 'Monoliths vs Microservices'; focus on Team Cognitive Load @ The Futur...Manuel Pais
The debate on monoliths vs microservices as architectural patterns for modern software systems usually focuses on technological aspects, missing crucial details around organizational strategy and team dynamics.
Should we start with a monolith and extract microservices or start with microservices? How many microservices is the right number? These kinds of questions indicate a confusion that is made worse by the perceived need to adopt lots of new technology in order to make microservices work.
The false dichotomy between monoliths and microservices helps no-one. Instead, switched-on organizations start with the team cognitive load required to build and run a part of the software system. If a team is not able to fully understand the details of a service or subsystem, there is little chance of the team being able to own and support it.
The resulting team-sized services are by definition suitable in size and complexity for a single team to own, develop, and run. No longer do we care how many lines of code there are in a single service or whether it is a “monolith”: what we care about is that a team can own and run the software effectively.
Using team cognitive load as the guiding principle - assessed by the team via measures such as supportability, deployability, testability, operability, prioritization difficulties and domain complexity - organizations can optimize for sustainable ownership and evolution of software systems.
This talk draws on research and case studies from the book Team Topologies by Matthew Skelton and Manuel Pais (IT Revolution Press, 2019) together with first-hand consulting experience from the authors with organizations around the world.
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.
Fast Flow & Organizational Evolution with Team Topologies @ Masters of Softwa...Manuel Pais
This guest lecture at the Masters of Software Engineering graduate program covers common organizational challenges to achieve fast flow and high performing teams. Key aspects of Team Topologies that are covered include the four fundamental team types, the team API, cognitive load, and the three core team interaction modes.
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
Forget Monoliths vs Microservices - Focus on Team Cognitive Load @ DevOps Per...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.
Avoiding the CI/CD Monolith with Team Topologies @ DevOps Sydney meetup, Oct ...Manuel Pais
More than legacy technology or architecture, the emergence of monoliths often comes down to a lack of clear boundaries and responsibilities between teams.
Should every 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?
Or a CI/CD platform providing out-of-the-box solutions that can be customized by application teams to fit their specific needs?
Join me to find out what the answers to these questions have to do with cognitive load, team interactions, and the co-evolution of CI/CD boundaries and responsibilities.
Why You Need to Think About Team Design for CI/CD @Jenkins World Lisbon 2019Manuel Pais
At Jenkins World 2018, Kohsuke Kawaguchi talked about the need to move away from Jenkinsteins, those single-headed monsters that eat all our food (resources) and steal our peace of mind.
Jenkins X, Pipelines as Code, Configuration as Code, Evergreen, and Serverless Jenkins are all important initiatives to achieve modern, fast and reliable software delivery. However… there’s still something we need to talk about and that is team organization for effective continuous integration/continuous delivery.
Should every application team own and maintain their own instances and flavors of Jenkins, since it’s all code now? Or do we still need a Jenkins admin team to handle Jenkins for everyone in the department/org so they only have to worry about their own pipelines and nothing else? Or something else, like a CI/CD platform providing out-of-the-box solutions that can be customized by application teams to fit their specific needs? The answer, as you probably guessed, is: it depends!
But just like we are advancing our tools to become easier to install, run and update, we also need to think about how to design our teams and responsibilities for transparency and ownership of both the CI/CD system (it’s actually a product) itself and the application pipelines.
This talk draws on research and case studies from the book Team Topologies by Matthew Skelton and Manuel Pais (IT Revolution Press, 2019) together with first-hand consulting experience from the authors with organizations around the world.
Key takeaways:
1. Moving to fast, distributed, and reliable CI/CD systems is not just a matter of better tooling, but also clearer team design and responsibilities.
2. With “everything as code” for CI/CD, application teams can be empowered to own their CI/CD chains if they wish. But with great power comes great responsibility. We need to consider the teams’ cognitive capacity as well as organization size (which btw might change quickly).
3. By applying four fundamental topologies and three interaction modes from Team Topologies, we can describe different ways to split responsibility for our CI/CD system and decide which one best matches the organization and teams’ needs.
Forget 'Monoliths vs Microservices'; focus on Team Cognitive Load @ The Futur...Manuel Pais
The debate on monoliths vs microservices as architectural patterns for modern software systems usually focuses on technological aspects, missing crucial details around organizational strategy and team dynamics.
Should we start with a monolith and extract microservices or start with microservices? How many microservices is the right number? These kinds of questions indicate a confusion that is made worse by the perceived need to adopt lots of new technology in order to make microservices work.
The false dichotomy between monoliths and microservices helps no-one. Instead, switched-on organizations start with the team cognitive load required to build and run a part of the software system. If a team is not able to fully understand the details of a service or subsystem, there is little chance of the team being able to own and support it.
The resulting team-sized services are by definition suitable in size and complexity for a single team to own, develop, and run. No longer do we care how many lines of code there are in a single service or whether it is a “monolith”: what we care about is that a team can own and run the software effectively.
Using team cognitive load as the guiding principle - assessed by the team via measures such as supportability, deployability, testability, operability, prioritization difficulties and domain complexity - organizations can optimize for sustainable ownership and evolution of software systems.
This talk draws on research and case studies from the book Team Topologies by Matthew Skelton and Manuel Pais (IT Revolution Press, 2019) together with first-hand consulting experience from the authors with organizations around the world.
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.
Fast Flow & Organizational Evolution with Team Topologies @ Masters of Softwa...Manuel Pais
This guest lecture at the Masters of Software Engineering graduate program covers common organizational challenges to achieve fast flow and high performing teams. Key aspects of Team Topologies that are covered include the four fundamental team types, the team API, cognitive load, and the three core team interaction modes.
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
Forget Monoliths vs Microservices - Focus on Team Cognitive Load @ DevOps Per...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.
Playing Tetris with Cognitive Load @ Craft Conference, Jun 2021Manuel Pais
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!
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
Product teams need a family too! Fundamental Team Topologies for Flow @ DevOp...Manuel Pais
https://devopsdays.org/events/2019-portugal/program/manuel-pais/
So you’re trying to move from agile project teams to business-aligned product teams. Everyone from the CEO to middle management is on board. Yet somehow it’s not that easy, is it? You’ve just about figured out how to split infrastructure responsibilities between teams when the next great tech for cost-effective scalability is out there and it doesn’t fit in the new model. Oh, and let’s not forget that products X and Y have no automated tests since they were developed by temporary project teams.
The underlying questions are: What are the product team’s responsibilities? How do they interact with other teams and when? The fundamental team topologies provide a framework for thinking about and aligning teams with an expected set of behaviors and responsibilities. In other words, they clarify the teams’ purpose and ways of working.
We recommend four fundamental team topologies, each with a well defined purpose and responsibilities. Along stream-aligned teams (of which product teams are a subset), the other three topologies recommended are platform, enabling, and complicated subsystem. This family of topologies provides the support system necessary for product teams to thrive.
In this talk we will see what each of these topologies brings to the table and how they enable organizations to quickly evolve and respond to both new technology and business requirements over time. We will also map some common team types in the industry to the fundamental topologies, highlighting how the same team can be either a pattern or an anti-pattern depending on the context around them.
Product Teams Need a Family Too! @ New Ways of Working - Modern Agile in Well...Manuel Pais
Are you trying to move from agile project teams to business-aligned product teams?
Everyone from the CEO to middle management is on board.
Yet somehow it’s not that easy, is it?
You’ve just about figured out how to split infrastructure responsibilities between teams when the next great tech for cost-effective scalability is out there and it doesn’t fit in the new model. Oh, and let’s not forget that products X and Y have no automated tests since they were developed by temporary project teams.
The underlying questions are: What are the product team’s responsibilities? How do they interact with other teams and when?
The fundamental team topologies provide a framework for thinking about and aligning teams with an expected set of behaviors and responsibilities. In other words, we are clarifying their purpose and ways of working.
We recommend four fundamental team topologies, each with a well defined purpose and responsibilities. Along stream-aligned teams (of which product teams are a subset), the other three topologies recommended are platform, enabling, and complicated subsystem. This family of topologies provides the support system necessary for product teams to thrive.
In this talk we will see what each of these topologies brings to the table and how they enable organizations to quickly evolve and respond to both new technology and business requirements over time.
Remote-first Team Interactions with Team Topologies @ Agile Arizona meetup, M...Manuel Pais
Remote-first work is the ” new normal ” for 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 presents some useful approaches that 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 helps organizations keep a fast flow of delivery.
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
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.
Product Teams Need a Family Too! @ School of Product Ownership, Apr 2020 MeetupManuel Pais
Autonomous product teams are key for sustainable software delivery. But what does autonomy really mean? Do we expect the team to set up CI/CD, automate infra, test/UX all the things, and, of course, run and monitor their product? And still deliver features? Four fundamental team
topologies and three interaction modes can help reduce the cognitive load on product teams.
Conway's Law Is Out to Get You! @ #PMOwfh meetup, May 2020Manuel Pais
Wednesday 20th May: We'll be looking at Conway's Law with Manuel Pais, Co-Author of 'Team Topologies: Organizing business and technology teams for fast flow'.
In this informative and enlightening session, we'll be exploring how you can use exploit Conway's law and use it to your advantage. We'll also be looking at how communication structures, cognitive load, and alignment all play a crucial role in accelerating delivery and enabling delivery teams.
How to choose tools for DevOps and Continuous Delivery - #doxlonMatthew Skelton
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/
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
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.
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.
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-26Matthew 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
Kubernetes is Not Your Platform, It's Just the Foundation @ UK Cloud Infrastr...Manuel Pais
Kubernetes helps us tame sprawling microservices architectures and address increased operational complexity. Kubernetes gives developers abstractions and APIs to deploy and run their services.
But there is a price to pay in terms of both the in-house operational expertise required and the learning curve for application teams. The elephant in the room is that to run, maintain and evolve Kubernetes, we likely need a dedicated Kubernetes team.
Is the tradeoff between better operational tools and introducing a new dependency layer on the path to production for application teams worthwhile? Are we making life easier for application teams or instead reducing their end-to-end ownership?
Regardless of all the technical benefits that Kubernetes undoubtedly brings, team interactions are still key for successfully delivering and running services. We will look at a couple of organizations that have succeeded by focusing on reducing the cognitive load for application teams.
Unfortunately, many organizations see Kubernetes as “the” platform, rather than just a technical foundation for a true internal platform. In the worst case, they mandate all teams to adopt Kubernetes, regardless of both the application teams’ and the platform’s maturity levels.
Successful Kubernetes adoption requires thinking about what a platform really means and learning which team structures and interactions work well. And evolve them over time.
Everyone is Part of Continuous Delivery @ All Day DevOps (Oct 2017)Manuel Pais
Getting full value from Continuous Delivery means catering for the needs of everyone in the organization: business, devs, ops, etc. Pipelines are excellent for visualizing work status. But even better when they increase collaboration by highlighting bottlenecks due to hand-offs between siloed teams.
Business agility with Team Topologies - NatWest Group - 2021-01-19Matthew 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.
Accidental Architects - how HR designs software systems - Team Topologies - f...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. Based on ideas in the book Team Topologies, this talk by co-author Matthew Skelton explains how and why to bring together HR and Engineering to shape team boundaries and interactions for effective software delivery.
From a talk at FlowCon 2020
Playing Tetris with Cognitive Load @ Chile Ágil meetup, Oct 2022Manuel 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/
What is platform as a product? Clues from Team Topologies - Puppetize 2020 - ...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.
Playing Tetris with Cognitive Load @ Craft Conference, Jun 2021Manuel Pais
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!
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
Product teams need a family too! Fundamental Team Topologies for Flow @ DevOp...Manuel Pais
https://devopsdays.org/events/2019-portugal/program/manuel-pais/
So you’re trying to move from agile project teams to business-aligned product teams. Everyone from the CEO to middle management is on board. Yet somehow it’s not that easy, is it? You’ve just about figured out how to split infrastructure responsibilities between teams when the next great tech for cost-effective scalability is out there and it doesn’t fit in the new model. Oh, and let’s not forget that products X and Y have no automated tests since they were developed by temporary project teams.
The underlying questions are: What are the product team’s responsibilities? How do they interact with other teams and when? The fundamental team topologies provide a framework for thinking about and aligning teams with an expected set of behaviors and responsibilities. In other words, they clarify the teams’ purpose and ways of working.
We recommend four fundamental team topologies, each with a well defined purpose and responsibilities. Along stream-aligned teams (of which product teams are a subset), the other three topologies recommended are platform, enabling, and complicated subsystem. This family of topologies provides the support system necessary for product teams to thrive.
In this talk we will see what each of these topologies brings to the table and how they enable organizations to quickly evolve and respond to both new technology and business requirements over time. We will also map some common team types in the industry to the fundamental topologies, highlighting how the same team can be either a pattern or an anti-pattern depending on the context around them.
Product Teams Need a Family Too! @ New Ways of Working - Modern Agile in Well...Manuel Pais
Are you trying to move from agile project teams to business-aligned product teams?
Everyone from the CEO to middle management is on board.
Yet somehow it’s not that easy, is it?
You’ve just about figured out how to split infrastructure responsibilities between teams when the next great tech for cost-effective scalability is out there and it doesn’t fit in the new model. Oh, and let’s not forget that products X and Y have no automated tests since they were developed by temporary project teams.
The underlying questions are: What are the product team’s responsibilities? How do they interact with other teams and when?
The fundamental team topologies provide a framework for thinking about and aligning teams with an expected set of behaviors and responsibilities. In other words, we are clarifying their purpose and ways of working.
We recommend four fundamental team topologies, each with a well defined purpose and responsibilities. Along stream-aligned teams (of which product teams are a subset), the other three topologies recommended are platform, enabling, and complicated subsystem. This family of topologies provides the support system necessary for product teams to thrive.
In this talk we will see what each of these topologies brings to the table and how they enable organizations to quickly evolve and respond to both new technology and business requirements over time.
Remote-first Team Interactions with Team Topologies @ Agile Arizona meetup, M...Manuel Pais
Remote-first work is the ” new normal ” for 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 presents some useful approaches that 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 helps organizations keep a fast flow of delivery.
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
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.
Product Teams Need a Family Too! @ School of Product Ownership, Apr 2020 MeetupManuel Pais
Autonomous product teams are key for sustainable software delivery. But what does autonomy really mean? Do we expect the team to set up CI/CD, automate infra, test/UX all the things, and, of course, run and monitor their product? And still deliver features? Four fundamental team
topologies and three interaction modes can help reduce the cognitive load on product teams.
Conway's Law Is Out to Get You! @ #PMOwfh meetup, May 2020Manuel Pais
Wednesday 20th May: We'll be looking at Conway's Law with Manuel Pais, Co-Author of 'Team Topologies: Organizing business and technology teams for fast flow'.
In this informative and enlightening session, we'll be exploring how you can use exploit Conway's law and use it to your advantage. We'll also be looking at how communication structures, cognitive load, and alignment all play a crucial role in accelerating delivery and enabling delivery teams.
How to choose tools for DevOps and Continuous Delivery - #doxlonMatthew Skelton
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/
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
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.
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.
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-26Matthew 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
Kubernetes is Not Your Platform, It's Just the Foundation @ UK Cloud Infrastr...Manuel Pais
Kubernetes helps us tame sprawling microservices architectures and address increased operational complexity. Kubernetes gives developers abstractions and APIs to deploy and run their services.
But there is a price to pay in terms of both the in-house operational expertise required and the learning curve for application teams. The elephant in the room is that to run, maintain and evolve Kubernetes, we likely need a dedicated Kubernetes team.
Is the tradeoff between better operational tools and introducing a new dependency layer on the path to production for application teams worthwhile? Are we making life easier for application teams or instead reducing their end-to-end ownership?
Regardless of all the technical benefits that Kubernetes undoubtedly brings, team interactions are still key for successfully delivering and running services. We will look at a couple of organizations that have succeeded by focusing on reducing the cognitive load for application teams.
Unfortunately, many organizations see Kubernetes as “the” platform, rather than just a technical foundation for a true internal platform. In the worst case, they mandate all teams to adopt Kubernetes, regardless of both the application teams’ and the platform’s maturity levels.
Successful Kubernetes adoption requires thinking about what a platform really means and learning which team structures and interactions work well. And evolve them over time.
Everyone is Part of Continuous Delivery @ All Day DevOps (Oct 2017)Manuel Pais
Getting full value from Continuous Delivery means catering for the needs of everyone in the organization: business, devs, ops, etc. Pipelines are excellent for visualizing work status. But even better when they increase collaboration by highlighting bottlenecks due to hand-offs between siloed teams.
Business agility with Team Topologies - NatWest Group - 2021-01-19Matthew 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.
Accidental Architects - how HR designs software systems - Team Topologies - f...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. Based on ideas in the book Team Topologies, this talk by co-author Matthew Skelton explains how and why to bring together HR and Engineering to shape team boundaries and interactions for effective software delivery.
From a talk at FlowCon 2020
Playing Tetris with Cognitive Load @ Chile Ágil meetup, Oct 2022Manuel 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/
What is platform as a product? Clues from Team Topologies - Puppetize 2020 - ...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.
WFT is platform as a product? Clues from Team Topologies - WTFinar with Conta...Matthew Skelton
From a WTFinar with Container Solutions on 2020-11-19
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.
Product Teams Need a Family Too! @ Agile Delivery Meetup, May 2020Manuel Pais
Descripción: Autonomous product teams are key for sustainable software delivery. But what does autonomy really mean? Do we expect the team to set up CI/CD, automate infra, test/UX all the things, and, of course, run and monitor their product? And still deliver features? Four fundamental team topologies and three interaction modes can help reduce the cognitive load on product teams.
Business and Technical Agility with Team Topologies, Jun 2021Manuel 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.
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.
Product Teams Need a Family Too! @ Enterprise Agile San Francisco meetup, Jul...Manuel Pais
Autonomous product teams are key to sustainable software delivery. But what does autonomy really mean? Do we expect the team to set up CI/CD, automate infra, test/UX all the things, and, of course, run and monitor their product? And still, deliver features? Four fundamental team topologies and three interaction modes can help reduce the cognitive load on product teams.
So you’re trying to move from agile project teams to business-aligned product teams. Everyone from the CEO to middle management is on board. Yet somehow it’s not that easy, is it? You’ve just about figured out how to split infrastructure responsibilities between teams when the next great tech for cost-effective scalability is out there and it doesn’t fit in the new model. Oh, and let’s not forget that products X and Y have no automated tests since they were developed by temporary project teams.
The underlying questions are: What are the product team’s responsibilities? How do they interact with other teams and when? The fundamental team topologies provide a framework for thinking about and aligning teams with an expected set of behaviors and responsibilities. In other words, we are clarifying their purpose and ways of working.
We recommend four fundamental team topologies, each with a well-defined purpose and responsibilities. Along with stream-aligned teams (of which product teams are a subset), the other three topologies recommended are platform, enabling, and complicated subsystem. This family of topologies provides the support system necessary for product teams to thrive.
In this discussion, we will see what each of these topologies brings to the table and how they enable organizations to quickly evolve and respond to both new technology and business requirements over time.
This talk draws on research and case studies from the book Team Topologies by Matthew Skelton and Manuel Pais (IT Revolution Press, 2019) together with first-hand consulting experience from the authors with organizations around the world. Team Topologies are the evolution of the highly praised DevOps Topologies, focusing on an evolutionary approach for organization design.
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.
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.
Beyond Engineering: The Future of Platforms @ CraftConf, May 2023Manuel 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.
Jay Lyman 451 ResearchBrent Beer GitHubSteven Anderson Sendachi talk about these topics:
Cloud, DevOps, agile development capability and adoption of containers are all important in both perception and reality.
Enterprise adoption of cloud computing, DevOps, agile development and containers are all growing, including production use.
Modernizing applications to SaaS & migrating them to the cloud are equally important as net-new, so-called ‘cloud-native’ applications.
Advantages and benefits of these technologies and methodologies center on: flexibility and speed, cost reduction, improvements in resiliency and reliability and fitness for new/emerging applications.
Barriers center on: lack of internal skills, immaturity, lack of familiarity, satisfaction with current technology, cost and security.
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.
How to choose tools for DevOps and Continuous Delivery - DevOps CardiffMatthew Skelton
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.
What Is Platform as a Product - Clues from Team Topologies @ AXA, Sep 2021Manuel 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.
Matthew Skelton - How to choose tools for DevOps - collaboration over automationOutlyer
skeltonthatcher.com | @matthewpskelton
Title: How to choose tools for DevOps - collaboration over automation
Matthew Skelton has been building, deploying, and operating commercial software systems since 1998. Co-founder and Principal Consultant at Skelton Thatcher Consulting Ltd, he specialises in helping organisations to adopt and sustain good practices for building and operating software systems: Continuous Delivery, DevOps, aspects of ITIL, and software operability. Matthew founded and leads the 700-member London Continuous Delivery meetup group (http://londoncd.org.uk/), and instigated the first conference in Europe dedicated to Continuous Delivery, PIPELINE Conference (http://pipelineconf.info/). He also co-facilitates the popular Experience DevOps workshop series (http://experiencedevops.org/).
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.
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.
Business and Technical Agility with Team Topologies @ CAS 2022Manuel 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.
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
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.
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.
Traditional vs Modern Internal Platforms @ Humanitec webinar, Jun 2021Manuel 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?
Remote-first Team Interactions for Business and Technology Teams @ DevOps Not...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's not much out there 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.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
13. “Despite striving to be
cross-functional, one of the thornier
problems product teams often face is
lacking some necessary
competence.”
– Peter Neumark, 2015
13
37. 37
Platform teams provide services that
enable stream-aligned teams to deliver
work with substantial autonomy
38. “A digital platform is a foundation of
self-service APIs, tools, services,
knowledge and support which are
arranged as a compelling internal
product.”
– Evan Bottcher, 2018
38
39. “A digital platform is a foundation of
self-service APIs, tools, services,
knowledge and support which are
arranged as a compelling internal
product.”
– Evan Bottcher, 2018
39
48. Free workbook coming soon
Team Topologies
for Remote Teams
48
for Remote
Teams
Sign up for news: teamtopologies.com/newsletter
Remote-first Team Interactions video:
youtube.com/watch?v=iQ6JfBt_rc4