Click here🔗https://teamtopologies.com/all-guided-workshops/workshop-team-topologies-in-a-nutshell-p818 if you want the graphic to make sense. Are you a leader, executive, or change agent looking to transform your organization's dynamics?
The🌟Team Topologies in a Nutshell - Foundation Workshop is designed just for you!
🚀 Transform your organization with our "Team Topologies in a Nutshell" Workshop! Perfect for leaders and change agents. Learn the "Team-first" approach, Conway's Law, workflow optimization, and more in 2 sessions.
Maximize your #TrainingBudget by enrolling in the Team Topologies Academy courses. Discover the fundamentals of #TeamTopologies, #TeamDynamics, #PlatformAsAProduct, and #ValueStreams. Moreover, if you bring along your team, you can avail of discounts starting from 5% and going up to a whopping 40%. Don't let this opportunity slip away. https://bit.ly/3ACEdVW
I am starting to explore words/phrases other than "ownership" to convey a sense of "looking after a thing in a healthy way":
- custodian / custodianship
- curator / curation
- caretaker / caretaking
This is in the context of long-lived software-enriched services (online IT/software services, legal services, accounting services, HR services, etc.) and emphasizing the need for long-term care, not short-term "throw the feature over the fence".
"You mean each value stream should have its own legal/sales/HR... activities not reused across value streams? "
Yes, this is exactly what some organizations do: core business capabilities aligned to and focused on specific value streams or business areas.
The entire of Team Topologies is about thinking where certain capabilities should best sit and the extent to which - and context in which - some capabilities might be reused when we need to go quickly.
Team Topologies is not really about structure. In fact, it's more about dynamics and organisational mission than org chart.
The implications of approaches like TT include the need to:
- Identify value streams
- Align funding to those streams
- Adopt product management for internal services and internal platforms
- Redesign system and organisational architecture to be realistic about team cognitive load and flow
And a whole bunch of other things. 😁
🔜 Ihr wollt erste Schritte mit #TeamTopologies gehen, typische Anti-Patterns und Fehler vermeiden und erfahren wie der Ansatz eurer Organisation nützen kann?
🏋️🧠 Im Workshop von @st_toth und @pgoetz auf der #SAGconf erfahrt ihr, wie dies mit Hilfe von #TeamTopologies gelingen kann, praxisnah und im Kontext eurer eigenen Organisation!
🖍 Jetzt anmelden:
🚀 Exciting insights from Matthew Skelton & Jon Smart on combining 'Team Topologies' & 'Sooner Safer Happier' for adaptive orgs.
🔹 Shift from silos to value streams
🔹 Embrace team insights for identifying value streams
🔹 Adapt & evolve stream boundaries for efficiency
🔹 A talk full of actionable insights for org agility!
🚀 Discover the keys to effective remote work! https://www.linkedin.com/feed/update/urn:li:activity:7133153582631038976
Explore principles and patterns from Team Topologies to boost your remote team interactions and thrive in the evolving work landscape. Learn from the experts. 👥🌐
🎯 New bundle available on the @TeamTopologies Academy, at 15% OFF.
It includes 2 self-paced video courses: "Effective Enabling Teams" (by Manuel Pais 🇺🇦 & Eduardo da Silva) & "#TeamTopologies Distilled" (by Manuel Pais 🇺🇦 and Matthew Skelton).
Learn how to leverage #EnablingTeams as an accelerator of learning and fast flow of value in modern organizations with this bundle that covers the fundamentals of Team Topologies plus how to grow effective Enabling Teams.
🚀 Explore MVP & TVP in Platform Engineering! Learn how "Thinnest Viable Platform" complements MVP for long-term success. This New Stack article by Abby Bangser explains how TVP ensures continuous platform improvement. Perfect for those aiming to balance innovation with sustainability. Dive in for insights on maintaining and extending software effectively.
Today I had the honour of speaking at the Agile Serbia / RSG 2023 in Belgrade.
I would like to thank the organizers for inviting me and taking good care of me, and everyone who came to my session "Domain-Driven Design and Team Topologies for Product-led Organizations".
This was my first trip to Belgrade and I only have positive feelings from all of the interactions I've had. I hope to return one day.
coming to the conclusion that in some cases #teamtopologies interaction modes should be less per team, more per service provided by the team.
yes, teams sometimes violate SRP principle, ie. providing a mature service per xaas and something different per collaboration mode.
now, how could that work in the visual language...?
🎉✨ Exciting News! Holiday Cheer is Here! 🌟
Ready to supercharge your learning journey this festive season? 🚀 Dive into the world of innovation with our exclusive holiday discount on ALL courses and bundles at @team Topologies Academy! 📚🔥
Learn about #TeamTopologies concepts, unlock the secrets to successful team collaboration, efficient DevOps practices, and much more! 🚀
🎁 Use code: WINTER2023 for an extra 15% off at checkout!
Explore our collection now: https://bit.ly/3ACEdVW 🌐
🔛 Mittendrin im #INNOQTechnologyDay mit über 700 wunderbaren Teilnehmer:innen. Freut Euch auf die kommenden Sessions ab 14:15 Uhr zu den Themen #AI Products, #TechStackCanvas, #TeamTopologies, Weiterbildung und der Optimierung von #LLM. Wo bist Du dabei?
Yesterday, I had a good time with the folks at the Fast Flow meetup. What a fantastic start for the community. I know that the organizers will publish the YT video later. 🤓 Spoiler alert: I was the chaos agent!
Here are the slides of my talk "Why should I care about sociotechnical systems? " 👉 https://speakerdeck.com/joaoasrosa/why-should-i-care-about-sociotechnical-systems-at-fast-flow-meetup-2023
Did you attend the DevOps Enterprise Summit in Las Vegas? Did you catch all the Tips and Tricks to Successfully apply Team Topologies? Full Video & Sides:▶️https://lnkd.in/dQcazCFw
We just finished watching a captivating talk filmed at this year's DevOps Enterprise Summit hosted by it revolution held in Las Vegas. The talk was given by Marcelo Ancelmo and Dinkar Gupta from KPMG Switzerland, it was about:🌟Tips and Tricks to Successfully apply Team Topologies🌟
We are excited to announce our newest Team Topologies Value Practitioner to join our team of experienced facilitators!
Kenny has years of experience working closely with CTOs, managers, architects, and software teams to revolutionise the way we design and develop software and he will be bringing that expertise to our customers in workshops and sessions.
Welcome to the TT team Kenny!
🚀 Introducing Independent Service Heuristics (ISH) for Optimized Software Delivery 🧠
Full Article and Video: 👉https://openpracticelibrary.com/practice/independent-service-heuristics-ish/
Exciting news from the thought leaders in software architecture and design! Matthew Skelton & Manuel Pais, the minds behind "Team Topologies," have contributed yet another powerful concept to the tech community: Independent Service Heuristics (ISH).
🚀 Unlocking Efficiency: Aligning Teams with Expertise 🎯
Team expertise is a valuable asset, and by organizing teams to match this expertise, we can maximize efficiency and productivity. Here's how to achieve alignment:
🤝 Unlocking Efficiency: The Art of Efficient Interactions 🚀
Collaboration and communication between teams can significantly impact productivity and overall success. Here's why it's essential:
Remote Engineering Strategy Workshop is open! 🙌
After the great feedback from my talk during the #scbcn23, I decided to dedicate two half-days to go into more detail about the concepts we saw during the talk for those who are facing similar challenges.
If you want to learn more about Engineering Strategy and Situation Awareness using #DomainDrivenDesign, #TeamTopologies and practical scenarios, I hope you can join me the next 29th and 30th of November!
Interested in achieving success with #internalplatform teams? Discover essential #TeamTopologies concepts & fundamental principles of #Platform as a #Product: Value, Customer Engagement, User Experience, and the #AdoptionCycle. Access these insights through the Platform Engineering Bundle offered by the Team Topologies Academy, featuring the 'Platform as a Product' & 'Team Topologies Distilled' courses authored by the Team Topologies writers, Manuel Pais & Matthew Skelton https://bit.ly/3Jx7JQj
@Andylongshaw great framing of the question. We'd see this as effectively a Platform service from the Content Design capability.
But also consider how a Content Design expert could help Stream-aligned teams to improve their design capability AND detect opportunities for providing additional content design services from a flow platform.
Blog: Key ideas for fast flow and DevOps transformation - from DevOpsDays Oslo 2023
"The common theme that emerged from the sessions I attended is really that structure is not going to save or fix your digital transformation. Instead, we need to pay attention to the group sizes, group interactions, and group experience when using tools."
Before I left a company, we had this picture of flow of change.
I recall people sharing two things:
- Stream-aligned teams are shipping at a good pace.
- The team is handling Backend with Kotlin, Web with React, and Mobile with ReactNative
A domain able to deliver E2E without handovers.
Those things were possible due to Platform Grouping and Enabling Teams. Leadership started to behave as enabling team and a little like platforms.
The #FlowOfChange and the team autonomy was great. The team had the cognitive load high but also were challenged and enjoying their work.
Breaking that team into "frontend, mobile, and backend" wouldn't improve the velocity but **destroy **it.
When you see the power of multiple peaces of #TeamTopologies working together to improve fast flow... no way you will look organizations as departments anymore but as flow change.
In Team Topologies, we define a platform as anything that improves flow and reduces extraneous team cognitive load in teams that use it.
- Wiki page
- Design System
- Infra tooling
A platform is not necessarily (just) a blob of technology.
Slides from my keynote talk at DevOpsDays Oslo 2023 are here online: https://speakerdeck.com/matthewskelton/how-to-fail-at-team-topologies-lessons-for-fast-flow-success-matthew-skelton-devopsdays-oslo
"How to fail at Team Topologies - lessons for fast flow success " - it turns out that the movie Frozen II is full of useful advice!
"Let’s discover what happens when a Kanban practitioner looks at the Team Topologies and how to use both as leverages for improving flow, evolving the whole organization beyond myopic teams’ focus.
This is what happens when Kanban meets Team Topologies."
Let’s discover what happens when a Kanban practitioner looks at the Team Topologies and how to use both as leverages for improving flow, evolving the whole organization beyond myopic teams’ focus.
This is what happens when Kanban meets Team Topologies.
This Medium article https://cloudnative.ly/beginning-team-topologies-764c796dc202 by Cloud Native Acceleration on Beginning Team Topologies, written by Billie Thompson is such a great way to introduce your team to Team Topologies.
Ever felt bureaucracy slowing down your team's delivery? 🤔
'Team Topologies' is bridging the gap between experts and novices. Find out why are organizations turning to this approach, and how does it refocus teams? Read this Medium article to find out more. 🌐
Entdecken Sie das Geheimnis effizienter Teamdynamik und Produktentwicklung mit Team Topologien! 🚀 Neugierig? Jetzt eintauchen. 🌐 https://cdi.digital/team-topologies/
Unlock the secret to streamlined team dynamics and product development with Team Topologies! 🚀 Curious? Dive in now. 🌐
Team Topologies (the book) is 4 years old! We had TT-coloured celebration cake 🍰 at our core team meeting 🤩
In a customer session yesterday there was a misunderstanding about "long-lived teams". People felt that the need to keep teams around long-term was a high bar preventing swarming and discovery.
"Long-lived teams" is instead of short-lived teams (2 weeks, 3 months, etc.) that ignore the "superpowers" of well-functioning teams.
Keep the teams together after they have developed a good working pattern, then bring work to that team.
📣 Did you know that all the free videos from the "Organizing for Independent #ValueStreams" Bundle in our Academy are available on the @TeamTopologies YouTube channel? Watch them now: https://bit.ly/3TuhbJ0
The bundle includes two self-paced video courses: "#TeamTopologies for Managers" by Matthew Skelton & Manuel Pais and "Independent Value Streams with Domain-Driven Design" by Nick Tune & Kacper Gunia.
I’m so excited to work out here. My main focuses:
- Share my internal overview of ITSM product space (user journey map, capabilities checklist)
- Complete my #TeamTopologies of that stack
- Eat more dosas and find a good chai
- Figure out a great one-pager product overview template
- Finish my #ProductManager assessment spreadsheet
It’s going to be a fun couple of weeks
Day 1 on Mastodon and I’ve been reblogged and followed by the co author of one of my favourite books at the moment, Team Topologies. We read it as part of a book club in my last team and it just made a whole lot of sense, highly recommend for anyone interested in building and running teams in a modern software engineering organisation - thanks @matthewskelton
What I absolutely love about #TeamTopologies is that when you say "wow, that's so much cleaner of a picture" it means you made an architecture so much easier to explain to others 😍
Customer question: "In terms of the concept of fully owned systems, what's the best way to approach code repos of shared packages that are contributed to by multiple teams? "
My reply: "Great question. Some further questions to help make decisions:
1. Why does the code need to be shared? What's the sense of value in the sharing?
2. What kind of coupling does the code sharing introduce? Do we want that coupling?
Does anyone have experiences (good or bad) of the emerging practice/tool of "talent marketplace" https://beamery.com/resources/blogs/what-is-a-talent-marketplace-and-why-do-you-need-one
💓 In its good form, a talent marketplace could help orgs to find good fits for people inside well-managed, slowly-evolving teams.
☣️ In a bad form, a talent marketplace would drive "fungible resources" nonsense and destroy teams.
The value of Team Topologies for software teams.
To learn more download our free minibook here 👉 https://landing.teamtopologies.com/mini-book-ddd-tt
@Today was all about books! 📚 Got my copies signed by @trisha_gee for her awesome trio: Head First Java, 97 Things Every Java Programmer Should Know, and Getting 2 Know IntelliJ IDEA. 😄 I may have brought a few too many, Trisha even thought I was swiping her display copies! 😂 No blame there. I also gave a copy of a book to a friend, and guess what? An Amazon surprise - Team Topologies arrived in the mail! 📦 Such a fantastic day! 🌟
#Books #Java #IntelliJ #TeamTopologies
This week in the DORA.community, @matthewskelton will join us for a discussion about untangling software delivery with team topologies, flow metrics, and careful decoupling.
Join the Google Group for a calendar invite and information on how to join the discussion on Thursday at 14:00 UTC.
Quick update on my book:
4 out of 17 chapters have passed through copy editing. Target is for all 17 to be completed this month.
AFAIK, we are still on schedule for physical copies to be available this year, possibly 31st October.
Thanks for all of your support. This is a tiring process and every bit of help gives me a tiny extra bit of motivation.
New blog post: How to write a talk about Team Topologies
📢 Team Topologies announces Armakuni as the first Team Topologies Solution Partner (TTSP) worldwide
We used the Team-Cognitive-Load-Assessment to understand the team cognitive load in a quarterly basis.
Based on the survey responses, we gather insights that were converted into initiatives with a desired outcome description.
When executed those initiatives, we might reached our desired outcome but we also had undesired consequences.
As any #complexSystem, we cannot say doing X, we will move from point A to B. But we can say, by doing X, we want to be closer to the desired end state.
We need to track the consequences and act on them.
It was painfully hard to gather all the data and have an historic overtime, that's why we started https://teamcognitiveload.com.
Wouldn't be cool to know how your organization evolved overtime and how your decisions helped to enable fast flow of change?
Gentle reminder. There is no Team Topologies certification program. No 2-day quick course, no special letters after your name for your CV, no certification circus. 🚫🤡
Instead, we are cultivating an ecosystem of informed practitioners. This is less "monetizable" but ultimately more valuable to all. 🌱