When you are a individual contributor, these concepts seems farfetch, but when you enter a large company and teams start to grow, and you face the inner burocracy, and the codebase reach 500+ thousand lines of code, then these concepts start to emerge. DevOps culture, workflow automation, test automation, ownership, governance, acountability, etc. Because suddendly the individual performance doesnt extrapolate to the team performance anymore, coordination become more dificult, and the pace of shipping features start to slow, then these kinds of insights start to be more valuable, even when no direct accionable is mencion.
This talk and Lean management practices are in alignment. Value stream of software development processes is often set and rarely optimized consistently. Good reminders.
Excellent video. Thank You. I really like views that step back and look for similarity across apparently unrelated fields. The social scaling really resonates with me as I am really interested in the concept of autonomy@scale rather than Agile@scale which is where I think most organisations are failing to get the benefits that they expect from Agile transformations.
Verbose, but not wrong. Dare I summarise - organisations should be modelled on a Directed Acyclic Graph topology - directed, as in there is some value produced at the end; acyclic, in that its clear which teams provide services for other teams and there are no infinite loops; and graph, in that we accept real world has more than one parent node :)
Watching for the second time to arm myself further and start delving into this paradigm. I've run my small studio somehow similar but I know I need a well defined methodology to follow.
I have to agree. The title makes very little sense in terms of architecture or complexity. It should be more along the lines of "how to grow companies to be successful". And cut down the chit chat here. Should be 30 minutes. Guess they pay Thoughtworks talkers by the hour.
When you are a individual contributor, these concepts seems farfetch, but when you enter a large company and teams start to grow, and you face the inner burocracy, and the codebase reach 500+ thousand lines of code, then these concepts start to emerge. DevOps culture, workflow automation, test automation, ownership, governance, acountability, etc. Because suddendly the individual performance doesnt extrapolate to the team performance anymore, coordination become more dificult, and the pace of shipping features start to slow, then these kinds of insights start to be more valuable, even when no direct accionable is mencion.
This talk and Lean management practices are in alignment. Value stream of software development processes is often set and rarely optimized consistently. Good reminders.
This talks is excellent and it has been featured in the last issue of Tech Talks Weekly newsletter 🎉
Excellent video. Thank You. I really like views that step back and look for similarity across apparently unrelated fields. The social scaling really resonates with me as I am really interested in the concept of autonomy@scale rather than Agile@scale which is where I think most organisations are failing to get the benefits that they expect from Agile transformations.
Verbose, but not wrong. Dare I summarise - organisations should be modelled on a Directed Acyclic Graph topology - directed, as in there is some value produced at the end; acyclic, in that its clear which teams provide services for other teams and there are no infinite loops; and graph, in that we accept real world has more than one parent node :)
Wow I didn't know about Stefan Tilkov, I was a big fan of his talks. Influenced me a lot.
Watching for the second time to arm myself further and start delving into this paradigm. I've run my small studio somehow similar but I know I need a well defined methodology to follow.
Fantastic talk, Team Topologies is one of those books that you want to re-read from time to time.
Another nonsensical low value video from Thoughtworks; Capital T for thought lowercase w for work.
I have to agree. The title makes very little sense in terms of architecture or complexity. It should be more along the lines of "how to grow companies to be successful". And cut down the chit chat here. Should be 30 minutes. Guess they pay Thoughtworks talkers by the hour.