Product Teams Need a Family Too! @ Product Camp Brazil, Dec 2021
•
1 like•136 views
This document discusses organizing teams for fast product development. It introduces the concepts of team topologies, which are the fundamental types of teams needed to build software. The main topologies are stream-aligned teams, platform teams, and facilitating teams. It also discusses the core interaction modes between teams: collaboration, X-as-a-service, and facilitating. Managing cognitive load and treating platforms as products are identified as keys to success. Stream-aligned teams focus on a single product stream while platform teams create shared tools and services to reduce cognitive load across many teams.
Report
Share
Report
Share
Download to read offline
Recommended
Product Teams Need a Family Too! @ Stockholm Engineering Leadership Meetup, J...
Talk and Q&A at Stockholm Engineering Leadership meetup on product teams, ownership, autonomy, cognitive load, types of teams and interactions.
Traditional vs Modern Internal Platforms @ Humanitec webinar, Jun 2021
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?
Business Agility with Team Topologies @ Digital Transformation London meetup,...
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/
Playing Tetris with Cognitive Load @ Craft Conference, Jun 2021
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!
Product Teams Need a Family Too - Fundamental Team Topologies for Flow @ DevO...
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.
How to choose tools for DevOps and Continuous Delivery - #doxlon
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/
Business and Technical Agility with Team Topologies @ WTF Is Cloud Native, No...
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.
Why You Need to Think About Team Design for CI/CD @Jenkins World Lisbon 2019
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.
Recommended
Product Teams Need a Family Too! @ Stockholm Engineering Leadership Meetup, J...
Talk and Q&A at Stockholm Engineering Leadership meetup on product teams, ownership, autonomy, cognitive load, types of teams and interactions.
Traditional vs Modern Internal Platforms @ Humanitec webinar, Jun 2021
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?
Business Agility with Team Topologies @ Digital Transformation London meetup,...
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/
Playing Tetris with Cognitive Load @ Craft Conference, Jun 2021
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!
Product Teams Need a Family Too - Fundamental Team Topologies for Flow @ DevO...
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.
How to choose tools for DevOps and Continuous Delivery - #doxlon
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/
Business and Technical Agility with Team Topologies @ WTF Is Cloud Native, No...
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.
Why You Need to Think About Team Design for CI/CD @Jenkins World Lisbon 2019
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.
Product Teams Need a Family Too! @ School of Product Ownership, Apr 2020 Meetup
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.
Remote first team interactions with Team Topologies - IT Revolution webinar -...
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.
What is platform as a product? Clues from Team Topologies - WTFinar with Cont...
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.
What Is Platform as a Product - Clues from Team Topologies @ AXA, Sep 2021
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.
Accelerating Flow with Team Topologies & Friends @ Adaptive Organizations Wee...
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.
Avoiding the CI/CD Monolith with Team Design & Evolution @ London CD meetup, ...
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.
Monoliths vs Microservices is the Wrong Question; Start with Team Cognitive L...
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
Business and Technical Agility with Team Topologies, Jun 2021
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.
Business agility with Team Topologies - NatWest Group - 2021-01-19
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.
Team Topologies in action - early results from industry - DOES Las Vegas 2020...
Since the book Team Topologies was published in 2019, organizations around the world have started to adopt Team Topologies principles and practices like Stream-aligned teams, modern platforms, well-defined team interactions, and team cognitive load as a key driver for fast software delivery and operations.
We will look at examples from these organizations:
- Footasylum gives fashion-focused youth a multi-branded retail experience mixing global sportswear household names with emerging brands and its own stable of in-house labels. Founded in 2005, Footasylum now has 70 stores across the UK and a thriving ecommerce platform, with revenue of £260m per annum and over 2500 employees. Footasylum used Team Topologies patterns to revolutionize their ecommerce platform.
- PureGym is Britain’s largest gym chain - the first to gain over 1 million members. As PureGym expanded, so did the need for software to enable their members to book and manage gym sessions. Since 2019, PureGym has re-aligned its teams and team interactions based on Team Topologies patterns, helping to scale the engineering teams and improve flow.
- uSwitch / RVU, one of the UK’s leading consumer price comparison websites, has grown a modern platform from scratch, allowing stream-aligned teams to focus on consumers needs, offloading infrastructure provisioning concerns to the platform which also provides cross-cutting services around scalability, security and data management
- Wealth Wizards is a UK company making financial advice affordable and accessible to everyone through online tools and apps. The engineering division at Wealth Wizards has used the Team Topologies ideas around team cognitive load to help right-size their teams and align teams to the most important flows of business change.
For each of these examples, we explore how the ideas and patterns in Team Topologies were useful to the organization and the results of the changes.
Forget monoliths vs microservices - focus on team cognitive load - Team Topol...
The “monoliths vs microservices” debate often focuses on technological aspects, ignoring strategy and team dynamics. Instead of technology, smart-thinking organizations are beginning with team cognitive load as the guiding principle for modern software. In this talk we explain how and why, based on material from the book Team Topologies by Matthew Skelton and Manuel Pais.
Business and technical agility with Team Topologies - QCon Plus - 2021-05-26
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
Product Teams Need a Family Too! @ Enterprise Agile San Francisco meetup, Jul...
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.
WFT is platform as a product? Clues from Team Topologies - WTFinar with Conta...
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.
Team Topologies at Parts Unlimited, The Unicorn Project Book Club, Jan 2020
Executive summary from the Team Topologies report on org design and team dynamics at Parts Unlimited, as requested by Maxine.
Accidental Architects - how HR designs software systems - Team Topologies - e...
Who designs the architecture of your software systems? Conway's Law suggests that HR may be strongly shaping software architecture by deciding how teams are composed and interrelate. Do you want HR designing your software architecture?
Organization architecture and software system architecture need to be co-designed to avoid friction from Conway's Law.
---
From a talk given by Matthew Skelton at Elabor8- 2020-05-27
Product teams need a family too! Fundamental Team Topologies for Flow @ DevOp...
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.
Continuous Delivery at scale - Matthew Skelton - NHS Digital agile CoP - Marc...
Continuous Delivery practices have increasingly become “table stakes” for effective software delivery since the publication of the book Continuous Delivery by Jez Humble and Dave Farley in 2010. The combination of sound technical practices and a scientific approach to testing and feature development has led to significant success with software delivery with organisations around the world.
However, in large organisations with many teams and many different suppliers, there are also many ideas about what Continuous Delivery is. This variety of approaches and assumptions can lead to conflicts around deployments, testing, releasing, and operations, resulting in a macro-level sub-optimal flow of change.
In this talk, Matthew Skelton will share some insights from his time spent as Engineering Lead at a large GOV.UK department during most of 2018. There he championed Continuous Delivery practices across 70+ teams and 7 locations, helping to raise standards for software operability, Developer Experience (DevEx), testing, deployments, and inter-team communications. He will share some practical techniques for getting Continuous Delivery working at scale.
Playing Tetris with Cognitive Load @ QEDx internal conference (keynote), Jan ...
This Team Topologies talk covers the issues around identifying, limiting and addressing cognitive load for cross-functional stream-aligned teams.
Product Teams Need a Family Too! @ Agile Delivery Meetup, May 2020
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.
More Related Content
What's hot
Product Teams Need a Family Too! @ School of Product Ownership, Apr 2020 Meetup
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.
Remote first team interactions with Team Topologies - IT Revolution webinar -...
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.
What is platform as a product? Clues from Team Topologies - WTFinar with Cont...
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.
What Is Platform as a Product - Clues from Team Topologies @ AXA, Sep 2021
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.
Accelerating Flow with Team Topologies & Friends @ Adaptive Organizations Wee...
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.
Avoiding the CI/CD Monolith with Team Design & Evolution @ London CD meetup, ...
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.
Monoliths vs Microservices is the Wrong Question; Start with Team Cognitive L...
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
Business and Technical Agility with Team Topologies, Jun 2021
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.
Business agility with Team Topologies - NatWest Group - 2021-01-19
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.
Team Topologies in action - early results from industry - DOES Las Vegas 2020...
Since the book Team Topologies was published in 2019, organizations around the world have started to adopt Team Topologies principles and practices like Stream-aligned teams, modern platforms, well-defined team interactions, and team cognitive load as a key driver for fast software delivery and operations.
We will look at examples from these organizations:
- Footasylum gives fashion-focused youth a multi-branded retail experience mixing global sportswear household names with emerging brands and its own stable of in-house labels. Founded in 2005, Footasylum now has 70 stores across the UK and a thriving ecommerce platform, with revenue of £260m per annum and over 2500 employees. Footasylum used Team Topologies patterns to revolutionize their ecommerce platform.
- PureGym is Britain’s largest gym chain - the first to gain over 1 million members. As PureGym expanded, so did the need for software to enable their members to book and manage gym sessions. Since 2019, PureGym has re-aligned its teams and team interactions based on Team Topologies patterns, helping to scale the engineering teams and improve flow.
- uSwitch / RVU, one of the UK’s leading consumer price comparison websites, has grown a modern platform from scratch, allowing stream-aligned teams to focus on consumers needs, offloading infrastructure provisioning concerns to the platform which also provides cross-cutting services around scalability, security and data management
- Wealth Wizards is a UK company making financial advice affordable and accessible to everyone through online tools and apps. The engineering division at Wealth Wizards has used the Team Topologies ideas around team cognitive load to help right-size their teams and align teams to the most important flows of business change.
For each of these examples, we explore how the ideas and patterns in Team Topologies were useful to the organization and the results of the changes.
Forget monoliths vs microservices - focus on team cognitive load - Team Topol...
The “monoliths vs microservices” debate often focuses on technological aspects, ignoring strategy and team dynamics. Instead of technology, smart-thinking organizations are beginning with team cognitive load as the guiding principle for modern software. In this talk we explain how and why, based on material from the book Team Topologies by Matthew Skelton and Manuel Pais.
Business and technical agility with Team Topologies - QCon Plus - 2021-05-26
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
Product Teams Need a Family Too! @ Enterprise Agile San Francisco meetup, Jul...
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.
WFT is platform as a product? Clues from Team Topologies - WTFinar with Conta...
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.
Team Topologies at Parts Unlimited, The Unicorn Project Book Club, Jan 2020
Executive summary from the Team Topologies report on org design and team dynamics at Parts Unlimited, as requested by Maxine.
Accidental Architects - how HR designs software systems - Team Topologies - e...
Who designs the architecture of your software systems? Conway's Law suggests that HR may be strongly shaping software architecture by deciding how teams are composed and interrelate. Do you want HR designing your software architecture?
Organization architecture and software system architecture need to be co-designed to avoid friction from Conway's Law.
---
From a talk given by Matthew Skelton at Elabor8- 2020-05-27
Product teams need a family too! Fundamental Team Topologies for Flow @ DevOp...
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.
Continuous Delivery at scale - Matthew Skelton - NHS Digital agile CoP - Marc...
Continuous Delivery practices have increasingly become “table stakes” for effective software delivery since the publication of the book Continuous Delivery by Jez Humble and Dave Farley in 2010. The combination of sound technical practices and a scientific approach to testing and feature development has led to significant success with software delivery with organisations around the world.
However, in large organisations with many teams and many different suppliers, there are also many ideas about what Continuous Delivery is. This variety of approaches and assumptions can lead to conflicts around deployments, testing, releasing, and operations, resulting in a macro-level sub-optimal flow of change.
In this talk, Matthew Skelton will share some insights from his time spent as Engineering Lead at a large GOV.UK department during most of 2018. There he championed Continuous Delivery practices across 70+ teams and 7 locations, helping to raise standards for software operability, Developer Experience (DevEx), testing, deployments, and inter-team communications. He will share some practical techniques for getting Continuous Delivery working at scale.
What's hot (20)
Product Teams Need a Family Too! @ School of Product Ownership, Apr 2020 Meetup
Product Teams Need a Family Too! @ School of Product Ownership, Apr 2020 Meetup
Remote first team interactions with Team Topologies - IT Revolution webinar -...
Remote first team interactions with Team Topologies - IT Revolution webinar -...
What is platform as a product? Clues from Team Topologies - WTFinar with Cont...
What is platform as a product? Clues from Team Topologies - WTFinar with Cont...
What Is Platform as a Product - Clues from Team Topologies @ AXA, Sep 2021
What Is Platform as a Product - Clues from Team Topologies @ AXA, Sep 2021
Accelerating Flow with Team Topologies & Friends @ Adaptive Organizations Wee...
Accelerating Flow with Team Topologies & Friends @ Adaptive Organizations Wee...
Avoiding the CI/CD Monolith with Team Design & Evolution @ London CD meetup, ...
Avoiding the CI/CD Monolith with Team Design & Evolution @ London CD meetup, ...
Monoliths vs Microservices is the Wrong Question; Start with Team Cognitive L...
Monoliths vs Microservices is the Wrong Question; Start with Team Cognitive L...
Business and Technical Agility with Team Topologies, Jun 2021
Business and Technical Agility with Team Topologies, Jun 2021
Business agility with Team Topologies - NatWest Group - 2021-01-19
Business agility with Team Topologies - NatWest Group - 2021-01-19
Team Topologies in action - early results from industry - DOES Las Vegas 2020...
Team Topologies in action - early results from industry - DOES Las Vegas 2020...
Forget monoliths vs microservices - focus on team cognitive load - Team Topol...
Forget monoliths vs microservices - focus on team cognitive load - Team Topol...
Business and technical agility with Team Topologies - QCon Plus - 2021-05-26
Business and technical agility with Team Topologies - QCon Plus - 2021-05-26
Product Teams Need a Family Too! @ Enterprise Agile San Francisco meetup, Jul...
Product Teams Need a Family Too! @ Enterprise Agile San Francisco meetup, Jul...
WFT is platform as a product? Clues from Team Topologies - WTFinar with Conta...
WFT is platform as a product? Clues from Team Topologies - WTFinar with Conta...
Team Topologies at Parts Unlimited, The Unicorn Project Book Club, Jan 2020
Team Topologies at Parts Unlimited, The Unicorn Project Book Club, Jan 2020
Accidental Architects - how HR designs software systems - Team Topologies - e...
Accidental Architects - how HR designs software systems - Team Topologies - e...
Product teams need a family too! Fundamental Team Topologies for Flow @ DevOp...
Product teams need a family too! Fundamental Team Topologies for Flow @ DevOp...
Continuous Delivery at scale - Matthew Skelton - NHS Digital agile CoP - Marc...
Continuous Delivery at scale - Matthew Skelton - NHS Digital agile CoP - Marc...
Similar to Product Teams Need a Family Too! @ Product Camp Brazil, Dec 2021
Playing Tetris with Cognitive Load @ QEDx internal conference (keynote), Jan ...
This Team Topologies talk covers the issues around identifying, limiting and addressing cognitive load for cross-functional stream-aligned teams.
Product Teams Need a Family Too! @ Agile Delivery Meetup, May 2020
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.
Product Teams Need a Family Too! @ New Ways of Working - Modern Agile in Well...
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.
Product Teams Need A Family Too! @ Iberia SWE Fest, Mar 2023
Upgrade of the "Product Teams Need A Family Too!" talk with new insights and techniques from the last few years.
Keynote@CADE2018_HalukDemirkan
The 5th Competitive Advantage in the Digital Economy (CADE)
June 18-20, 2018: Venice, Italy
What is platform as a product? Clues from Team Topologies - Puppetize 2020 - ...
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.
Beyond Engineering: The Future of Platforms @ CraftConf, May 2023
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.
Playing Tetris with Cognitive Load @ Chile Ágil meetup, Oct 2022
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/
Fast Flow & Organizational Evolution with Team Topologies @ Masters of Softwa...
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.
Matthew Skelton_What is Platform as a Product_ Clues from Team Topologies - D...
What Is Platform as a Product? - Matthew Skelton
Five Key Focus Areas for New-Age Collaboration
Virtually any enterprise can benefit greatly from deploying new-age organizations' collaboration technologies and systems. We review the tools and activities available for collaborating on five levels: within a program, within an organization, between channels, within the extended enterprise and with the external world.
Oracle connect zone case study
Voted third in ‘105 Crucial Websites on Data Centers for IT Specialists’, by Technologyschools.org, ‘The Future of the Data Center’ is an Oracle sponsored social portal created by IDG Connect. Through a new white paper, 24 blogs and a targeted email campaign, this delivered 561 leads from 26 countries in 6 months.
Situational applications and their role in enterprise it strategy
In this article a describe how situational applications have come of age through enterprise situational applications platforms - and how they are helping organizations to rationalize IT platforms and empower innovation by producing tens if not hundreds of applications
Not Actually a DevOps Talk, or, Beyond “Survival is Not Mandatory”
SpringOne Platform 2017
Michael Cote, Pivotal
"Most people putting DevOps in place have only the foggiest notion of what it is beyond a better mousetrap, and something about 'culture.' This talk uses failures and successes from DevOps-practicing organizations to give advice from the real world on getting DevOps started at your organization.
“DevOps” has developed a vulgar definition that’s come to mean “whatever the things are we do that makes IT better.” While it’s annoying to have to spend the first 10 minutes of any conversation calibrating on what “DevOps” means, this points towards a broader need: organizations are desperate to improve how they create, deploy, and manage their custom written software. The goals of DevOps align perfectly with this need, though as organizations who try to “scale” DevOps are finding, DevOps doesn’t solve all of your problems. This talk will cover this framing of DevOps and then walk through several case studies of how (mostly large, but some medium and small) organizations are failing and succeeding at applying DevOps. In doing so, this talk provides advice for high level planning and then daily tactics for not only “doing the DevOps,” but improving the way organizations manage their stable of software."
Keynote: Frozen DevOps? The not-so-technical Last Mile @ DevOpsDays Portugal,...
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.
O'Reilly ebook: Machine Learning at Enterprise Scale | Qubole
Real-world data science practitioners offer perspectives and advice on six common Machine Learning problems
https://www.qubole.com/resources/ebooks/oreilly-ebook-machine-learning-at-enterprise-scale
What is Platform as a Product? Clues from Team Topologies @ DevOps Porto meet...
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.
Pervasive, intelligent cloud ecosystems, spectacular firms and frontier firms...
Pervasive, intelligent cloud ecosystems, spectacular firms and frontier firms...Economic Strategy Institute
This is a discussion of how firms that build strong skills in software development and data analytics, especially intelligent analytics, will dominate their industries in the next few years. Similar to Product Teams Need a Family Too! @ Product Camp Brazil, Dec 2021 (20)
Playing Tetris with Cognitive Load @ QEDx internal conference (keynote), Jan ...
Playing Tetris with Cognitive Load @ QEDx internal conference (keynote), Jan ...
Product Teams Need a Family Too! @ Agile Delivery Meetup, May 2020
Product Teams Need a Family Too! @ Agile Delivery Meetup, May 2020
Product Teams Need a Family Too! @ New Ways of Working - Modern Agile in Well...
Product Teams Need a Family Too! @ New Ways of Working - Modern Agile in Well...
Product Teams Need A Family Too! @ Iberia SWE Fest, Mar 2023
Product Teams Need A Family Too! @ Iberia SWE Fest, Mar 2023
What is platform as a product? Clues from Team Topologies - Puppetize 2020 - ...
What is platform as a product? Clues from Team Topologies - Puppetize 2020 - ...
Beyond Engineering: The Future of Platforms @ CraftConf, May 2023
Beyond Engineering: The Future of Platforms @ CraftConf, May 2023
Playing Tetris with Cognitive Load @ Chile Ágil meetup, Oct 2022
Playing Tetris with Cognitive Load @ Chile Ágil meetup, Oct 2022
Fast Flow & Organizational Evolution with Team Topologies @ Masters of Softwa...
Fast Flow & Organizational Evolution with Team Topologies @ Masters of Softwa...
Matthew Skelton_What is Platform as a Product_ Clues from Team Topologies - D...
Matthew Skelton_What is Platform as a Product_ Clues from Team Topologies - D...
Strategic Advantage and the Microsoft Application Platform (1)
Strategic Advantage and the Microsoft Application Platform (1)
Situational applications and their role in enterprise it strategy
Situational applications and their role in enterprise it strategy
Not Actually a DevOps Talk, or, Beyond “Survival is Not Mandatory”
Not Actually a DevOps Talk, or, Beyond “Survival is Not Mandatory”
Keynote: Frozen DevOps? The not-so-technical Last Mile @ DevOpsDays Portugal,...
Keynote: Frozen DevOps? The not-so-technical Last Mile @ DevOpsDays Portugal,...
O'Reilly ebook: Machine Learning at Enterprise Scale | Qubole
O'Reilly ebook: Machine Learning at Enterprise Scale | Qubole
What is Platform as a Product? Clues from Team Topologies @ DevOps Porto meet...
What is Platform as a Product? Clues from Team Topologies @ DevOps Porto meet...
Pervasive, intelligent cloud ecosystems, spectacular firms and frontier firms...
Pervasive, intelligent cloud ecosystems, spectacular firms and frontier firms...
More from Manuel Pais
Accelerating Flow with Team Topologies & Friends @ Wroclaw Kanban, Lean & Cof...
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 2022
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...
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...
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...
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.
Conway's Law is Out to Get You! @ Large Financial Group, Apr 2022
Based on the ideas from Team Topologies, this talk covers:
1. Conway's Law
2. Team Cognitive Load
3. Stream-Aligned Teams
4. Team API
Frozen DevOps? Team Topologies Comes to the Rescue! @ DevSecOps - London Gath...
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
Frozen DevOps? Team Topologies Comes to the Rescue! @ DevOpsDays Poznan, Oct ...
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
Organizational Trends and Patterns with Team Topologies @ LPCx Meetup, July 2021
Intro to Organisations & Team Topologies
Kubernetes is Not Your Platform, It's Just the Foundation @ UK Cloud Infrastr...
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.
Avoiding the CI/CD Monolith with Team Topologies @ DevOps Sydney meetup, Oct ...
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.
Forget Monoliths vs Microservices - Focus on Team Cognitive Load @ DevOps Per...
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.
Remote-first Team Interactions for Business and Technology Teams @ DevOps Not...
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.
More from Manuel Pais (13)
Accelerating Flow with Team Topologies & Friends @ Wroclaw Kanban, Lean & Cof...
Accelerating Flow with Team Topologies & Friends @ Wroclaw Kanban, Lean & Cof...
Business and Technical Agility with Team Topologies @ CAS 2022
Business and Technical Agility with Team Topologies @ CAS 2022
Remote-first Team Interactions with Team Topologies @ Team Topologies Confere...
Remote-first Team Interactions with Team Topologies @ Team Topologies Confere...
Remote-first Team Interactions with Team Topologies @ DevOps Perth Meetup, Ju...
Remote-first Team Interactions with Team Topologies @ DevOps Perth Meetup, Ju...
Remote-first Team Interactions for Business and Technology Teams @ Berlin CTO...
Remote-first Team Interactions for Business and Technology Teams @ Berlin CTO...
Conway's Law is Out to Get You! @ Large Financial Group, Apr 2022
Conway's Law is Out to Get You! @ Large Financial Group, Apr 2022
Frozen DevOps? Team Topologies Comes to the Rescue! @ DevSecOps - London Gath...
Frozen DevOps? Team Topologies Comes to the Rescue! @ DevSecOps - London Gath...
Frozen DevOps? Team Topologies Comes to the Rescue! @ DevOpsDays Poznan, Oct ...
Frozen DevOps? Team Topologies Comes to the Rescue! @ DevOpsDays Poznan, Oct ...
Organizational Trends and Patterns with Team Topologies @ LPCx Meetup, July 2021
Organizational Trends and Patterns with Team Topologies @ LPCx Meetup, July 2021
Kubernetes is Not Your Platform, It's Just the Foundation @ UK Cloud Infrastr...
Kubernetes is Not Your Platform, It's Just the Foundation @ UK Cloud Infrastr...
Avoiding the CI/CD Monolith with Team Topologies @ DevOps Sydney meetup, Oct ...
Avoiding the CI/CD Monolith with Team Topologies @ DevOps Sydney meetup, Oct ...
Forget Monoliths vs Microservices - Focus on Team Cognitive Load @ DevOps Per...
Forget Monoliths vs Microservices - Focus on Team Cognitive Load @ DevOps Per...
Remote-first Team Interactions for Business and Technology Teams @ DevOps Not...
Remote-first Team Interactions for Business and Technology Teams @ DevOps Not...
Recently uploaded
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
PHP Frameworks: I want to break free (IPC Berlin 2024)
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
GenAISummit 2024 May 28 Sri Ambati Keynote: AGI Belongs to The Community in O...
“AGI should be open source and in the public domain at the service of humanity and the planet.”
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Enhancing Performance with Globus and the Science DMZ
ESnet has led the way in helping national facilities—and many other institutions in the research community—configure Science DMZs and troubleshoot network issues to maximize data transfer performance. In this talk we will present a summary of approaches and tips for getting the most out of your network infrastructure using Globus Connect Server.
Securing your Kubernetes cluster_ a step-by-step guide to success !
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
The Metaverse and AI: how can decision-makers harness the Metaverse for their...
The Metaverse is popularized in science fiction, and now it is becoming closer to being a part of our daily lives through the use of social media and shopping companies. How can businesses survive in a world where Artificial Intelligence is becoming the present as well as the future of technology, and how does the Metaverse fit into business strategy when futurist ideas are developing into reality at accelerated rates? How do we do this when our data isn't up to scratch? How can we move towards success with our data so we are set up for the Metaverse when it arrives?
How can you help your company evolve, adapt, and succeed using Artificial Intelligence and the Metaverse to stay ahead of the competition? What are the potential issues, complications, and benefits that these technologies could bring to us and our organizations? In this session, Jen Stirrup will explain how to start thinking about these technologies as an organisation.
Climate Impact of Software Testing at Nordic Testing Days
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
GraphRAG is All You need? LLM & Knowledge Graph
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
Accelerate your Kubernetes clusters with Varnish Caching
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.
UiPath Community Day Dubai: AI at Work..
Welcome to the first live UiPath Community Day Dubai! Join us for this unique occasion to meet our local and global UiPath Community and leaders. You will get a full view of the MEA region's automation landscape and the AI Powered automation technology capabilities of UiPath. Also, hosted by our local partners Marc Ellis, you will enjoy a half-day packed with industry insights and automation peers networking.
📕 Curious on our agenda? Wait no more!
10:00 Welcome note - UiPath Community in Dubai
Lovely Sinha, UiPath Community Chapter Leader, UiPath MVPx3, Hyper-automation Consultant, First Abu Dhabi Bank
10:20 A UiPath cross-region MEA overview
Ashraf El Zarka, VP and Managing Director MEA, UiPath
10:35: Customer Success Journey
Deepthi Deepak, Head of Intelligent Automation CoE, First Abu Dhabi Bank
11:15 The UiPath approach to GenAI with our three principles: improve accuracy, supercharge productivity, and automate more
Boris Krumrey, Global VP, Automation Innovation, UiPath
12:15 To discover how Marc Ellis leverages tech-driven solutions in recruitment and managed services.
Brendan Lingam, Director of Sales and Business Development, Marc Ellis
Video Streaming: Then, Now, and in the Future
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Recently uploaded (20)
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf
FIDO Alliance Osaka Seminar: FIDO Security Aspects.pdf
FIDO Alliance Osaka Seminar: FIDO Security Aspects.pdf
Monitoring Java Application Security with JDK Tools and JFR Events
Monitoring Java Application Security with JDK Tools and JFR Events
Transcript: Selling digital books in 2024: Insights from industry leaders - T...
Transcript: Selling digital books in 2024: Insights from industry leaders - T...
PHP Frameworks: I want to break free (IPC Berlin 2024)
PHP Frameworks: I want to break free (IPC Berlin 2024)
GenAISummit 2024 May 28 Sri Ambati Keynote: AGI Belongs to The Community in O...
GenAISummit 2024 May 28 Sri Ambati Keynote: AGI Belongs to The Community in O...
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Free Complete Python - A step towards Data Science
Free Complete Python - A step towards Data Science
Enhancing Performance with Globus and the Science DMZ
Enhancing Performance with Globus and the Science DMZ
Securing your Kubernetes cluster_ a step-by-step guide to success !
Securing your Kubernetes cluster_ a step-by-step guide to success !
The Metaverse and AI: how can decision-makers harness the Metaverse for their...
The Metaverse and AI: how can decision-makers harness the Metaverse for their...
Climate Impact of Software Testing at Nordic Testing Days
Climate Impact of Software Testing at Nordic Testing Days
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
Accelerate your Kubernetes clusters with Varnish Caching
Accelerate your Kubernetes clusters with Varnish Caching
Product Teams Need a Family Too! @ Product Camp Brazil, Dec 2021
- 1. TeamTopologies.com @TeamTopologies Product Teams Need a Family Too! Manuel Pais @manupaisable Product Camp - 8 Dec 2021
- 2. Team Topologies 3 Organizing business and technology teams for fast flow Matthew Skelton & Manuel Pais IT Revolution Press, 2019 teamtopologies.com/book
- 3. “innovative tools and concepts for structuring the next generation digital operating model” Charles T. Betz, Principal Analyst, Forrester Research 4
- 4. “Great products emerge from empowered, fully cross-functional teams.” – John Cutler, 2019 5
- 6. “Organizations should not expect to become highly evolved just because they use cloud and automation… They are held back by organizational structure and dynamics” – State of DevOps Report, 2021 7
- 7. “need to address organizational and team aspects, namely helping teams clarify their mission, primary customers, interfaces, and what makes for healthy interactions with others.” – State of DevOps Report, 2021 8
- 10. “Great products emerge from empowered, fully cross-functional teams.” – John Cutler, 2019 12
- 11. “Despite striving to be cross-functional, one of the thornier problems product teams often face is lacking some necessary competence.” – Peter Neumark, 2015 13
- 20. 22 autonomy
- 21. 23 capabilities
- 22. 24 How to alleviate the tension between: team autonomy (increases flow) and lack of capabilities (decreases flow)
- 24. 26 in-flow blocking dependencies based on handovers out-of-flow non-blocking dependencies based on capabilities
- 25. 27
- 26. “Highly evolved firms have a small number of team types whose role and responsibilities are clearly understood by their adjacent teams.” – State of DevOps Report, 2021 28
- 27. 29
- 29. “Cognitive load is the total amount of mental effort being used in the working memory” - John Sweller 31
- 30. 32 Cognitive load Intrinsic: “How is a class defined in Java?”
- 32. 34 Cognitive load Intrinsic (skills) Extraneous: “How do I deploy this app again?”
- 33. 35 Cognitive load Intrinsic (skills) Extraneous (mechanics) Germane: “How do bank transfers work?”
- 34. 36 Cognitive load Intrinsic (skills) Extraneous (mechanics) Germane (customer focus)
- 35. 39 Cognitive load Intrinsic (skills) Extraneous (mechanics) Germane (customer focus)
- 36. 4 key metrics: ‘Accelerate’ 40 lead time deployment frequency mean time to restore (MTTR) change fail percentage
- 37. 41
- 38. “Highly evolved firms use a combination of stream-aligned teams and platform teams as the most effective way to manage team cognitive load at scale” – State of DevOps Report, 2021 42
- 40. “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 44
- 41. “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 45
- 42. A good platform is treated as a product (reliable, usable, fit for purpose) 46
- 44. “Not every platform team is automatically successful, but the successful ones treat their platform as a product.” – State of DevOps Report, 2021 48
- 45. 49
- 47. 51
- 48. 52
- 50. 54
- 51. 55 Collaboration: 2 teams working together X-as-a-Service: 1 provides, 1 consumes Facilitating: 1 team helps another
- 52. 56
- 53. 57 When used with care, these are the only four fundamental team topologies and three core interaction modes needed to build and run modern software systems.
- 54. Also important 59 Team-sized software Avoid Conway mismatches Organizational sensing Thinnest Viable Platform (TVP)
- 55. Free Resources 62 teamtopologies.com/learn (slides, videos, articles) teamtopologies.com/infographics (templates, assessments, etc)
- 56. Workbook coming in 2022... Remote team interactions 63 Resources: teamtopologies.com/remote-first
- 58. Thank you! 67 Matthew Skelton, Conflux @matthewpskelton Manuel Pais, FlowOnRails @manupaisable teamtopologies.com @teamtopologies