Continuous Delivery Foundation Ortelius Project Meetings, 20 May 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Team Topologies from the field

Description

Presented by Sergio Canales at the May 20, 2022 Ortelius Visionaries Summit

Team Topologies are the leading approach to organizing business and technology teams for fast flow, providing a practical, step-by‑step, adaptive model for organizational design and team interaction.Let's talk from the field how this comes into reality.

A

Hello, everybody welcome to our telus visionaries 2022.

A

um Today we are going to talk about team 2 topologies, but this version is like apply in the field, so this is experience from a real project, so I hope you enjoyed it. um This is mainly what is tim to police. Try to do so. It's something that today is uh in the mind of a lot of people. We are going to add um a little information of what happened when you were trying to use it right, so my name is erica analyst. um This is pretty much what I am I work at red hat.

A

I usually work on transformational project or maybe in simple workbreak that are focused to change process, uh demonstrator way to work waiting where to I don't know, work itself. um So, if you want to, um if you want to reach out there, there is my email. um I will be super happy to exchange any experience so for our next we are going to start so this is uh originally hannah's an attack for an hour. So we are going to do it today in a light tall uh mode.

A

So, hang on, we are going to go a little fast, but I have, I hope you enjoyed it. So what is deep topologies? This is mainly what is team topologies. There is an official page. There is a a whole learning um process, guidance on studies about it. So there is the link you can watch it all so, but this is like the main ideas, so it it's a. This is like their big resume about team topologies.

A

um So this is the step, probably how, where you're, going to start where you're going to end uh again. There is a lot of material about that, but this is like the main stages. If you want to look it on at one page.

A

But okay, that's like the idea. That's the theory! That's like this side that tell me what I can learn. What uh how I can prepare. So, let's go to the field and try to put this on uh make this happen. Okay, so the expectation is like you're going to your organization, you're going to say: okay, this is like my instructor. This is like the the the most common police that I have, the the interaction between them.

A

Okay, let's try to do that and- and let's see if I can like match this on my organization, but what usually happens is that um not everything in an organization is so structured so like uh well understand it um usually, usually when you are going to start a project and you want to, and you are going to work based off team topology, you are going to say, hey, okay, I need to like.

A

People from different areas, because I need like uh I need diversity in one team that can solve a lot of different aspect of what I need to accomplish, but in reality, usually you're just going to have like a few resources, some expertise, some role, some people with some experience, and usually it's really hard to get this nice topology, where you are having like good connections to a lot of departments.

A

um If you are trying to deliver some workloads, you're, probably going to depend from networking from storage for platforms infrastructure. So but what usually happens is that is like your team, developing something with uh maybe a counterpart from from other areas. At least one that probably is going to talk with a lot of people will try to do it and after that, you're, probably just going to have a a really nice interaction with some ticket platform, or something like that. So I'm trying to say that is super hard on the on the beginning, you're.

A

So you are having so less and you have so much to do so. Let's speak again a little ahead. So what we can do in the beginning is pretty much a project team that is not connected at all with other teams. You need to identify some stuff. First of all, you need to focus on your team. Okay, that the the main thing you need to optimize.

A

What is your team doing because, usually on an organization uh you're not going to have like extra time extra people, you need to do like pretty much more with the same, so you need to optimize and optimize it pretty much developing your team making them giving them tools to do his work faster in efficient way. So you can save time at the end, you can have space for your project needs.

A

After that, you need to uh give confidence to that team, and usually that is like accomplished goals. There is no team that is going to move forward if it's not like uh giving success or having this image that they are being successful in what they are doing. And, finally, you need to identify what is like what is happening around you, because you're not going to uh make this happen just by yourself. Okay, usually you are going to have like this a lot of teams that are disconnected.

A

So, if you you, you see all the x mark, it's just because you're done having that interaction. So, first of all, you need to uh met all this team and you need to start like making connection a way to talk consistently have communication with these teams. You need to change a lot of aspect of the culture. Here is a little short list for this, but it's longer than that, but this is a a way resume of what you need to change.

A

After that you need to make a trusted environment, usually in organization you're going to discuss. Who is makes more sense. Who has more knowledge, but I I recommend you always work in. In fact, right always do something look like give something that is is working. Try to avoid conversation about what things should do, what is probably going to happen, try to work what it's happening itself like in reality the logic team.

A

Your team is the main thing and even for team topologies, what is you're going to have at the end is what the team is developed itself. It's not never it's going to be the same to one to another. An organization is just give the space to your team grow and your team is the one who's going to is going to define. What is the structure?

A

What is the interaction, or what is the work is going to do is going to have, if you give the, if you give them the space to grow, okay, give people achievement like for for a person like recognize themselves when you they change something they do a good impact when they support each other. When they give you opportunities, give rewards you, we usually do stuff like giving. I don't know at the end of every every spring we give like a ticket for for having a a meal for having a pizza having a drink.

A

I don't know but give rewards, make an spa happy to to cheers to to to recognize each other. So what we are having from this session this this session, it is really hard. It's a really hard work to do. Team, topologies or work on your teams, but remember you need to support your people. People at the end are the people support people, and that is the thing that is going to help you to build up structures and connection okay.

A

Don't forget that agility is about people, it's not about technology. Okay, agility is not software development itself. It's about people. Doing that, so don't forget it, and at the end solutions solutions are implemented. They are going to be successful and make sense only if there's you have people who can can support that that I don't know tools it uh itself are not solutions are just tooling are just technology. You need someone that is.

A

Doing a a a good would work with that. So don't forget it. Okay. This was like the lining tool. This is not how to like directly implement gym. Topologies is like all the tips you need to know to be sure that you can grow in a in in team topologies to achieve team instructor to achieve interactions to achieve like a major state of your of your organization. So don't forget it. People are the center, and this is like what you nee usually need to focus to make this happen.

A

Okay, so again, thank you um any question any more details about how to do it in their in in your projects. In your experience in your organization here I am here, are my contacts so see you soon.

A