Product Teams Need a Family Too! @ New Ways of Working - Modern Agile in Wellington meetup, Sep 2020
•
1 like•1,771 views
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.
Report
Share
Report
Share
Download to read offline
Recommended
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.
Conway's Law Is Out to Get You! @ #PMOwfh meetup, May 2020
Wednesday 20th May: We'll be looking at Conway's Law with Manuel Pais, Co-Author of 'Team Topologies: Organizing business and technology teams for fast flow'.
In this informative and enlightening session, we'll be exploring how you can use exploit Conway's law and use it to your advantage. We'll also be looking at how communication structures, cognitive load, and alignment all play a crucial role in accelerating delivery and enabling delivery teams.
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
Forget 'Monoliths vs Microservices'; focus on Team Cognitive Load @ The Futur...
The debate on monoliths vs microservices as architectural patterns for modern software systems usually focuses on technological aspects, missing crucial details around organizational strategy and team dynamics.
Should we start with a monolith and extract microservices or start with microservices? How many microservices is the right number? These kinds of questions indicate a confusion that is made worse by the perceived need to adopt lots of new technology in order to make microservices work.
The false dichotomy between monoliths and microservices helps no-one. Instead, switched-on organizations start with the team cognitive load required to build and run a part of the software system. If a team is not able to fully understand the details of a service or subsystem, there is little chance of the team being able to own and support it.
The resulting team-sized services are by definition suitable in size and complexity for a single team to own, develop, and run. No longer do we care how many lines of code there are in a single service or whether it is a “monolith”: what we care about is that a team can own and run the software effectively.
Using team cognitive load as the guiding principle - assessed by the team via measures such as supportability, deployability, testability, operability, prioritization difficulties and domain complexity - organizations can optimize for sustainable ownership and evolution of software systems.
This talk draws on research and case studies from the book Team Topologies by Matthew Skelton and Manuel Pais (IT Revolution Press, 2019) together with first-hand consulting experience from the authors with organizations around the world.
Remote-first Team Interactions with Team Topologies @ Agile Arizona meetup, M...
Remote-first work is the ” new normal ” for around the world. There is no shortage of advice on how individual teams can bond and work effectively remotely.
However, there is not much on how to address remote interactions between different teams that need to collaborate remotely, as part of the same value stream. Moving from the physical to the online world can further expose pre-existing interaction problems, increase wait times and slow down delivery and possibly response to incidents.
Based on the ideas from Team Topologies, Manuel Pais presents some useful approaches that clarify and evolve inter-team interactions and communication in this remote-first world.
Designing "Team APIs" and virtual communication channels that promote relevant team interactions while minimizing communication overhead helps organizations keep a fast flow of delivery.
Following well-defined interaction patterns and architecting for team-first software boundaries will also help reduce communication overhead, clarify expectations on teams, and increase visibility of on-going work and support.
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.
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.
Remote-first Team Interactions for Business and Technology Teams @ NYC Scrum...
This document discusses concepts from the book "Team Topologies" about organizing teams for remote work. It promotes defining team dependencies, interactions, and boundaries to improve collaboration. It argues organizational charts don't reflect reality and interactions should be driven by real needs, not formal processes. It also advocates clarifying communication purposes and channels, using feedback to evolve, and replacing rigid support structures with swarming to resolve incidents.
Recommended
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.
Conway's Law Is Out to Get You! @ #PMOwfh meetup, May 2020
Wednesday 20th May: We'll be looking at Conway's Law with Manuel Pais, Co-Author of 'Team Topologies: Organizing business and technology teams for fast flow'.
In this informative and enlightening session, we'll be exploring how you can use exploit Conway's law and use it to your advantage. We'll also be looking at how communication structures, cognitive load, and alignment all play a crucial role in accelerating delivery and enabling delivery teams.
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
Forget 'Monoliths vs Microservices'; focus on Team Cognitive Load @ The Futur...
The debate on monoliths vs microservices as architectural patterns for modern software systems usually focuses on technological aspects, missing crucial details around organizational strategy and team dynamics.
Should we start with a monolith and extract microservices or start with microservices? How many microservices is the right number? These kinds of questions indicate a confusion that is made worse by the perceived need to adopt lots of new technology in order to make microservices work.
The false dichotomy between monoliths and microservices helps no-one. Instead, switched-on organizations start with the team cognitive load required to build and run a part of the software system. If a team is not able to fully understand the details of a service or subsystem, there is little chance of the team being able to own and support it.
The resulting team-sized services are by definition suitable in size and complexity for a single team to own, develop, and run. No longer do we care how many lines of code there are in a single service or whether it is a “monolith”: what we care about is that a team can own and run the software effectively.
Using team cognitive load as the guiding principle - assessed by the team via measures such as supportability, deployability, testability, operability, prioritization difficulties and domain complexity - organizations can optimize for sustainable ownership and evolution of software systems.
This talk draws on research and case studies from the book Team Topologies by Matthew Skelton and Manuel Pais (IT Revolution Press, 2019) together with first-hand consulting experience from the authors with organizations around the world.
Remote-first Team Interactions with Team Topologies @ Agile Arizona meetup, M...
Remote-first work is the ” new normal ” for around the world. There is no shortage of advice on how individual teams can bond and work effectively remotely.
However, there is not much on how to address remote interactions between different teams that need to collaborate remotely, as part of the same value stream. Moving from the physical to the online world can further expose pre-existing interaction problems, increase wait times and slow down delivery and possibly response to incidents.
Based on the ideas from Team Topologies, Manuel Pais presents some useful approaches that clarify and evolve inter-team interactions and communication in this remote-first world.
Designing "Team APIs" and virtual communication channels that promote relevant team interactions while minimizing communication overhead helps organizations keep a fast flow of delivery.
Following well-defined interaction patterns and architecting for team-first software boundaries will also help reduce communication overhead, clarify expectations on teams, and increase visibility of on-going work and support.
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.
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.
Remote-first Team Interactions for Business and Technology Teams @ NYC Scrum...
This document discusses concepts from the book "Team Topologies" about organizing teams for remote work. It promotes defining team dependencies, interactions, and boundaries to improve collaboration. It argues organizational charts don't reflect reality and interactions should be driven by real needs, not formal processes. It also advocates clarifying communication purposes and channels, using feedback to evolve, and replacing rigid support structures with swarming to resolve incidents.
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.
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.
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.
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.
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.
Accelerating Flow with Team Topologies & Friends @ Adaptive Organizations Wee...
This document summarizes Manuel Pais' presentation on accelerating flow with Team Topologies. It discusses key concepts from Team Topologies like stream-aligned teams, platform teams, and evolving team interactions. It provides an example case study of how Footasylum applied Team Topologies concepts to increase responsiveness. It concludes by discussing how Team Topologies helps organizations gain situational awareness and focus on their core mission to improve business and technical agility.
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.
Playing Tetris with Cognitive Load @ Craft Conference, Jun 2021
This document discusses managing cognitive load on software delivery teams. It defines intrinsic, extraneous, and germane cognitive loads, and explains how to limit cognitive load through adequate team topologies. The key team topologies are stream-aligned teams for end-to-end ownership, enabling teams for mentoring, platform teams for reusable services, and specialized subsystem teams. Teams should interact through collaboration, X-as-a-service, or facilitating modes. Explicit cognitive load, team-sized software, and adequate topologies are critical to taming cognitive load.
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
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
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.
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.
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.
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.
From a talk at Dept Manchester sponsored by Commercetools https://www.deptagency.com/en-gb/event/architecting-the-modern-digital-experience/
Monoliths vs microservices is missing the point - start with team cognitive l...
The document discusses team cognitive load and organizing teams and software boundaries based on a team's cognitive capacity. It introduces the concepts of intrinsic, extraneous, and germane cognitive load and argues that software and teams should be sized based on what fits in a team's head. It presents case studies of companies that evolved their structures to align with cognitive load and discusses techniques like stream-aligned teams, enabling teams, and platform teams. The document provides guidance on assessing a team's cognitive load and interactions to determine the appropriate organizational structure.
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.
Kubernetes Is Not Your Platform, It's Just the Foundation @ Tech Community Da...
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.
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.
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.
Beyond the Spotify Model - Team Topologies - Tech.rocks - 2020-12-10 - Matthe...
From a talk at Tech.Rocks 2020
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes.
This talk will cover the basics of organization design using Team Topologies, exploring a selection of key team types, and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on the book Team Topologies by Matthew Skelton and Manuel Pais including first-hand experience helping companies around the world with the design of their technology teams.
Key takeaways:
1. Why using the “Spotify Model” of team design is not enough
2. The four fundamental team topologies needed for modern software delivery
3. The three team interaction modes that enable fast flow and rapid learning
4. How to address Conway’s Law, cognitive load, and team evolution with Team Topologies
Monoliths, microservices, and team cognitive load - Team Topologies - DOES EU...
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, illustrated by real case studies.
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! @ 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.
More Related Content
What's hot
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.
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.
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.
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.
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.
Accelerating Flow with Team Topologies & Friends @ Adaptive Organizations Wee...
This document summarizes Manuel Pais' presentation on accelerating flow with Team Topologies. It discusses key concepts from Team Topologies like stream-aligned teams, platform teams, and evolving team interactions. It provides an example case study of how Footasylum applied Team Topologies concepts to increase responsiveness. It concludes by discussing how Team Topologies helps organizations gain situational awareness and focus on their core mission to improve business and technical agility.
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.
Playing Tetris with Cognitive Load @ Craft Conference, Jun 2021
This document discusses managing cognitive load on software delivery teams. It defines intrinsic, extraneous, and germane cognitive loads, and explains how to limit cognitive load through adequate team topologies. The key team topologies are stream-aligned teams for end-to-end ownership, enabling teams for mentoring, platform teams for reusable services, and specialized subsystem teams. Teams should interact through collaboration, X-as-a-service, or facilitating modes. Explicit cognitive load, team-sized software, and adequate topologies are critical to taming cognitive load.
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
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
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.
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.
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.
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.
From a talk at Dept Manchester sponsored by Commercetools https://www.deptagency.com/en-gb/event/architecting-the-modern-digital-experience/
Monoliths vs microservices is missing the point - start with team cognitive l...
The document discusses team cognitive load and organizing teams and software boundaries based on a team's cognitive capacity. It introduces the concepts of intrinsic, extraneous, and germane cognitive load and argues that software and teams should be sized based on what fits in a team's head. It presents case studies of companies that evolved their structures to align with cognitive load and discusses techniques like stream-aligned teams, enabling teams, and platform teams. The document provides guidance on assessing a team's cognitive load and interactions to determine the appropriate organizational structure.
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.
Kubernetes Is Not Your Platform, It's Just the Foundation @ Tech Community Da...
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.
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.
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.
Beyond the Spotify Model - Team Topologies - Tech.rocks - 2020-12-10 - Matthe...
From a talk at Tech.Rocks 2020
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes.
This talk will cover the basics of organization design using Team Topologies, exploring a selection of key team types, and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on the book Team Topologies by Matthew Skelton and Manuel Pais including first-hand experience helping companies around the world with the design of their technology teams.
Key takeaways:
1. Why using the “Spotify Model” of team design is not enough
2. The four fundamental team topologies needed for modern software delivery
3. The three team interaction modes that enable fast flow and rapid learning
4. How to address Conway’s Law, cognitive load, and team evolution with Team Topologies
Monoliths, microservices, and team cognitive load - Team Topologies - DOES EU...
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, illustrated by real case studies.
What's hot (20)
Avoiding the CI/CD Monolith with Team Topologies @ DevOps Sydney meetup, Oct ...
Avoiding the CI/CD Monolith with Team Topologies @ DevOps Sydney meetup, Oct ...
Avoiding the CI/CD Monolith with Team Design & Evolution @ London CD meetup, ...
Avoiding the CI/CD Monolith with Team Design & Evolution @ London CD meetup, ...
Product Teams Need a Family Too! @ Stockholm Engineering Leadership Meetup, J...
Product Teams Need a Family Too! @ Stockholm Engineering Leadership Meetup, J...
Remote first team interactions with Team Topologies - IT Revolution webinar -...
Remote first team interactions with Team Topologies - IT Revolution webinar -...
Fast Flow & Organizational Evolution with Team Topologies @ Masters of Softwa...
Fast Flow & Organizational Evolution with Team Topologies @ Masters of Softwa...
Accelerating Flow with Team Topologies & Friends @ Adaptive Organizations Wee...
Accelerating Flow with Team Topologies & Friends @ Adaptive Organizations Wee...
Product Teams Need a Family Too! @ Enterprise Agile San Francisco meetup, Jul...
Product Teams Need a Family Too! @ Enterprise Agile San Francisco meetup, Jul...
Playing Tetris with Cognitive Load @ Craft Conference, Jun 2021
Playing Tetris with Cognitive Load @ Craft Conference, Jun 2021
Frozen DevOps? Team Topologies Comes to the Rescue! @ DevOpsDays Poznan, Oct ...
Frozen DevOps? Team Topologies Comes to the Rescue! @ DevOpsDays Poznan, Oct ...
Frozen DevOps? Team Topologies Comes to the Rescue! @ DevSecOps - London Gath...
Frozen DevOps? Team Topologies Comes to the Rescue! @ DevSecOps - London Gath...
Product teams need a family too! Fundamental Team Topologies for Flow @ DevOp...
Product teams need a family too! Fundamental Team Topologies for Flow @ DevOp...
Why You Need to Think About Team Design for CI/CD @Jenkins World Lisbon 2019
Why You Need to Think About Team Design for CI/CD @Jenkins World Lisbon 2019
Forget monoliths vs microservices - focus on team cognitive load - Team Topol...
Forget monoliths vs microservices - focus on team cognitive load - Team Topol...
Forget monoliths vs microservices - focus on Team Cognitive Load - Team Topol...
Forget monoliths vs microservices - focus on Team Cognitive Load - Team Topol...
Monoliths vs microservices is missing the point - start with team cognitive l...
Monoliths vs microservices is missing the point - start with team cognitive l...
Team Topologies in action - early results from industry - DOES Las Vegas 2020...
Team Topologies in action - early results from industry - DOES Las Vegas 2020...
Kubernetes Is Not Your Platform, It's Just the Foundation @ Tech Community Da...
Kubernetes Is Not Your Platform, It's Just the Foundation @ Tech Community Da...
Business and Technical Agility with Team Topologies @ WTF Is Cloud Native, No...
Business and Technical Agility with Team Topologies @ WTF Is Cloud Native, No...
Beyond the Spotify Model - Team Topologies - Tech.rocks - 2020-12-10 - Matthe...
Beyond the Spotify Model - Team Topologies - Tech.rocks - 2020-12-10 - Matthe...
Monoliths, microservices, and team cognitive load - Team Topologies - DOES EU...
Monoliths, microservices, and team cognitive load - Team Topologies - DOES EU...
Similar to Product Teams Need a Family Too! @ New Ways of Working - Modern Agile in Wellington meetup, Sep 2020
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! @ 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.
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.
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.
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
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.
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.
Product Teams Need a Family Too! @ Product Camp Brazil, Dec 2021
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.
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.
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.
Matthew Skelton_What is Platform as a Product_ Clues from Team Topologies - D...
1) A platform as a product approach treats an internal platform like an externally-facing product by carefully designing it, evolving it based on user needs, and using modern product management practices.
2) This reduces cognitive load on internal engineering teams using the platform by simplifying tasks and providing optional, self-service capabilities.
3) Getting started involves assessing user needs, defining the platform, and determining team interaction models for collaboration and service delivery. Case studies demonstrate how platforms can evolve from basic services to sophisticated, widely adopted products.
Team Topologies at Parts Unlimited, The Unicorn Project Book Club, Jan 2020
This document discusses organizing business and technology teams at Parts Unlimited to enable fast flow. It recommends taking a team-first approach by focusing teams on individual business streams and platform services. Teams should be kept small, around 9 people, to reduce cognitive load. The platform should be treated as a product and overseen by dedicated teams. An enabling team can help bridge capability gaps and teach skills rather than doing the work. The organization and systems architectures need to be codesigned to allow for rapid feedback and change.
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/
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.
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.
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/
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.
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.
Emerging Trends of Software Engineering
The document discusses emerging trends in software engineering and development after the COVID-19 pandemic and in preparation for sustainable development goals. It notes that digital transformation is a priority for many businesses as they adapt to remote work and contactless services. Software developers will play a key role in building the post-pandemic world and achieving sustainability. DevOps and agile methodologies are discussed as approaches that can provide continuous delivery of high quality software. Benefits of agile include increased speed, customer satisfaction, valuing employees, and eliminating rework. Best practices and tools to support agile are also outlined.
An evening with... DevOps
DevOps es un conjunto de prácticas que automatizan los procesos entre el desarrollo de software y los equipos de infraestructura, de manera que el software pueda ser construido, probado y puesto en producción más rápidamente y con la misma confiabilidad.
El concepto de DevOps esta fundamentado en la construcción de una cultura de colaboración entre equipos que históricamente son silos. Los beneficios aparentes incluyen confianza mutua, más rápidos ciclos de puesta en producción, habilidad para resolución de incidentes más rápidamente y mejor adaptación a los cambios.
En esta sesión revisamos conceptos clave de DevOps, el estado del arte y algunas de las tecnologías involucradas.
Similar to Product Teams Need a Family Too! @ New Ways of Working - Modern Agile in Wellington meetup, Sep 2020 (20)
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! @ Iberia SWE Fest, Mar 2023
Product Teams Need A Family Too! @ Iberia SWE Fest, Mar 2023
Business and Technical Agility with Team Topologies, Jun 2021
Business and Technical Agility with Team Topologies, Jun 2021
Keynote: Frozen DevOps? The not-so-technical Last Mile @ DevOpsDays Portugal,...
Keynote: Frozen DevOps? The not-so-technical Last Mile @ DevOpsDays Portugal,...
Business and technical agility with Team Topologies - QCon Plus - 2021-05-26
Business and technical agility with Team Topologies - QCon Plus - 2021-05-26
What is platform as a product? Clues from Team Topologies - Puppetize 2020 - ...
What is platform as a product? Clues from Team Topologies - Puppetize 2020 - ...
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...
Product Teams Need a Family Too! @ Product Camp Brazil, Dec 2021
Product Teams Need a Family Too! @ Product Camp Brazil, Dec 2021
Business agility with Team Topologies - NatWest Group - 2021-01-19
Business agility with Team Topologies - NatWest Group - 2021-01-19
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...
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...
Team Topologies at Parts Unlimited, The Unicorn Project Book Club, Jan 2020
Team Topologies at Parts Unlimited, The Unicorn Project Book Club, Jan 2020
Playing Tetris with Cognitive Load @ Chile Ágil meetup, Oct 2022
Playing Tetris with Cognitive Load @ Chile Ágil meetup, Oct 2022
Business and Technical Agility with Team Topologies @ CAS 2022
Business and Technical Agility with Team Topologies @ CAS 2022
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...
Business Agility with Team Topologies @ Digital Transformation London meetup,...
Business Agility with Team Topologies @ Digital Transformation London meetup,...
Accelerating Flow with Team Topologies & Friends @ Wroclaw Kanban, Lean & Cof...
Accelerating Flow with Team Topologies & Friends @ Wroclaw Kanban, Lean & Cof...
Beyond Engineering: The Future of Platforms @ CraftConf, May 2023
Beyond Engineering: The Future of Platforms @ CraftConf, May 2023
More from Manuel Pais
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
Conway's Law states that organizations will inevitably produce systems that mirror their internal communication structures. This document discusses how to organize teams to avoid this by limiting cognitive load, aligning teams with business streams, and defining clear team APIs. It suggests starting by assessing a team's existing cognitive load, whether work streams are misaligned, and if there are large mismatches between team interactions and architecture. Providing resources on these topics can help teams get started with the right organizational structures.
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.
Organizational Trends and Patterns with Team Topologies @ LPCx Meetup, July 2021
The document discusses Team Topologies, an organizational framework for structuring business and technology teams to enable fast flow. It covers key concepts like operational constraints, trust boundaries, cognitive load, Conway's Law, and organizational patterns. It also outlines triggers for sensing and evolving an organization as its ecosystem changes. The framework provides a shared language and common patterns to help organizations explore solutions for designing and evolving their structure.
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?
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.
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 (9)
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
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
Organizational Trends and Patterns with Team Topologies @ LPCx Meetup, July 2021
Organizational Trends and Patterns with Team Topologies @ LPCx Meetup, July 2021
Traditional vs Modern Internal Platforms @ Humanitec webinar, Jun 2021
Traditional vs Modern Internal Platforms @ Humanitec webinar, Jun 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...
Remote-first Team Interactions for Business and Technology Teams @ DevOps Not...
Remote-first Team Interactions for Business and Technology Teams @ DevOps Not...
Recently uploaded
HCL Notes and Domino License Cost Reduction in the World of DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Generating privacy-protected synthetic data using Secludy and Milvus
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
ここ3000字までしか入らないけどタイトルの方がたくさん文字入ると思います。
Choosing The Best AWS Service For Your Website + API.pptx
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
TrustArc Webinar - 2024 Global Privacy Survey
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
How to Get CNIC Information System with Paksim Ga.pptx
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.OpenID AuthZEN Interop Read Out - Authorization
During Identiverse 2024 and EIC 2024, members of the OpenID AuthZEN WG got together and demoed their authorization endpoints conforming to the AuthZEN API
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Best 20 SEO Techniques To Improve Website Visibility In SERP
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Recently uploaded (20)
HCL Notes and Domino License Cost Reduction in the World of DLAU
HCL Notes and Domino License Cost Reduction in the World of DLAU
Generating privacy-protected synthetic data using Secludy and Milvus
Generating privacy-protected synthetic data using Secludy and Milvus
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
Choosing The Best AWS Service For Your Website + API.pptx
Choosing The Best AWS Service For Your Website + API.pptx
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
How to Get CNIC Information System with Paksim Ga.pptx
How to Get CNIC Information System with Paksim Ga.pptx
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Best 20 SEO Techniques To Improve Website Visibility In SERP
Best 20 SEO Techniques To Improve Website Visibility In SERP
Product Teams Need a Family Too! @ New Ways of Working - Modern Agile in Wellington meetup, Sep 2020
- 1. TeamTopologies.com @TeamTopologies Product Teams Need a Family Too! Manuel Pais @manupaisable
- 2. 2 Manuel Pais Independent IT organizational consultant and trainer Ex-dev, ex-build manager, ex-tester, ex-QA lead LinkedIn instructor on Accelerating Continuous Delivery Twitter: @manupaisable LinkedIn: manuelpais
- 3. Team Topologies 3 Organizing business and technology teams for fast flow Matthew Skelton & Manuel Pais IT Revolution Press (2019) https://teamtopologies.com
- 4. Origins - DevOps Topologies 4 CC BY-SA devopstopologies.com @TeamTopologies
- 5. “Great products emerge from empowered, fully cross-functional teams.” – John Cutler, 2019 5
- 12. 12 There’s a limit to the scalability of product teams alone
- 13. 13
- 17. 19 Handovers (can) kill flow
- 19. 21
- 20. “Great products emerge from empowered, fully cross-functional teams.” – John Cutler, 2019 22
- 21. “Despite striving to be cross-functional, one of the thornier problems product teams often face is lacking some necessary competence.” – Peter Neumark, 2015 23
- 30. 32 autonomy
- 31. 33 competences
- 32. 34 How to alleviate the tension between: team autonomy (increases flow) and lack of competences (decreases flow)
- 34. 36 in-flow dependencies based on handovers out-of-flow dependencies based on capability gaps
- 35. 37
- 36. 38
- 37. 39
- 39. “Cognitive load is the total amount of mental effort being used in the working memory” - John Sweller 43
- 40. 48 Cognitive load Intrinsic (skills) Extraneous (mechanics) Germane (business focus)
- 41. 51 Cognitive load Intrinsic (skills) Extraneous (mechanics) Germane (business focus)
- 42. “Software that fits in your head” - Daniel Terhorst-North 52 https://speakerdeck.com/tastapod/microservices-software-that-fits-in-your-head?slide=62
- 43. 53 “Software that fits in our heads”
- 44. 54 Team ownership must include: Releasability Testability Operability / Supportability
- 45. 4 key metrics: ‘Accelerate’ 55 lead time deployment frequency mean time to restore (MTTR) change fail percentage
- 46. 56
- 48. “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 58
- 49. A good platform is treated as a product (reliable, usable, fit for purpose) 59
- 50. 60
- 52. 62
- 53. 63
- 55. 65
- 56. 66 Collaboration: 2 teams working together X-as-a-Service: 1 provides, 1 consumes Facilitating: 1 team helps another
- 57. 67 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.
- 58. 68
- 59. Also important 69 Team-sized software Avoid Conway mismatches Organizational sensing Thinnest Viable Platform (TVP)
- 60. 70
- 61. 71
- 62. Team Topologies 72 Organizing business and technology teams for fast flow Matthew Skelton & Manuel Pais IT Revolution Press Order via stores worldwide: teamtopologies.com/book
- 63. teamtopologies.com/news Team Topologies Essentials Training Oct 7, 8, 14, 15 (APAC friendly) Details: teamtopologies.com/events 4 half-day online sessions with Manuel Pais 10% discount code TTWELLINGTON10
- 64. Resources 79 teamtopologies.com/resources (links, slides, video) github.com/teamtopologies (templates, assessments, etc)
- 65. Thank you! 80 Matthew Skelton, Conflux @matthewpskelton Manuel Pais, Independent @manupaisable teamtopologies.com