Evolving Enterprise Architect practice at AT&T Mexico | EA Global Summit 2024
All right, so I assume everybody can see Ryan, are we speaking? All right, fantastic. So again, thanks for the introduction, Ryan. And I'm so glad Nathalie, the leader of the architecture effort at AT&T Mexico can join us. So we're going to be talking kind of evolving the architecture practice at AT&T Mexico.
So we'll do a brief, you know, you know, introduction of AT&T Mexico, a little recap of what we talked about last year and then, you know, some of the progress we've made and then we'll dive into the details. So just a little bit about APG. Again, our basically our focus is on trying to help people adopt industry standard best practices around architecture and engineering. And a big part of that is participating in standards organizations like the OMG, the Open Group INCOSE and of course for the telecommunications industry, the TM Forum in the Open Digital Framework and Open Digital architecture. And then Nathalie, you want to tell us a little bit about AT&T Mexico? Yes, of course. So we are in business since almost nine years.
We come from a merger between 3 Mexico Teleco company. We arrived and took over. We represent today 13% of the market. We have the second largest telecom in Mexico and we have 22,000,022.6 million at last month's customer ongoing. Excellent.
So I'll just do a quick summary of what we kind of talked about yesterday or last year about the foundation. So the whole idea was, you know, to uplift the architecture practice it's, you know, and establish a collaborative dynamic practice, make that a way of working, try to embrace the concept of reuse. So that's the one of the themes of this is trying to reuse things like TOGAF, ArchiMate, the TM forum reference models, you know, to make all these standards work together in a practical fashion. Again, have, you know, continue to provide guidance and mentoring to teams across the organization and of course have implemented a set of tools to support that. Of course, Sparx Enterprise Architect Pro Cloud Server and Prolaborate, but we're also integrating with ServiceNow, Alation and WS O2 to get other data into the repository.
So I don't know, Nathalie, if you want to talk a little bit about what we've been working on lately. Yeah, lately we really focus on open agile architecture. We are looking to migrate all of our legacy or monolith application into component TM Form Certified to accelerate transformation to a digital landscape, but also to impulse even more the TM Forum Open API on and allow us to become a partner not only as telco, but as data on network, thanks to the TM Forum Open API on Camara Consortium. So the company is opening as a way to become provider of that as a service and network as a service.
And then as we'll talk a little bit about where we kind of recent development that's gained a lot of momentum is to try to capture a set of patterns that are going to guide how people, you know, make this transition from monolithic to event driven micro services and of course updated our meta model. We'll give you a peek to that. And there's also been some progress made in the, the alignment with the digital transformation office as it relates to mapping to value streams and capabilities and also kicking off some API governance and, and just some tool updates. We've updated to the upgraded to the latest and greatest from Sparx. And I've got some cool little tool things we'll show you along the way around Prolaborate.
And we're also exploring, as many people are, I think we know what role artificial intelligence is going to have in architecture. And so we started to kick off a, a pilot project at AT&T Mexico to explore those options. Go ahead. So I, I don't know if you want to add anything to that, Nathalie, or if that's good enough. No, no.
So it's summarized, pretty good. So pretty similar, but not going to dwell too much on this 'cause this is just really again, reflecting what we started with a couple years ago. Really the only major difference is that, you know, while we're certainly using TOGAF and the architecture development method, we're being formed by open Agile architecture to try to execute that life cycle in a modern agile format. And I don't, it's possible that there might be folks on the in the meeting that haven't heard of this before. So again, open Agile architecture is a, it's not really a new, it's a newer standard. It's been around for several years, but it's basically a collection of best practices that borrows from other efforts such as continuous architecture, scaled agile and domain driven design.
And if you look at the manifesto in the upper left, I mean, it's basically that, you know, architects really need to be involved in the lifetime of products, not just, you know, project level solutions. We want to architect our product with a, you know, holistic end to end view of the system as a whole. We don't want to just build architecture models.
We want to validate and prove that it's worth by actually, you know, implementing the architecture. Make sure that we understand that architecture is again, A-Team activity, not just something that is done solely by architects. We need to kind of take the agile approach of deferring, making critical decisions to the last possible moment, but no later.
And again, start, you know, sharing, you know, in building, improving out the architecture by building out critical customer features. So I could give a whole talk just on open agile architecture, but this is just to try to set the, the, the starting point for this. And so a part of that has been, you know, trying to describe to the architecture community, you know, what's going to be the life cycle of doing work. So we've crafted a a new architecture method based on open agile architecture. Again, not going to get into the gory details, but you know, a big part of this is trying to really, and you can certainly talk to this Nathalie, but really trying to elevate the work of the architects out of the often being team leads in individual projects. But really, you know, elevate them into, you know, contributing more to a strategy and visibility.
In that case, it's really trying to move away from the application architect on to really become solution architect. And as we have a reduced number, a limited number. So what's the best way for us to organize ourself and to be able to still oversee everything without to increase or multiply the the the workforce? Yep. And a big part of that is that, you know, other team members are going to be taking on additional responsibilities that perhaps the architects used to do.
And as many know, architects get asked to do a lot of things that really aren't architecture, but because they tend to be pretty skilled and experienced, they're a natural, you know, target by project managers to help out. But like, like continuous architecture says, you know, architecture is a team activity. You know, there need to needs to be a sharing of responsibilities across a complete life cycle. And a part of the method is trying to make it clear what types of artifacts the solution architects need to create. So this is just a example, you know, in the lower right hand corner, we've kind of partitioned them into EA artifacts, portfolio artifacts, solution artifacts, and governance artifacts. I'm pretty sure these are the solution artifacts.
So things like a solution vision context diagram, again, a high level application and deployment diagram, and then a number of different models to try to demonstrate how the the solution is aligned or not with the target architecture. A big part of, again, as some may know, particularly with scaled agile is, you know, focusing on an MVP a Minimum Viable Product. And as many may know, you know, that's really supposed to be designed to try to see if the the vision of the product has any, you know, if it connects with the customer particularly and it's going to, you know, be something useful. So it tends to focus more on features, but then once that, so we want to be careful about introducing too much hardcore architecture early, too early, particularly if the MVP ends up demonstrating that it's not a good idea. So we, we really wanna, you know, jump in after the MVP to, to provide this agile architecture guidance.
And a part of that is, you know, we've, we've had a tradition at AT&T Mexico and keeping track of all project artifacts in the EA repository. We had a template that kind of represented the legacy old method of doing stuff. Well, now that we're transitioning to open Agile architecture, we've got a new template.
So this is the organization structure that people are expected to follow when they do the agile architecture method. And one of the things that, you know, came out of that actually from our legacy work is, you know, being able to publish a dashboard about a project without having to manually assemble it. So this was a, a little a new tool thing that we created. It's basically a script that runs in Enterprise Architect where you basically you pick a package and then it will basically go through all of the diagrams and the elements and child packages and all the child diagrams and automatically build a dashboard of diagram thumbnails. And so this is again, another part of how we're trying to leverage the platform to help us, you know, accelerate projects and not have architects, you know, have to do a lot of messing around in tools to expose their content to, you know, stakeholders. And then just to give you guys a little bit of an update, you know, we've one of the, you know, we had a particular way of crafting our landing page in Prolaborate 3, which is where we were coming from.
And then, you know, due to some changes in how dashboards where it came up with a different approach. But the whole idea is that we want to really provide without having to go look in the dashboard drop down, which in our case, I think we have, you know, Nathalie, upwards of 150 dashboards. There's a lot of information. Yep. And so having some way to help people navigate to find that content is how we, we built this again, collection of landing pages, starting with the main landing page that allows us to get the different types of content.
And a big part of this is grounding this in a refined meta model. So people that may have joined us last year might find this familiar because it is somewhat similar. But again, our focus is significantly on the things on the right.
So in particular, still focusing around business applications, which are those pieces of software that are registered in ServiceNow. And we're trying to do 2 things with that, one kind of from a, an agile architecture position. We want to be able to keep track of architecture decisions that are made about evolving improved and new business applications.
And then when decisions are made that perhaps don't follow architect recommendations because of real world issues about time and money, we want to keep track of technical debt, you know, associated with those decisions so that that doesn't get lost as it often does in many organizations. And then we've got, you know, of course, a mapping to a big critical part of the TM Forums open digital architecture, namely a family of ODA components that are mapped to open APIs. And then trying to understand a little bit better which APIs, that are currently in the AT&T Mexico landscape, which of those should conform to the TM Forum Open APIs. It's not going to be 100% match all the time. Again, as Nathalie said earlier, trying to make sure that that, you know, new development is aligned with the open digital architecture as much as it's feasible.
So Nathalie, I don't know if you want to talk a little bit about some of the work we've been doing with the digital transformation office. Yes. So what we're having, we're having all of our value stream per safe definition where everybody, all of the software factory within the company and we were having our type of self as architect to identify which functionality, which business domain, which capability we were really working on. So we, we made this little bit not easy job to go a factory value stream initiative on map to the value stream of the the, the BA Guild on the capabilities to get to the level of the business process of the TM4. And that to allow us to see where we were spending a lot of money or time on see what we could improve to adjust with our strategy.
And as many people know, a lot, a lot of challenges many organizations have is because of how the business is organized and then how the IT is organized to support the business. There's a lot of people changing the same kinds of things for different reasons and different technologies and different applications. And you know, this is an important step that we found to try to help bring awareness to this, to the technique management so they can make informed decisions about, you know, spending money and allocating resources wisely to get the outcomes that are required to support the business strategy. And so a big part of what we're going to, you know, what we started several months ago and it's going to be a big part of our, you know, story in the upcoming year, well more than a year probably, but is, you know, alignment with the TM forums, open digital architecture.
And a big part of that is described by a set of what are called ODA components. And you can see that in the upper left image where each of the ODA components is represented by a hexagon. And that's really a call out, as many may know, to the idea of a hexagonal architecture pattern where, you know, we have basic, you know, ultimately these ODA components are logical representations of micro services. So completely, you know, stand alone self, you know, independent deployable, you know, software asset.
And as as Nathalie mentioned, one of the programs at the TM Forum is there are, I forget the number, but there are a lot of vendors that have gotten their solutions certified by the TM Forum to be conformant with the requirements of each of these components as well as conformant with the open APIs that each of those solutions maps to. So I don't know if you want to talk a little bit more to, you know, the strategy there Nathalie, particularly around package implementations. Yeah, well we started our open digital transformation 2 years back concentrating trying to remove relevance of some of our dinosaur or monolith applications on this year. We well to next year we have a plan to incorporate in addition of the core commerce management on the party management go work more in if you want by by 2027 we want to be able to have 80% of for capabilities handled through ODI components on open API TM forum certified.
Why not only because we want flexibility, we don't we want to remove dependence with some provider. We want to avoid black box that we have today, but we also want to be able to interconnect with the telecom ward with all of the companies will want to have service with us. How the best way that to be using this architecture where we all expect or speak the same language. Yep. And in, of course, in a big part of, you know, modern application development in most organizations is, you know, you should reserve the fund, the, the funding resources and associated risk with custom software development to those places where it really is essential.
And so I think a part of AT&T Mexico strategy is if there's a vendor solution out there that meets our requirements that's aligned with the TM forum and certified that really, you know, we should be looking at those solutions 1st. And, you know, only through, you know, exceptional circumstances would we disqualify them and decide we can do better ourselves. So again, you know, trying to make sure that, you know, we, we, you know, for software development as we all know is an inherently risky thing. And it should be, you know, in custom software development really should be reserved to those places that we've decided really represent a competitive differentiation where that type of investment, you know, makes sense. So just for people that you know, perhaps aren't familiar with all this in the lower right hand corner. Well, firstly, in the upper right hand corner is a representation of core commerce management as Nathalie was talking about in enterprise architecture.
So just FYI, as people might know, you can turn custom style on. And one of the things you can do is you can turn the rectangles into different multi sided polygons. So we were able to transition the transform those into the hexagons.
But then you know, it's more than just the hexagons. The TM Forum has a detailed spec for each one of these components that not only identifies which ETOM business processes, which are the yellow rounded rectangles in the bottom are applicable to this component, the what are called the Sid aggregate business entities. So parts of the information model, those are the dashed yellow rectangles at the bottom. But even more importantly, as Nathalie was talking about, you know, interconnectivity within AT&T Mexico as well as outside through data and network as a service. Showing which open APIs, which are the blue boxes on the outside, does this open this ODA component consume? So those are dependent APIs in this case they're on the left hand side for the most part.
And then which open APIs, does this ODA component expose or implement? Because that's how we can figure out how all those different components are going to work together. And of course, as everybody knows, this is really not a new idea. It's been around for many decades.
But it's, you know, a lot of organizations find it really difficult to deliver upon that. And the TM forum just provides a lot of great assets and services to make that a, a reality. And then one of the things that is being done again per the meta model is a mapping of the of a, a core BSS and OSS as they're called in the Teleco business, business and operational support systems.
You know, how do the current applications map to these ODA components? And we're planning on doing a four level mapping. We're really just finishing up the first level, which is, is doing a mapping from those applications, which again are coming from ServiceNow of which of these applications implement the functionality of the ODA components, but aren't doing it with the open APIs. But at least from a process and a data and a functional perspective, they do perform the same functions and but then the the next level is going to be mapping, you know, as particularly we're going to be doing migration from a couple of monolithic applications very soon how those are going to get decomposed into ODA based micro services. And then we're going to show which applications, you know, either fully implement all of the APIs of an ODA component and that'll be a different colored colored circle, or partially implement the APIs because again, not necessarily one piece of software is going to implement all of them in every single case. And then the fourth level that we're going to get to eventually is mapping which ODA components does this piece of software depend upon. Yeah, But this was a this visualization again is based on the mappings that exist in the repository, but again, was created from a script and enterprise architect to generate this kind of custom traceability view in Prolaborate.
So whenever we update the mappings, we can regenerate this matrix knowing that it's always going to be up to date and consistent with what we see in the repository. And then, you know, this is just, you know, showing some different views of the same thing because that matrix is kind of pretty big. I mean, as many people know, matrices are great ways to show, you know, what things are connected and what things aren't connected. But you kind of have to read the whole row or the whole column to kind of get a sense of how it all aggregate. So this, you know, helps us validate what, you know, is, is obvious when you look at it that a big, a great number of these core applications are supporting bill calcul, bill generation, I think. Yeah, Bill generation, party management, bill calculation, product configuration management, payment management.
And again, these are, I don't think Nathalie, you know, these are surprising since those are really important parts of the enterprise. But you know, there's a great opportunity to hear for, you know, some consolidation, you know, into a smaller set of core strategic applications. And then I'm sorry, go ahead Nathalie. It's even more in our case that we come in reality from three company who become the 4th 1:00. So we still have legacy application where making sense in one of the three company, but then after group to make sense to the fourth one who arrived. But today is where the difficulty is, is when an application start to do a little bit of everything.
There is where our job become even more complicated because when we want to optimize or or start to remove pieces, decompose, decompose the monolith, that is even more difficult because it's 'cause disarmament. But I think that's happening in many companies even more when the company has been merged. And that's often a consequence, you know, of these acquisitions is as many people know, you've got, as Nathalie said, you know, a collection of applications that do the same thing, you know, in, you know, for different customer segments or different products or the same customer segments or the same products. And a big part of, you know, what increases the complexity of the application land state is are those acquisitions 'cause, you know, you don't just acquire the customers and the products and the employees.
You require a couple of these, you know, IT assets and and you know, a big part of organizations being successful, you know, moving forward past acquisition is trying to figure out how can we become masters of this complexity as opposed to becoming victims of it. Because again, but that's where, you know, we think architecture really has an opportunity to shine because that's one of the important, you know, outcomes that architecture is trying to deliver because there is inherent complexity in a lot of these business. But you know, we don't need to make it any harder than it already is.
So to help guide the the new solution teams to align with open digital architecture and the philosophies that support it, particularly event driven architecture and micro services, we've collected a, a set of I think we've identified about 130 patterns right now, Nathalie, which is a lot and far more than we're going to use immediately. But but you know, in a lot of cases, you know, you want to cast the net wide and then we're making some very deliberate decisions about, you know, these are the 10 or 20 patterns that are really critical to support some of the monolithic decomposition and legacy retirement activities. And so, so step one again is collecting all of those patterns and then we're starting to elaborate them so that we can, you know, provide guidance to the solution teams. But a big part of what we're going to be working on in the upcoming weeks and months is getting this out of kind of theoretical land and actually get it into practical application.
I don't know if you want to talk about that, Nathalie. Yeah, it's where we, we are really extending our knowledge to the solution engineering, to the solution architect from the entrepreneur architecture. And we're creating this task force to start to break the monolith and go to the component.
So for that is where we are going to ensure that we are aligned with suspect terms and that we provide them and they understand them because we have to be also training. So try to really work hand by hand with whoever is going to implement ODA capabilities. So it's good timing now to have all of that because we are creating this this sales of work with, we are looking at a mix of architect in solution, architect, engineer, developers to be able to to work also in pattern area with a with a provider. But we want to keep the skills in the house.
So this is interesting approach where entrepreneur architecture is not anymore in the prettier repository, but is a is a live on on is really used day by day on on. We are reference and we are helping and participate. And one of the big things that we're going to be helping the teams with is, you know, of course we want them to, you know, document the critical parts of the architecture in the repository in accordance with the new agile architecture method and structure. But for patterns particularly, one of the big things we want to try to get out of it as soon as we can is harvest examples of how these patterns have been used at AT&T Mexico. So, you know, we're, as you'll see on the next slide, you know, we're starting with, you know, pretty typical generic descriptions of the patterns that hopefully people again understand why they should care about this pattern, what this problem, the problems it solves, the side effects and consequences and implications, you know, different kinds of strategies, all that good stuff. And then of course, there's models of the patterns.
But what's really gonna, I think make this resonate with the, the, the, you know, the practitioner community is, hey, you know, I get the idea behind this pattern and what it means conceptually. But, you know, if I could see a real world example of how this pattern was used here at AT&T Mexico in the 21st century, you know, that's really going to help, I think, with people accepting these as legitimate patterns and also provide, again, a lot of great contextual guidance on, you know, what does this really mean in the real world. So what we're doing is, you know, this kind of represents our end game. Well, not our end game, but you know, one of the steps. So kind of our approach is we have a catalog like we said, you know about 130 patterns we and that helps us again prioritize and focus on those subset of patterns that are most critical. So they've got a name and they've got a description.
And then what we've decided recently is we're actually going to take an intermediate step. So, so that before we just go ahead and detail out all of these patterns, again, we're kind of trying to do it in a segmented, prioritized way, but we're going to create for some of these patterns and outline because we don't want people to feel like they need to wait until the pattern is completely specified in accordance with, you know, best practices, which is again, represented here that, you know, and, and again, trying to embrace the agile nature of this stuff, which is, you know, we don't have to have a perfect description of a model of a pattern completely done the way it's supposed to be done. Just, you know, the name of the pattern or description. Maybe a, a quick overview that we might copy, you know, from, you know, a PowerPoint slide or a website and maybe some links, you know, 'cause at least that'll get people going. Again, it doesn't need to be, you know, perfect.
And then as we work with the teams applying the patterns, we'll get those examples that we'll be able to supplement the core pattern descriptions and again, continue to evolve the formal description. So, you know, we're, we're following again, a pattern for patterns, as you might not be surprised where every pattern, you know, has an intent, you know, a description of the problem and the the forces that are causing us to need to solve some sort of problem. But then, you know, we're trying to get a little formal with, you know, what are the parts of this pattern. So that's represented by, you know, kind of a class like diagram, although we're still using Arkhamate.
But of course, one of the cool things about Enterprise Architect is that while, you know, Archimate is the language of choice for TM Forum and AT&T Mexico, we can still use some of the UML features of Enterprise Architect. In particular, on the right, we're using sequence diagrams, you know, that represent the behavior of those patterns. And then I think the last topic, if I'm not mistaken, Nathalie, is API governance. And so we're, you know, this is a draft version and so it's not finished.
And there's of course a lot more to it. You know, people will recognize the the link icon in the lower right hand corner of some of these processes. So there's definitely more to it than just this.
But as many people know, you know, when you start transitioning into, you know, an, an API driven approach without governance and oversight, you can find yourself with an over proliferation of APIs that do the same thing that aren't really well governed. And again, that's a part of, of, of, of what the EA team led by Nathalie and Tony are trying to, to help the organization focus on. You know, it's not just about creating APIs because that's what people do today. We need to create the right APIs at the right time and the right way. So I don't know if you have any, you know, comments about that.
Nathalie Yeah, yes, we have now strong tools to to do API getaway where we can do Slas, we can do a lot of things, but if we don't control what is a blooded there on the sometimes, you know, basic things like who is the owner? What is the description, what is for? So we did this work with our new newly APIs with our core management components we already deployed last year. But now we need to bring on board everything else from the ESB, the billing system, prepaid post pay because how do we want to improve it if we don't know as as is on how we we can ensure is no is no duplication if we don't know what we are. So that is the a challenge on the there where we really need to do governance. If you want more like to become police of if you want to do API, you need to come by us 1st and chauffeurs that that don't exist is the one who exists you want to improve. And if you are following the TM for home specification, Yep.
And so just like application Yep. And so and just like application development, you know, there's you know, there could there could be multiple APIs that kind of have overlapping requirements. We want to consolidate those.
There might be APIs on some of the legacy platform like ESB that we want to move away from and we need to migrate, you know, to a new open API implementation. And then of course, you know, eventually deprecate and retire those APIs. So I think we just got a couple of minutes left, Nathalie. So I think Yep. So here, here we are I guess the conclusions, I don't know if you want to wrap it up here, Nathalie and then we can maybe take a question or two if there's any time. Well, I think we're in a very exciting time where we came from to be a far away group where they're not sure what they are doing to now really become focused on the CIO put architecture on data as part of this main pillars.
So it's where we were supposed to be and we are finally getting there on it's going to be demanding, but interesting. All right. Well, I think that's what we wanted to talk about. So like I said, I don't know if there's any any questions and we might have a chance to answer a couple.
Yep, there are a few questions. So the first question is well comment, this is some great work is AT&T in Mexico playing on contributing some of this work back to the TM forum for other telcos to leverage? Yes, of course you guys are always doing a lot of sharing. The next question, we have been working with our peers AT and TUS on cricket and the idea is we participate also with the be a guilt. The idea is, is to share what we are doing with everybody else as well is why I'm here today. OK, The next question is for Chris.
Chris, when you share the Meta model slide, there look to be multiple standards blended together. Is this unique for AT&T Mexico or is the pick and choose approach becoming more common with organizations you work with? You know, like obviously it kind of depends, but you know, obvious, you know, one of the nice things, you know, 2024, there's a lot more, you know, relevant content from many different standards organizations. Some of them are, you know, industry vertical like the Forum, some of them are more practice oriented like the the Business Architecture Guild or Nkosi in the case of systems engineering. So, you know, I think there's an opportunity to do that kind of hybrid blending of standards today that really wasn't possible maybe, you know, certainly 10 years ago. So, you know, I, I think that it is becoming more prevalent in, you know, in, in the different industries that I've been working in.
So it is not uncommon. But for us was was our vision. We wanted to bring Toga, we wanted to bring Ashimet, we wanted to find a tool where we could really implement on not only other definitions and we wanted also to leverage TM Forum. So it's where I met Chris at that point where I was OK, nothing is there, what can I do? How can I do it? This year we continue because we added the business architecture, guilt, value streaming capabilities that really help us to. I think his idea is to take the best of each world on to make work what is good for you. We are not purists.
We are trying to be practical. We are just in. In our case, we also had the Agile Software factory, where also sometimes the definition of the names were the same.
I was confusing everybody, but we tried to clarify. But you need to. You cannot only stand one. I'm not depending on the telecommunication. We're in telecommunication, so we must have TM4, but TM forum was not suffering this really hands on was was not a tool where you could extend and implement their frameworks and it's what we had with the ES parts. OK.
So Nathalie, another question for you. When you were introduced your, it sounds like your role spans both enterprise architecture and data governance. How are you bringing these two disciplines together and what's your vision there? Well, for enterprise architectures, you need to have inputs, right? So our inputs at the company level was the application with we need to know our assets.
So with why we integrate with the ServiceNow 8 PIMCMDB and we, we also needed to know our data, right? So we brought to the company things we didn't have yet or the concept that the catalogue steward. More when we were also migrating to data like in the cloud. So was even more important to understand all of this data we were having because the idea is to don't migrate things that you don't use. So we are at this stage, we created the data committee. So if you want my, my data governance part was really more focused on bringing the platform on the methodology.
But the idea now that the data committee become also more multidisciplinary so that the business is more involved. So we'll have more like if you want the consultant position, because I want to dedicate more time to the enterprise architecture part. But we need to guide them because isn't it? We don't get the tool and Isaac is sure at the beginning we are integrated with many things that we need to be able to model properly on to take the decision. So I don't know that answer the question, no, that was good. And then the last question and then we'll wrap up is this sounds like a very ambitious architecture effort.
How are you going about finding the right resources with the right skills to staff this project? Well, I can say that the people I'm working with, I'm working with this with them since long time they have been following us. We were part of DIRECTV LATAM, become AT&T LATAM and then we went to DIRECTV on to AT&T Mexico case. I know him since like six years more something like that. So and I think it's a small world where people who left, who came back who even like Venezuela, I had a team in Venezuela who left who went to Mexico because he could not stay in Venezuela.
And I didn't know that I was going to be working in Mexico a year later. And I contacted with them people that are in Colombia that they could not bring with me because was not the entity of AT&T there. But to come to work for us who a provider so much it take to change company or came after to work with us to as a provider.
I must say it's a small word. And when you have somebody where really has the knowledge of the the telecommunication plus the knowledge of enterprise architecture solution, we take them with. But of course is what is a small team. So what we're really working the last two years is to make grow the rest of the team.
What we are Hive enterprise architecture was very small. We're like 10 people, but last year of CIU trust us on on board together all of the architect to work in the different branch speciality on the we finally were happened to make a difference because if you were not only preaching to them. We were part of the same team on the same year. Archie same objective, which is easier. So it's what we are now and now we need to deliver because I think this year is a year of the transformation. OK, great.
That was that was a great answer. I mean, I think events like this give people an opportunity to network, to find other, other people with the skills and knowledge and experience they're looking for to, to, to make those connections. And you're right, it is a small world and you're very often the people we've worked with in the past become our team members and our partners in the future. So that's fantastic. OK, so let me go ahead and and wrap this up.
I want to start by thanking Chris and Nathalie for joining today and sharing their insights with us. And thanks for all the people who attended and participated and asked the questions for contributing your time and participating. The session recording will be posted on EA Global Summit website and the prolaborate YouTube page after the event. And if you'd like to connect with Chris and or Nathalie, you can reach out to sales at Sparx systems dot US and we will get you connected. If you happen to be also attending the Ankosi Western States regional conference this week, Chris will also be there if you want to talk to him live.
So the next session will begin in a few minutes. You can find the session link in your registration e-mail. Our next discussion is actually a a panel discussion where we're talking about the biggest problems, business problems that organizations are addressing through architecture. So it's going to be an exciting, exciting discussion.
So we thank you again for joining this session and look forward to having you join us on the next session of EA Global Summit 2024. Thanks and have a great day. Thanks everybody.
2024-12-26 07:35
