Really enjoying the writing in this paper on visual explanations + causality learning and our clever ways of designing them. From Holly Huey and collabs (2023), has a lovely momentum right from the first sentence:
"From infants exploring the objects in their immediate environment to scientists exploring the frontiers of our solar system, humans are driven to understand how things work and use that knowledge to generate desired outcomes"
@grimalkina oh this is awesome to see — I want to work on a masters in cog sci(?) with diagramming as a way to align understanding of complex systems ( #teamtopologies, #WardleyMapping being favorites). I’ve been in industry forever — is there a term for this type of focus?
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
"Experian, Fidelity and JP Morgan are amongst the organisations finding development flow with Team Topologies" - great summary of FastFlowConf from Mark Chillingworth
"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.
Published: A Cost-Savings Case for Team Topologies
Recently, I was involved in an unusual technology due diligence. We were asked how the technology organisation can save on costs. After some analysis and many interviews, we suggested a Team Topologies approach to organising teams that came with an impressive estimated cost reduction.
I've got exciting news! 🤩 I’m developing an online course on "Effectively Manage Team Cognitive Load." Targeted at managers, senior managers, executives, agile coaches, and software architects. Or anyone responsible to shape org structures, processes or software.
"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."
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".
Want to lead a more humane and effective organisation?🎙️Tune in, to the latest alphalist #Podcast featuring Matthew Skelton, co-author of Team Topologies and show host Tobias Schlottke.
Here's what you'll discover:
🌊 Value Flow
🪢 Team Topologies
🛡️ Continuous Stewardship
🧩 Decoupling in Time
Apply these principles to foster adaptive flow-based approaches and solve hard problems with ease.
It feels that stream-aligned teams and the fluid teams is a big conflict? And I'm wondering what kind of tradeoffs you've found when working with one or the other?
For example, how do devs build deep domain expertise in fluid teams?
Or if you do TeamToplogies, does it always mean that you might need to rework your architecture so teams can work on value and not just on individual components?
@tcoopman I listened to a podcast on FaST recently and it was super illuminating. FaST is essentially trying to optimize for developer engagement, not continuous care of services.
📣 AWS Embraces Team Topologies as a Foundational Standard!
Exciting news for DevOps and organizational design enthusiasts! (SO, basically everyone at Team Topologies) AWS has officially integrated the our model into its core standards. Find out more ▶️
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).