Product Teams Need a Family Too! @ Agile Connect Lisbon - December 2019 Meetup
•
3 likes•76 views
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. Manuel Pais (https://www.manuelpais.net) is an independent IT consultant and trainer, focused on team interactions, delivery practices, and accelerating flow. Manuel is co-author of the book "Team Topologies: Organizing Business and Technology Teams for Fast Flow" (IT Revolution Press, 2019). He helps organizations rethink their approach to software delivery and operation via strategic assessments, practical workshops, and coaching. Also InfoQ lead editor. Answers by @manupaisable on Twitter and Medium.
Report
Share
Report
Share
Download to read offline
Recommended
Product Teams Need a Family Too — Fundamental Team Topologies for Fast Flow @...
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.
Abstract:
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 a 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.
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.
Monoliths vs Microservices is Missing the Point — 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 session I explain how and why.
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 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 canown 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.
Product teams need a family too! @ Agile Coaching Dortmund, Feb 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.
Product Teams Need a Family Too - Fundamental Team Topologies for Flow @ DevO...
Autonomous product teams are key for sustainable software delivery. But what does autonomy really mean? Do we expect the team to set up CI/CD, automate infra, test/UX all the things, and, of course, run and monitor their product? And still deliver features? Four fundamental team topologies and three interaction modes can help.
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.
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.
Company culture hacks for competitive advantage
The document discusses various "hacks" or ways to improve company culture through infrastructure, building empathy between departments, accommodating different working styles, using open source, metrics, and celebrating success. Some specific hacks mentioned are treating infrastructure as code, having developers participate in on-call rotations to better understand operations work, providing flexible working conditions like remote work and wifi, and measuring employee happiness through informal metrics. The overall message is that these types of cultural hacks can help align teams and processes while creating transparency, trust, and a closer connection between departments.
Recommended
Product Teams Need a Family Too — Fundamental Team Topologies for Fast Flow @...
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.
Abstract:
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 a 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.
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.
Monoliths vs Microservices is Missing the Point — 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 session I explain how and why.
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 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 canown 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.
Product teams need a family too! @ Agile Coaching Dortmund, Feb 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.
Product Teams Need a Family Too - Fundamental Team Topologies for Flow @ DevO...
Autonomous product teams are key for sustainable software delivery. But what does autonomy really mean? Do we expect the team to set up CI/CD, automate infra, test/UX all the things, and, of course, run and monitor their product? And still deliver features? Four fundamental team topologies and three interaction modes can help.
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.
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.
Company culture hacks for competitive advantage
The document discusses various "hacks" or ways to improve company culture through infrastructure, building empathy between departments, accommodating different working styles, using open source, metrics, and celebrating success. Some specific hacks mentioned are treating infrastructure as code, having developers participate in on-call rotations to better understand operations work, providing flexible working conditions like remote work and wifi, and measuring employee happiness through informal metrics. The overall message is that these types of cultural hacks can help align teams and processes while creating transparency, trust, and a closer connection between departments.
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! @ 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.
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.
Product Teams Need a Family Too! @ New Ways of Working - Modern Agile in Well...
Are you trying to move from agile project teams to business-aligned product teams?
Everyone from the CEO to middle management is on board.
Yet somehow it’s not that easy, is it?
You’ve just about figured out how to split infrastructure responsibilities between teams when the next great tech for cost-effective scalability is out there and it doesn’t fit in the new model. Oh, and let’s not forget that products X and Y have no automated tests since they were developed by temporary project teams.
The underlying questions are: What are the product team’s responsibilities? How do they interact with other teams and when?
The fundamental team topologies provide a framework for thinking about and aligning teams with an expected set of behaviors and responsibilities. In other words, we are clarifying their purpose and ways of working.
We recommend four fundamental team topologies, each with a well defined purpose and responsibilities. Along stream-aligned teams (of which product teams are a subset), the other three topologies recommended are platform, enabling, and complicated subsystem. This family of topologies provides the support system necessary for product teams to thrive.
In this talk we will see what each of these topologies brings to the table and how they enable organizations to quickly evolve and respond to both new technology and business requirements over time.
Competitive Advantage of Continuous Integration
Continuous Integration doesn't stop after the code compiles.
Continuous Integration can be applied at multiple levels; from the developer to the market. When we continuously integrate with the market we have a competitive advantage.
Taking Your Product Development to the Next Level with Full Stack
Optimizely Full Stack helps product development teams experiment deep into their stack to create exceptional customer experiences on everything from search results and promos to recommendations and payment structures. In this session, Jamie Connolly, Senior Product Manager on Developer Experience will talk about the latest enhancements to Full Stack to drive compatibility, usability, and performance.
Kessel Run: A Digital Transformation Story within the World's Largest Bureauc...
There are few enterprises in the world that might find it tougher to become Agile and build software rapidly than a large Government organisation such as the US Air Force. But that's exactly the challenge Adam is solving through the Kessel Run project. Adam and the team are currently averaging about four months (124 days) to get a technology product from an idea on a whiteboard to operational - a task that normally would take 8 years. In his inspiring talk, Adam will talk us through his approach to becoming agile including; The problem and complexity of becoming Agile in a government Waterfall environment Dealing with constraints; Understanding that not everybody will (or wants to) get onboard with becoming Agile - how to get around it. The structure and approach taken: Successes and lessons to date.
Clone Clone Make: a better way to build
Description of the J9's build pipeline and how reshaping it around the "clone clone make" vision has helped to reshape the organization.
What can DesignOps do for you? by Carol Smith at TLMUX in Montreal
You have probably seen the terms DesignOps and/or ResearchOps float by in your social media queue. These teams make designing (and researching) at scale beautifully efficient and successful. Carol steps through how these teams work, the types of activities they perform, situations they are helpful for, and ways you can leverage these types of programs in your organization. Carol will share examples from her experiences and stories from other organizations that are using Design Ops to do effective design at scale.
Presented at Tout le monde UX in Montreal, Quebec, Canada on February 28, 2019. http://toutlemonde-ux.com/
Agile Australia 2017 Hypothesis-Driven COTS Software Selection Tiago Griffo
Commercial Off The Shelf (COTS) applications are a part of most (perhaps every) medium to large enterprises. A lot of money is spent every year in selection and implementation projects of such applications – think millions to billions of dollars if you consider lost opportunity costs (which are hard to measure).
Unfortunately, buying instead of building is no guarantee of success. Tales of monumental package implementation overruns and disappointing functionality – not to mention outright failures – abound. These failures occur despite elaborate, detailed evaluation processes meant to select just the right package and reduce the risk of implementation. It is clear that businesses have to get better at researching, evaluating, and selecting software products.
In this talk we’ll describe an approach to selecting and implementing package software that focuses on engineering quality and business agility. We prefer an approach that involves hands-on, experiential hypothesis testing and evidence gathering over endless feature checklists and vendor demonstrations.
Why we don’t use the Term DevOps: the Journey to a Product Mindset - Destinat...
While the adoption of DevOps makes teams move faster with reduced dependency on central operations, it can constrain teams who lack the skills to self-manage the full application and infrastructure stack.
The way to overcome this challenge is creating an internal platform and treating it as a world-class product offering. “Applying product management to internal platforms means establishing empathy with internal consumers (read: developers) and collaborating with them on the design. Platform product managers establish roadmaps and ensure the platform delivers value to the business and enhances the developer experience”, via ThoughtWorks Technology Radar.
In this talk, Henning Jacobs will walk you through how Zalando adopted a customer-first mindset with regards to its developer tooling. He will show the effect on developer satisfaction when internal platforms are given the same respect as external product offerings. Henning will furthermore tell his story about how Zalando moved from a classical infrastructure team to a product mindset with strong focus on building a world-class developer experience. Henning shares both their learnings and challenges going through this transition, and the impact it has on the daily life of Zalando’s customers (developers).
This talk was given in Aarhus on 4th of June 2019.
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.
Scrum Framework Explained
The product backlog is a prioritized list of features, stories, or tasks that need to be completed for a product. It is created and maintained by the product owner. Items in the backlog are estimated by the team and assigned a business value by the product owner. The backlog is a living document that evolves over time based on changes to requirements, new ideas, or technical challenges. Effective product backlog definition requires collaboration between multiple roles through iterative and incremental processes.
Devops the Microsoft Way
Devops is a cultural movement gathering developers and IT Pros responsible for operating applications around common values, goals, practices and tools in order to accelerate development and deployment cycles, creating fast feedback loops between development and operations. Like agility 15 years ago, Devops adoption, accelerated by Cloud platforms adoption, involves organizational, cultural, as well as tehcnical aspects. Emerging movement a few years ago, now well established at consumer web and mobile companies, Devops starts to get in the Enterprise.
This presentation will explain the cultural and organizational aspects of the Devops movement, then will give an overview of the most common tools that are used to implement a Devops approach, showing that Microsoft is one of the few providers proposing a complete and integrated toolset, that works seamlessly for .NET developers, while integrating the most popular third party open source and proprietary tools, making Azure a great platform to implement a Devops approach for Linux, Java and open source workloads. We will talk about Visual Studio Online, Windows Azure, System Center, Windows Server, Azure Pack, PowerShell, NewRelic, Chef & Puppet integrations, Jenkins, …
This deck was presented at Microsoft Techdays 2014, Read more at http://www.microsoft.com/france/mstechdays/programmes/2014/fiche-session.aspx?ID=07af5982-c413-46c3-8214-bba12365529b#0CDPXYrtwEbWxrgW.99
Devops a la sauce Microsoft
Devops est un mouvement culturel qui rassemble developpeurs et IT Pros specialistes des operations autour de valeurs, buts et pratiques communes, dans le but d’accelerer le cycle de developpement et deploiement des applications, en creant des boucles de feedback retroactives rapides entre developpement et operation. Comme l’agilite il y a 15 ans, l’adoption de Devops, acceleree par l’adoption des plateformes en nuage, met en jeu des aspects organisationnels, culturels, et techniques. Mouvement emergent il y a quelques annees, bien implante aujourd’hui chez les fournisseurs d’applications grand public, Devops commence a interesser les developpeurs en enterprise. Cette presentation fera un etat des lieux des aspects culturels et organisationnels du mouvement Devops, puis un etat de l’art des outils a la mode en ce moment pour implementer une demarche Devops, montrant que Microsoft est un des rares acteurs du marche a proposer une panoplie complete d’outils integres dans ce domaine, tout en s’integrant avec les outils existants, qu’ils soient proprietaires ou open source: Visual Studio Online, Windows Azure, System Center, Windows Server, Azure Pack, PowerShell, NewRelic, Chef & Puppet integrations, Jenkins, …
Speaker : Patrick Chanezon (Microsoft)
Continuous Intelligence - David Colls (ThoughtWorks Live)
In this talk, we will help you to identify and deliver with confidence on opportunities to intelligently empower your business, customers, team members and other stakeholders, sharing our approach for building the right organisational capabilities.
Practical Internet of Things Now -- What it is and six requirements for your ...
The Internet of Things is here and you're starting your first project. Great! But what does that mean, what do you really need to do and what are other people doing? Check out this presentation originally from ThingsExpo in NYC.
Delight + adCenter
Tips, Tricks & Tools you can use to amaze. Presented during the "Amazing PPC Tactics" session at SMX Advanced in Seattle June 4, 2008.
Combining Speed of Delivery and Quality in Complex Systems
Talk presented at the 2017 opening session of UNED's Masters of Computer Engineering.
Agenda
1. The Need for Speed (aka DevOps)
2. Failure = Quality in Complex Systems
3. Survival of High-Performing Cultures
Supercharge Your Digital Transformation by Establishing a DevOps Platform
Although DevOps practices have gained wide adoption across industries, many organizations are still failing in their digital transformation efforts because they focus on tools over people and processes. You can avoid this trap by providing DevOps as a platform that is built and maintained by experts who provide standardized tools, templates, and processes to teams across the organization—regardless of those teams’ roles within the company, the type of applications or environments they work with, or the software delivery patterns they’ve adopted.
A centralized DevOps platform allows developers to leverage predefined delivery processes, so they don’t have to reinvent the wheel to get their apps into Production. It also helps ensure the right processes are followed and the right people are involved at the right times. A DevOps platform can provide both technical users and business stakeholders with end-to-end visibility into the software delivery process—promoting information sharing and collaboration across the organization.
Learn how to successfully implement a DevOps platform in your organization, so that every team gets the tools, templates, and visibility they need to deliver software faster than ever before.
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.
More Related Content
Similar to Product Teams Need a Family Too! @ Agile Connect Lisbon - December 2019 Meetup
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! @ 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.
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.
Product Teams Need a Family Too! @ New Ways of Working - Modern Agile in Well...
Are you trying to move from agile project teams to business-aligned product teams?
Everyone from the CEO to middle management is on board.
Yet somehow it’s not that easy, is it?
You’ve just about figured out how to split infrastructure responsibilities between teams when the next great tech for cost-effective scalability is out there and it doesn’t fit in the new model. Oh, and let’s not forget that products X and Y have no automated tests since they were developed by temporary project teams.
The underlying questions are: What are the product team’s responsibilities? How do they interact with other teams and when?
The fundamental team topologies provide a framework for thinking about and aligning teams with an expected set of behaviors and responsibilities. In other words, we are clarifying their purpose and ways of working.
We recommend four fundamental team topologies, each with a well defined purpose and responsibilities. Along stream-aligned teams (of which product teams are a subset), the other three topologies recommended are platform, enabling, and complicated subsystem. This family of topologies provides the support system necessary for product teams to thrive.
In this talk we will see what each of these topologies brings to the table and how they enable organizations to quickly evolve and respond to both new technology and business requirements over time.
Competitive Advantage of Continuous Integration
Continuous Integration doesn't stop after the code compiles.
Continuous Integration can be applied at multiple levels; from the developer to the market. When we continuously integrate with the market we have a competitive advantage.
Taking Your Product Development to the Next Level with Full Stack
Optimizely Full Stack helps product development teams experiment deep into their stack to create exceptional customer experiences on everything from search results and promos to recommendations and payment structures. In this session, Jamie Connolly, Senior Product Manager on Developer Experience will talk about the latest enhancements to Full Stack to drive compatibility, usability, and performance.
Kessel Run: A Digital Transformation Story within the World's Largest Bureauc...
There are few enterprises in the world that might find it tougher to become Agile and build software rapidly than a large Government organisation such as the US Air Force. But that's exactly the challenge Adam is solving through the Kessel Run project. Adam and the team are currently averaging about four months (124 days) to get a technology product from an idea on a whiteboard to operational - a task that normally would take 8 years. In his inspiring talk, Adam will talk us through his approach to becoming agile including; The problem and complexity of becoming Agile in a government Waterfall environment Dealing with constraints; Understanding that not everybody will (or wants to) get onboard with becoming Agile - how to get around it. The structure and approach taken: Successes and lessons to date.
Clone Clone Make: a better way to build
Description of the J9's build pipeline and how reshaping it around the "clone clone make" vision has helped to reshape the organization.
What can DesignOps do for you? by Carol Smith at TLMUX in Montreal
You have probably seen the terms DesignOps and/or ResearchOps float by in your social media queue. These teams make designing (and researching) at scale beautifully efficient and successful. Carol steps through how these teams work, the types of activities they perform, situations they are helpful for, and ways you can leverage these types of programs in your organization. Carol will share examples from her experiences and stories from other organizations that are using Design Ops to do effective design at scale.
Presented at Tout le monde UX in Montreal, Quebec, Canada on February 28, 2019. http://toutlemonde-ux.com/
Agile Australia 2017 Hypothesis-Driven COTS Software Selection Tiago Griffo
Commercial Off The Shelf (COTS) applications are a part of most (perhaps every) medium to large enterprises. A lot of money is spent every year in selection and implementation projects of such applications – think millions to billions of dollars if you consider lost opportunity costs (which are hard to measure).
Unfortunately, buying instead of building is no guarantee of success. Tales of monumental package implementation overruns and disappointing functionality – not to mention outright failures – abound. These failures occur despite elaborate, detailed evaluation processes meant to select just the right package and reduce the risk of implementation. It is clear that businesses have to get better at researching, evaluating, and selecting software products.
In this talk we’ll describe an approach to selecting and implementing package software that focuses on engineering quality and business agility. We prefer an approach that involves hands-on, experiential hypothesis testing and evidence gathering over endless feature checklists and vendor demonstrations.
Why we don’t use the Term DevOps: the Journey to a Product Mindset - Destinat...
While the adoption of DevOps makes teams move faster with reduced dependency on central operations, it can constrain teams who lack the skills to self-manage the full application and infrastructure stack.
The way to overcome this challenge is creating an internal platform and treating it as a world-class product offering. “Applying product management to internal platforms means establishing empathy with internal consumers (read: developers) and collaborating with them on the design. Platform product managers establish roadmaps and ensure the platform delivers value to the business and enhances the developer experience”, via ThoughtWorks Technology Radar.
In this talk, Henning Jacobs will walk you through how Zalando adopted a customer-first mindset with regards to its developer tooling. He will show the effect on developer satisfaction when internal platforms are given the same respect as external product offerings. Henning will furthermore tell his story about how Zalando moved from a classical infrastructure team to a product mindset with strong focus on building a world-class developer experience. Henning shares both their learnings and challenges going through this transition, and the impact it has on the daily life of Zalando’s customers (developers).
This talk was given in Aarhus on 4th of June 2019.
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.
Scrum Framework Explained
The product backlog is a prioritized list of features, stories, or tasks that need to be completed for a product. It is created and maintained by the product owner. Items in the backlog are estimated by the team and assigned a business value by the product owner. The backlog is a living document that evolves over time based on changes to requirements, new ideas, or technical challenges. Effective product backlog definition requires collaboration between multiple roles through iterative and incremental processes.
Devops the Microsoft Way
Devops is a cultural movement gathering developers and IT Pros responsible for operating applications around common values, goals, practices and tools in order to accelerate development and deployment cycles, creating fast feedback loops between development and operations. Like agility 15 years ago, Devops adoption, accelerated by Cloud platforms adoption, involves organizational, cultural, as well as tehcnical aspects. Emerging movement a few years ago, now well established at consumer web and mobile companies, Devops starts to get in the Enterprise.
This presentation will explain the cultural and organizational aspects of the Devops movement, then will give an overview of the most common tools that are used to implement a Devops approach, showing that Microsoft is one of the few providers proposing a complete and integrated toolset, that works seamlessly for .NET developers, while integrating the most popular third party open source and proprietary tools, making Azure a great platform to implement a Devops approach for Linux, Java and open source workloads. We will talk about Visual Studio Online, Windows Azure, System Center, Windows Server, Azure Pack, PowerShell, NewRelic, Chef & Puppet integrations, Jenkins, …
This deck was presented at Microsoft Techdays 2014, Read more at http://www.microsoft.com/france/mstechdays/programmes/2014/fiche-session.aspx?ID=07af5982-c413-46c3-8214-bba12365529b#0CDPXYrtwEbWxrgW.99
Devops a la sauce Microsoft
Devops est un mouvement culturel qui rassemble developpeurs et IT Pros specialistes des operations autour de valeurs, buts et pratiques communes, dans le but d’accelerer le cycle de developpement et deploiement des applications, en creant des boucles de feedback retroactives rapides entre developpement et operation. Comme l’agilite il y a 15 ans, l’adoption de Devops, acceleree par l’adoption des plateformes en nuage, met en jeu des aspects organisationnels, culturels, et techniques. Mouvement emergent il y a quelques annees, bien implante aujourd’hui chez les fournisseurs d’applications grand public, Devops commence a interesser les developpeurs en enterprise. Cette presentation fera un etat des lieux des aspects culturels et organisationnels du mouvement Devops, puis un etat de l’art des outils a la mode en ce moment pour implementer une demarche Devops, montrant que Microsoft est un des rares acteurs du marche a proposer une panoplie complete d’outils integres dans ce domaine, tout en s’integrant avec les outils existants, qu’ils soient proprietaires ou open source: Visual Studio Online, Windows Azure, System Center, Windows Server, Azure Pack, PowerShell, NewRelic, Chef & Puppet integrations, Jenkins, …
Speaker : Patrick Chanezon (Microsoft)
Continuous Intelligence - David Colls (ThoughtWorks Live)
In this talk, we will help you to identify and deliver with confidence on opportunities to intelligently empower your business, customers, team members and other stakeholders, sharing our approach for building the right organisational capabilities.
Practical Internet of Things Now -- What it is and six requirements for your ...
The Internet of Things is here and you're starting your first project. Great! But what does that mean, what do you really need to do and what are other people doing? Check out this presentation originally from ThingsExpo in NYC.
Delight + adCenter
Tips, Tricks & Tools you can use to amaze. Presented during the "Amazing PPC Tactics" session at SMX Advanced in Seattle June 4, 2008.
Combining Speed of Delivery and Quality in Complex Systems
Talk presented at the 2017 opening session of UNED's Masters of Computer Engineering.
Agenda
1. The Need for Speed (aka DevOps)
2. Failure = Quality in Complex Systems
3. Survival of High-Performing Cultures
Supercharge Your Digital Transformation by Establishing a DevOps Platform
Although DevOps practices have gained wide adoption across industries, many organizations are still failing in their digital transformation efforts because they focus on tools over people and processes. You can avoid this trap by providing DevOps as a platform that is built and maintained by experts who provide standardized tools, templates, and processes to teams across the organization—regardless of those teams’ roles within the company, the type of applications or environments they work with, or the software delivery patterns they’ve adopted.
A centralized DevOps platform allows developers to leverage predefined delivery processes, so they don’t have to reinvent the wheel to get their apps into Production. It also helps ensure the right processes are followed and the right people are involved at the right times. A DevOps platform can provide both technical users and business stakeholders with end-to-end visibility into the software delivery process—promoting information sharing and collaboration across the organization.
Learn how to successfully implement a DevOps platform in your organization, so that every team gets the tools, templates, and visibility they need to deliver software faster than ever before.
Similar to Product Teams Need a Family Too! @ Agile Connect Lisbon - December 2019 Meetup (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! @ Enterprise Agile San Francisco meetup, Jul...
Product Teams Need a Family Too! @ Enterprise Agile San Francisco meetup, Jul...
Product Teams Need a Family Too! @ Stockholm Engineering Leadership Meetup, J...
Product Teams Need a Family Too! @ Stockholm Engineering Leadership Meetup, J...
Product Teams Need a Family Too! @ New Ways of Working - Modern Agile in Well...
Product Teams Need a Family Too! @ New Ways of Working - Modern Agile in Well...
Taking Your Product Development to the Next Level with Full Stack
Taking Your Product Development to the Next Level with Full Stack
Kessel Run: A Digital Transformation Story within the World's Largest Bureauc...
Kessel Run: A Digital Transformation Story within the World's Largest Bureauc...
What can DesignOps do for you? by Carol Smith at TLMUX in Montreal
What can DesignOps do for you? by Carol Smith at TLMUX in Montreal
Agile Australia 2017 Hypothesis-Driven COTS Software Selection Tiago Griffo
Agile Australia 2017 Hypothesis-Driven COTS Software Selection Tiago Griffo
Why we don’t use the Term DevOps: the Journey to a Product Mindset - Destinat...
Why we don’t use the Term DevOps: the Journey to a Product Mindset - Destinat...
Playing Tetris with Cognitive Load @ QEDx internal conference (keynote), Jan ...
Playing Tetris with Cognitive Load @ QEDx internal conference (keynote), Jan ...
Continuous Intelligence - David Colls (ThoughtWorks Live)
Continuous Intelligence - David Colls (ThoughtWorks Live)
Practical Internet of Things Now -- What it is and six requirements for your ...
Practical Internet of Things Now -- What it is and six requirements for your ...
Combining Speed of Delivery and Quality in Complex Systems
Combining Speed of Delivery and Quality in Complex Systems
Supercharge Your Digital Transformation by Establishing a DevOps Platform
Supercharge Your Digital Transformation by Establishing a DevOps Platform
More from Manuel Pais
Accelerating Flow with Team Topologies & Friends @ Wroclaw Kanban, Lean & Cof...
Organizations that do not adapt rapidly to the modern, highly-changeable business environment are failing, and failing in large numbers. Increased regulation, pressures from climate change, shifting of energy sources, digitalization, and (recently) the COVID-19 pandemic are all driving a need for business agility in organizations of all sizes. In this talk, we’ll explore how the patterns and principles from Team Topologies promote true business agility through a rapid flow of software change, fast feedback from running systems, a strong drive for loose coupling, and an awareness of sociotechnical mirroring. Combined with a product mindset and techniques from Domain-driven Design, the Team Topologies approach is helping organizations around the world to adapt to the “new normal” and achieve true business agility.
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.
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 @ 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.
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/
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.
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 @ 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.
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 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.
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.
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/
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
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.
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.
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?
More from Manuel Pais (20)
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
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 @ CAS 2022
Business and Technical Agility with Team Topologies @ CAS 2022
Playing Tetris with Cognitive Load @ Chile Ágil meetup, Oct 2022
Playing Tetris with Cognitive Load @ Chile Ágil meetup, Oct 2022
Keynote: Frozen DevOps? The not-so-technical Last Mile @ DevOpsDays Portugal,...
Keynote: Frozen DevOps? The not-so-technical Last Mile @ DevOpsDays Portugal,...
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 @ DevOps Porto meet...
What is Platform as a Product? Clues from Team Topologies @ DevOps Porto meet...
Product Teams Need a Family Too! @ Product Camp Brazil, Dec 2021
Product Teams Need a Family Too! @ Product Camp Brazil, Dec 2021
Business and Technical Agility with Team Topologies @ WTF Is Cloud Native, No...
Business and Technical Agility with Team Topologies @ WTF Is Cloud Native, No...
Accelerating Flow with Team Topologies & Friends @ Adaptive Organizations Wee...
Accelerating Flow with Team Topologies & Friends @ Adaptive Organizations Wee...
Business Agility with Team Topologies @ Digital Transformation London meetup,...
Business Agility with Team Topologies @ Digital Transformation London meetup,...
Frozen DevOps? Team Topologies Comes to the Rescue! @ DevOpsDays Poznan, Oct ...
Frozen DevOps? Team Topologies Comes to the Rescue! @ DevOpsDays Poznan, Oct ...
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
Business and Technical Agility with Team Topologies, Jun 2021
Business and Technical Agility with Team Topologies, Jun 2021
Traditional vs Modern Internal Platforms @ Humanitec webinar, Jun 2021
Traditional vs Modern Internal Platforms @ Humanitec webinar, Jun 2021
Recently uploaded
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.
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
“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.20240609 QFM020 Irresponsible AI Reading List May 2024
Everything I found interesting about the irresponsible use of machine intelligence in May 2024
5th LF Energy Power Grid Model Meet-up Slides
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Building Production Ready Search Pipelines with Spark and Milvus
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
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!
Skybuffer SAM4U tool for SAP license adoption
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
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.
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.
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.
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.
Programming Foundation Models with DSPy - Meetup Slides
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Artificial Intelligence for XMLDevelopment
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
National Security Agency - NSA mobile device best practices
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Recently uploaded (20)
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
20240609 QFM020 Irresponsible AI Reading List May 2024
20240609 QFM020 Irresponsible AI Reading List May 2024
Building Production Ready Search Pipelines with Spark and Milvus
Building Production Ready Search Pipelines with Spark and Milvus
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for Life Science to increase LLM accuracy
Choosing The Best AWS Service For Your Website + API.pptx
Choosing The Best AWS Service For Your Website + API.pptx
Best 20 SEO Techniques To Improve Website Visibility In SERP
Best 20 SEO Techniques To Improve Website Visibility In SERP
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
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
Generating privacy-protected synthetic data using Secludy and Milvus
Generating privacy-protected synthetic data using Secludy and Milvus
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
National Security Agency - NSA mobile device best practices
National Security Agency - NSA mobile device best practices
Product Teams Need a Family Too! @ Agile Connect Lisbon - December 2019 Meetup
- 1. TeamTopologies.com @TeamTopologies Product Teams Need a Family Too! Manuel Pais @manupaisable
- 2. “Great products emerge from empowered, fully cross-functional teams.” – John Cutler, 2019 2
- 9. 9 There’s a limit to the scalability of product teams alone
- 10. 10
- 11. 11
- 16. 16 Handovers (can) kill flow
- 18. 18
- 19. “Great products emerge from empowered, fully cross-functional teams.” – John Cutler, 2019 22
- 20. “Despite striving to be cross-functional, one of the thornier problems product teams often face is lacking some necessary competence.” – Peter Neumark, 2015 23
- 29. 32 autonomy
- 30. 33 competences
- 31. 34 How to alleviate the tension between: team autonomy (increases flow) and lack of competences (decreases flow)
- 33. 36
- 34. 37
- 35. 38
- 37. 40
- 39. 42
- 41. A good platform is treated as a product (reliable, usable, fit for purpose) 44
- 42. 45
- 44. 47
- 45. 48
- 47. 50
- 48. 51
- 49. 52 When used with care, these are the only four fundamental team topologies needed to build and run modern software systems.
- 50. 53
- 51. 54
- 52. Also important 55 Team-sized software Avoid Conway mismatches Organizational sensing Thinnest Viable Platform (TVP)
- 53. Nationwide Project to Product: Practical Realities at a Large Scale Enterprise Adidas Where Cloud Native Meets the Sporting Goods Industry Barclays The Yin and Yang of Speed and Control BMW Game Changer: 100% Agile DevOpsTopologies.com Mercedes DevOps Adoption at Mercedes-Benz.io Twilio Platforms at Twilio: Unlocking Developer Effectiveness MAN Truck & Bus How to Manage Cloud Infrastructure at MAN Truck & Bus Farfetch UX I DevOps - The Trojan Horse for Implementing a DevOps Culture