Here a good recap of this with conclusions => www.smharter.com/blog/2025/12...

Subtitle: How to structure and organise teams and cross-team collaboration around the work and the codebase

#TEAMTOPOLOGIES #FEATURETEAMS #LeSS
#SoftwareEngineering #ProductDevelopment
#SocioTechPractices

On this topic, AI-assisted coding, I also share this post discussing realistic expectations of productivity gains, and the tricky problem of the perception gap: www.smharter.com/blog/2025/09...

#AICoding #AIAssistedCoding
#VibeCoding
#PromptEngineering #LLM

See
- bsky.app/profile/luca... and
- bsky.app/profile/luca...

#TeamTopologies
#FeatureTeasm
#OrgDesign

Should an org or a professional devote themselves to one approach over the other (Team Topologies or Feature Teams)? Why? =>

If you prefer, join the conversation here www.linkedin.com/posts/lucami...

#TEAMTOPOLOGIES #FEATURETEAMS #LeSS
#SoftwareEngineering #ProductDevelopment
#SocioTechPractices

b) 𝗦𝗼𝘂𝗿𝗰𝗲 𝗖𝗼𝗱𝗲 𝗥𝗲𝘂𝘀𝗲: Software is shared as internal or external source code. 𝗢𝘄𝗻𝗲𝗿𝘀𝗵𝗶𝗽 𝗶𝘀 𝘀𝗵𝗮𝗿𝗲𝗱 to some degree, granting users rights like autonomously making direct code changes (a la Feature Teams or Google monorepo), autonomously forking, or at least posting a Pull Request.

continue...

a) 𝗕𝗹𝗮𝗰𝗸-𝗕𝗼𝘅 𝗥𝗲𝘂𝘀𝗲: Software is consumed as a closed system (e.g., commercial or internal binaries, or via IaaS/SaaS). 𝗢𝘄𝗻𝗲𝗿𝘀𝗵𝗶𝗽 remains 𝗲𝘅𝗰𝗹𝘂𝘀𝗶𝘃𝗲 to the providing team (a la Team Topologies or Amazon 2-pizza team) or external company.

continue...

... (continue) ... Thanks to (their contributions do not imply endorsement) @mrhinsh.bsky.social , Marcelo Lopez, Brian Marick, @martinfowler.com, Alistair Cockburn, Tom Gilb, Thoralf J Klatt, John Coleman, Greg Tutunjian and many others who contributed to this document.

- Thanks - to all those that provided info/content/edits etc (their contributions do not imply endorsement of this evolving doc): Tobias Mayer, @xpmatteo.bsky.social, Steve Tendon, @emilybache.com, George Dinwiddie, @daverooney.dev, @jrothman.com , Marco Bresciani, Karl Scotland, ...

With the rise of AI signalling a potential new paradigm of work, now is a good time to look back at the lessons learned and reflect on which of those can help in this major shift and what may come next.

You can check it out here => bit.ly/AgileTimeMac...

... Iterative and Incremental Development: A Brief History
Pdf => www.craiglarman.com/wiki/downloa...
Reference => ieeexplore.ieee.org/document/120...

#AI #ArtificialIntelligence #GenerativeAI
#FutureofTech #FutureofWork
#PromptEngineering #LLM
#AICoding #AIAssistedCoding #VibeCoding

Thanks to Outpace Conf for hosting a potentially controversial topic and for the great discussions with the audience 🎉

#OutpaceConf
#Manchester
#technologyConference
#seniorPractitioners
#leaders
#TEAMTOPOLOGIES
#FEATURETEAMS

The 1st time I was called out for leaning toward my passion and preferences and ignoring the pros of an alternative technique was by Giulio Vian. We have all been there; moving beyond that is part of the journey toward professional maturity.

More in general ... (TL;DR?!?!?!)
... It takes some distance from personal strengths, preferences, affiliations, biases, and passions, to look objectively at different techniques and understand where each fits well and why. And to learn from different perspectives, even when we may disagree.

What bottlenecks are you observing in your day-to-day AI-assisted coding practice?

#AI #ArtificialIntelligence #GenerativeAI
#FutureofTech #FutureofWork
#PromptEngineering #LLM
#AICoding #AIAssistedCoding #VibeCoding

The next bottleneck for Vibe coding (preferred for prototypes) is resolving the merge conflicts among multiple Agents.

The next bottleneck for Chat-oriented programming (preferred for high-quality production-ready code) is controlling the Agent(s), reviewing, validating and accepting their work.

BTW can agents ever learn from Trunk-Based-Development and the Elephant Carpaccio exercise?