 Welcome all to this interesting session on game-driven development. And I'm excited to hear from our game on the topic, right? So and over to you, okay. Okay. Hey guys, hi. Nice to meet you. I'm going to share my screen right now. Okay. So today guys, today we are going to, I'm going to share with you. Sorry. This talk, which is continuous on game driving development. Game driving development or GED is a framework that I designed it, you know, to help development teams to, you know, to use gamification to mature and adapt new ways of working, right? Like DevOps, like some software engineering practices through games, right? And actually it's also through technical activity. That's the idea of this framework. So as any other framework, you are going to see some steps, right? Some recommendations that you can apply if you want to follow this kind of approach, right? So just to make it simple, imagine that you are in your, in your companies and you have a challenge, right? You need to adapt new ways of working, like DevOps practices or cloud transformation or microservices or some agile testing practices, right? Whatever, whatever new, new ways of working. So game driving development is a good option. So you can design some game. So you can foster and you can engage and motivate people to, to learn new, new stuff, you know, new practices through this framework, you know? And as you know, right? In DevOps, we have, we have continuous deployment, continuous integration, continuous testing, continuous monitoring and so forth. So the idea is that game driving development is part of continuous time, right? Which is the human part of, of DevOps. So that, yeah, that's my talk about it. I'm going to share with you this presentation, which is a kind of foundation part of the framework. And then I'm going to move to the, to the framework itself, which is a Myro where you can see, actually a Myro that you, you can, you are going to see the entire framework, right? With all the steps, we are going to also play with the framework in some parts, with an asset or a framework which is named that design, game design canvas. We are going to run, we are going to create a real game design using that canvas. Okay. So that is the purpose of today. Okay. My presentation, my name is Jorge Castro. I'm, I am from Lima, Peru. I work as an AI coach, DevOps for a manager and test manager. Those are my, my roles actually. I work for entity data right now. So I'm very happy to be here. Here you can see my contact information. Please, please, please add me to your link in accounts. It would be awesome, you know, to have you in LinkedIn. You know, to try to share knowledge, you know, have some discussions, getting touch with you that would be great. So I can learn from you. Maybe I can share with you some ideas. If you like some, some, if you like some, some ideas in this talk, I would be very happy to share more knowledge with you. You know, so please add me to your LinkedIn accounts. That is, that is my LinkedIn. So thank you. Okay. I'm going to start with, I'm going to present this video. Yes, a kind of introduction to a topic. This video is about a real example of gamification in a serious business, right? As you know, well, maybe if you, if you know, a serious business is a kind of, a kind of real problem, right? Real problem that we can have in our business, you know, in our companies, in our enterprises and so forth. And also a serious business can be a problem that we can have in reality, right? Like a, like a traffic and so forth, right? In this video, you're going to see a real example of that is related to improve, you know, that the city pollution, you know, is about recycling, recycling basically, right? Try to improve the, how we can recycle bottles, you know, how we can take care of our, our city and so forth, right? It's about recycling. So I'm going to share a video with you. It's a short video, so please check it. Okay, great, great. So I'm going to go to the next slide. Yes. So actually a team, what you, what you saw is, is a kind of real example of gamification. You can see this bottle, bottle arcade game, right? Where people can recycle bottles, right? I'm using some gamification approach and having fun, right? You can see the video of the people where they, they, they, they were recycling, you know, the bottles. They were, at the same time, they were, they were having fun, you know, doing that, right? The kids, you know, the younger people and the adults will. So that's the idea, right? And also, also, also another message from the video is the, the theory of fun, right? Fun can change behavior. And I think that is true, right? If I enjoy something, I want to change my behavior most probably, right? So that is a real powerful approach. In gamification, the theory of fun and how it's, how we use it to change behavior. And as you know, right? Because as I said at the beginning, I work as a guide coach. And I suppose that some of you also work as an, a square master, maybe, or a guide coaches or lead developers, or maybe DevOps engineers and so forth, right? And you know that as part of our job is trying to change ways of working, right? Change some, or improve or change, right? Or also mindset or something like that. If you are going to apply Kanban or Spram or save or DevOps or microservice reformation, any of them demand some kind of behavior in our practices. So theory of fun is something useful for that, right? To change behaviors. So this is Yucacho. You know, you know, you know, you know, you know, you know, you know, you know, you know, you know, you know, you know,idos, of course there's a lot ofste , of course, there's a lot of things. So this is Yucacho. Yucacho is a kind of guru about gamification in the world. He's, this is one of his quotes, imagine a world where there is no longer a divide between what you have to do and what you want to do. That is the powerful power of gamification. And actually that is true, right? I know that maybe some of you, when you go to work, of gamification is also that, right? Try to improve our work, try to make our work something great, right? Something that we enjoy, right? And I think that is a really powerful message. And that is why I love gamification, and that is why I use gamification for my DevOps objective, my object transformation projects and so forth, right? Okay, another quote that is quite interesting is actually that is from Thomas Alba Edison, you know, the inventor from US. He said, I think work is the world's greatest fan, you know, because actually Thomas Alba Edison, he did really enjoy what he did, right? Invent a lot of things, right? And I think it's about passion, it's about having fun while you are doing it. And actually that is why I designed this framework, right? Because I think gamification games can motivate people's passion, having fun and also change some practices, right, for the best. So that's my approach, right, from today. Okay, let's start with the story, right? I'm going to share with you a story. Once upon a time in a common enterprise, okay, imagine that, as I said, right, at the beginning, imagine that you are an AI coach or a DevOps manager or a kind of technical lead, something like that, right? So imagine that you are working in your enterprise and you have this challenge, right? The challenge is that, you know, is improved flow and business through building agile DevOps and more collaborative ways of working at scale for distributed teams. So imagine that you are working in an enterprise, right? And this enterprise is, you know, is in the middle of a kind of agile formation or a deep transformation or something like that, right? You need to adopt a new way of working. But besides that, imagine that you are working a kind of distributed model. So you have teams in Latin America, in US, in India and so forth, right? It's a huge challenge, right? If you want to try to help to adopt these new behaviors, right? In a company, DevOps and agile and so forth, it's a huge challenge. Yeah, actually, this is a real experience. Okay, so, okay, for this challenge, you can try experiments, right, to try to sort this problem out. So in our case, we tried this first experiment, which was trainings, maturity practices, roadways, right, route maps, right? Trainings are route maps, the classic thing, right? If you want people to learn about continuous testing or continuous integration or Kanban or Scrum, okay, train them, right, give them trainings and also a route map to mature the practices, right? I think that is the traditional approach that we use right nowadays. In our case, we noticed that our approach was independent efforts without collecting the dots. That was real, actually, in our first approach. As I said, we did a lot of trainings, some independent dojos, some karas, some coding events, a lot of hackathons and so forth, but we failed. We failed. We didn't build ways of working as consistent as we looked for. Actually, that is true. That is a real story. We failed. Because at the end, we noticed that that was okay to do some kind of trainings and dojos and karas, but we need more than that, right? Especially for our context. We have a hundred of themes distributed themes in different continents. We have a large enterprise and we need more than that, right? We need a kind of strategy and try to make people really enjoy what we are doing to buy the idea and really apply those new practices. Actually, we failed, but we learned, right? What we learned? We learned that we needed a system strategy. I think that was something clear for us. Also, we learned that the best learning lessons were through games, right? Yes. We applied some games approach in the first experiment, and those experiments were the best. When we introduced some games as part of the learning, as part of the experimentation, they were very useful in our teams. Games was a good option for us, so we need to improve that approach. Also, we learned that we needed to sponsorship from our upper managers, right? I think that is something true. No matter what we are doing, right? If you are going to do AJA, the BSEC-OP, so capital formation or whatever, you need to sponsorship, right? You need some sponsorship from your managers. I think that is something quite important that we learned from that experience. Just a little video. I am going to play this video again. It is a short video, only 20 seconds, but please check this video. Please ask yourself about what you can see in this video, okay? Basically, what you can see in this video, in the video, is some children playing football. They are passing the ball using their heads one by one in a kind of process, and then the final goal is to put the ball in the basket, right? That is the goal, right? That is why he wins his score, right? Yes. Thank you. I am reading your answers. Thank you for that. You know, that is what we notice, guys. Actually, that behavior, right? That is collaboration. That is having fun. That is approach to have one goal as a team, to share, to collaborate, to support each other, to motivate people. That was what we observed in our first experiment when we applied games. So we say, hey, that is the formula, right? That is the approach, right? So that is why we tried this second experiment, which is this framework, basically, a continuous fun approach, game and development framework, aka GED, right? And also, we put this name saving the world, right? Try to make the world more fun for people. Yeah. So that is what we did in this second experiment. I am going to move. Okay. So this is the framework, right? As I said, the framework GED, a game-driven development, as any other framework in the market, I have some, the framework has some steps, some ways of working, you know, that you need to follow if you want to apply it. We have nine steps in the framework to, basically, the main, as I said, right, that the framework's goal, GED, the objective is to help teams to face a new challenge, a new new ways of working adoption, like DevOps, Scram, Agile, whatever, right? A real business problem, and help them to design a game, right, which we use the steps so they can apply in this game as part of their daily work, right? That is the other framework. So we, the framework has nine steps. Start with why is the number one is basically the purpose of the game, right? What is the problem and what is my why, right? Why am I going to do this, right? The problem, basically, why? What is the value? What is the outcome of this? Number two is to try to, if you have a kind of problem with your development teams or something like that, it's quite important that you also need to first try to apply some game model-based system engineer, right? And basically, this approach is to review what you have in your architecture, in your code, in your software, so you can apply some good patterns of game model-based system engineer, right? This is part of the framework as well. Number three is name your game, okay? Put the name of your game, whatever name that you think about it. Number four is game brainstorming, which basically is work with your teams, right? To try to share ideas about, okay, how we can gamify this, right? What is the approach there? It's a kind of app game or a kind of web application game or maybe this is a kind of a different game, right? Share ideas about ideas about how we can sort this problem out with some gamification. Number five is what we are going to do today. This framework has an asset, which is a gamification design canvas, which is a canvas that you can run with your teams. And also, well, we are going to, I want to share with you the entire framework today, but we are going to run specifically, specifically the number five, right, gamification design canvas, okay? Number six is game rules. You need to define the rules of your game, you know, it's part of the game, the rules, you know? And number seven is the storytelling part. You need to design your game, but also you need to apply some storytelling practices, like you need to have a kind of big situation, some kind of challenges in the middle, right? You need to have a kind of enemy or something like a challenge that you need to face, something like that. And, you know, you need to, you need a way to get awards about it and so forth, right? Use game story patterns to design your game. Number eight is the game character canvas, which is basically a canvas where you can design your main characters for the game. Imagine that if you are designing a game for developers, you need to design, you need to design, okay, this my character is going to be a developer, but you need to prepare some characteristics of this developer, how this developer is going to interact with the game, right? And so forth. It's part of the character design of any game. And number nine is the business part, right? Because at the end, this framework is going to propose you an idea of game that, of course, you need to use some resources to make it real, right? So, more or less, you need to get some support from a budget or something like that. So, the number, the step number nine is a game business model canvas, which is basically a business model canvas to support your game idea and to prepare your ideas to, you know, to sell your idea to your managers, right? To get their support. Basically, that is the number nine. Okay, that is a framework in just one minute. Okay, this is the number five, as I said. The gamification design canvas is a canvas, right? That you already know, right? Maybe I assume that you know, right? What is the canvas? Basically, it's a visual, a visual way to organize some ideas, right, in some kind of a process so you can make new, make an approach or make a strategy about some specific problem, right? In this case, the gamification design canvas is for game design, right? The result of this canvas is that you're going to have your game design approach, right? So, you can see here different steps, different steps that we are going to check later because as I said, we are going to run the canvas with a real example, right? With you, okay? But this is the idea, right? This is a part of the framework, the gamification design canvas. This is an example. This is an example that I want to share with you of a real game that was built using the GDD, the game design framework, and in this game was, this game was made for a large enterprise, large telecom enterprise from US. I cannot say the name, but it's one of the large telecom companies on the world. And this game was called Game of Testing, right? Game of Testing. That was the name of the game. And basically, this game is for foster the adoption of new ways of working related to continuous testing in DepsiCops, right? That is the approach of this game. What was the problem? The problem was that in this huge enterprise, they were facing the DevOps adoption, you know, the adoption of DevOps practices. And as part of that challenge, they were having some problems with that continuous testing approach, right? Because we had some problems with that because of the skills of our testers, because of the culture, because of our team organization, because of our tooling stuff and so forth, right? We had a lot of problems to adapt new ways of working for continuous testing, agile testing, right? So we created this game. So this game is basically a kind of tournament, right? Which all the teams over the world, team from Latin America, team from Europe, from India, from US, they were parts, they played in this tournament, which was the game of testing. And basically, in this tournament, each team had a chance to, depending of their level of maturity and depending of how many automated tests they built, they coded, depending of the types of tests that they have, right? If they implemented functional tests, unit tests, interaction tests, security tests, performance tests or whatever, right? And they put them in the pipeline running to check codes, right? And help continuous delivery. Depending on that, right? Each team gets some points, you know, in the game. So what you can see here is the dashboard of the game. You can see here that we have the teams here, you know, some teams, some points in the team. We have some levels, we have dragon levels, we have army levels, we have some release information, right? We have some enablers of the game, continuous integration, build breakers and so forth. And basically, that is the idea, right? This is the board game, which we share all the information about the results of the game, the teams that are getting points, the best players, right? As I said, in that game, you can get points adding more automated tests in the pipeline, right? So it was a very success for us, you know, because people enjoyed the game, people want to participate, want to share knowledge, want to try new ways of working with unit testing automated, functional testing, security and so forth. And they were very excited to run those tests in the pipeline because that helped them to make more points. And that was great, that improved quality and so forth. So yeah, that was the game of testing. It was a really good approach, especially working for a large enterprise, you know? So yeah, that was, that was the foundation of the talk. So now, as I said, I have a present, I have a gift for you, and this is basically the Myro, right? As I said, this framework is free. The game, driving design is free. All the information is on the internet, actually. And actually, I'm going to share with you the Myro. I'm going to share with you the link right now in the chat, okay? But anyway, you can take a screenshot of this slide, but anyway, I'm going to share with you the Myro. We are going to go to the Myro right now, okay? This is the Myro that, basically, this is the Myro that I have. And actually, as I said, this is the framework. This is the framework. You can find here the entire framework. I'm going to share with you the link anyway in the chat, okay? This Myro is for you. So you are, I'm going to share with you this Myro. You can use it. You can use it for you in your work, with your team, with your mates. So it's for you, okay? I share with you the link, okay, in the Myro. So yeah, this is the GED framework, where we have the team, right? We have Hulk, Spider-Man, and so forth. It's part of the fun, right? And today, we are going to go to the Spider-Man section, right? I'm going to give you a quick overview about the framework, but it's going to be very quick. I'm going to share with you. I'm going to use this option to bring everyone, please join, please enter to the Myro, please, okay? Please enter to the Myro. Okay, I'm going to, oh, sorry. Okay, I'm going to do it again. Okay, I paced a link. Really? You don't see it? Now it is. Okay, thank you. People think that they don't see it. I'll type it again. It's available right now. Okay. Okay, I think now it's there. Now? Yeah. Yeah, I can see it now. Okay, guys, please join the link. Is it the Myro? Oh, you can't. No, people say that they can't. Oh, no, okay. Okay, no problem, no problem, guys, no problem. I think, can you see now again? I can see it. I can see it. I can see it. Yes, yeah, they can see it. Okay, great. Thank you guys. Thank you. Please join, please join. Okay, again, guys, this Myro is for you. It's your Myro. This is the framework. It's open source. You can use it with your team members. It's for you, right? It's for you. Okay, but I'm going to, I'm going to just, I'm going to do a kind of overview of the framework very, very fast because I want to focus on the step number five, right? Well, here you can see the information of the framework. You have some service here. You have some instruction on the framework. You have a part for, you went to Maximize this, sorry. You have some part for different, you know, remember the nine steps that I shared with you? So basically, the framework is there. So you are going to, you can find the nine steps, you know, with some activities for your team, right? Some fun activities to define your team name, you define your rules, get some information about what is gamification, what is the object of the framework, some activities for, well, some foundation about the main pillars of the framework. In this case, I use the link startup methodology to build a framework. That is the idea, right? Try to experiment fast, you know? Start with why, you know, some kind of examples, define the problem that the business needs, and so forth, right? And then put the name of the game. I have another step here. Yeah, here you can have some kind of storytelling part, right? Design some characters of the game in this part, in the section. Yeah, you can design how many characters that you need in your game, basically. And then number five is the canvas. We are going to run the canvas in some minutes, okay? This is the game design canvas. We are going to run it in some minutes, but this is part of the framework as well. I leave you some extra canvas so you can use it with your teams, right? If you want to. So you can design your own game, right? And also you can have here your game rules. You can have some activities so you can define your game rules. Here you can have some examples, some recommendations about it so you can do it with your team. Here is the storytelling part as well, you know? This is a storytelling canvas, so you can use it to create your storytelling for your game, right? These are some examples, some questions that you need to ask your team about it so you can design your story, right? Then you have these, yeah, the characters, right? More detail about it about your main characters, right? Yeah, the heroes, the billions and so forth. And then you have these, the game character canvas, right? As I said, it's a canvas where we have some characteristics of your hero or your game or your player, right? And you need to describe your player, right? Yeah, that is the idea. And then number five, sorry, finally and finally, you can see here the business model canvas, right? Which is, as I said, right? As you know, business model canvas is a kind of a visual way to define what is the business case for your idea, right? For your proposal, for your product and so forth. In this case, I use this canvas to support the business idea, right? Of the game, right? Because at the end, I know that because I, it happened to me, right? That we need to present this idea to our managers more or less, you know, if, of course, if in the case that we need to some budget off, maybe, if we want to apply this game for the entire company, right? That which was my case, right? We create a game of testing game, not only for a team, we create a game for the entire company. I'm talking about more than, more than 1,000 people, right? More than 1,000 and more people, right? So with different countries. So it was very complicated. So this is a kind of a way to support your game, you know, your strategy, right? The business model canvas. And here you can see an example of Pokemon Go, you know, the posits around the canvas in these parts are actually the real posits for the business case, for the business model case of Pokemon Go. So, so you can see here the information here, right? You can play with this, with these canvas to, to define that as well. But this is the idea. This is an example of course, you can have this, this blank canvas so you can apply your, your own approach, right? At the end, at the end, basically, I share with you books, right? That I used for this approach, a lot of books. Actually, every gamification from Yukai Cho, I think this is the most important book in my, in my, in my experience. But of course, there are more, more books that you can, you can check if you want to go deeply in gamification. And basically, I shared, I shared, sorry, I shared those books because of, because those books helped me to design this game, right? Game storming, disrupting you about innovation, innovation games by Luke Hoffman. It's a great book about games in serious business. How your brain works is also another game and some resources right here, some resources, okay? Some links that you can use, okay? That is, that is the framework is, I think it's, it's, you know, I usually, I run this framework with, with people in more or less three hours because it's a kind of, you know, it's, it's, it's a very strong framework. But today with you, right, I'm going to run this real example with you about step number five, which is a gamification design canvas, okay? So we are going to run these, these canvas using the game of testing, right? Just remember, remember that in the game of testing approach, remember that the problem was, okay, we are working in a large enterprise. We need to adapt new ways of working, especially continuous testing or jail testing ways of working, which demands, you know, changes in the behavior, in the culture, in the engineering practices, changes in different team members, right? Product owners, as developers, testers, and so forth. They demands to adapt new ways of working, new, new practices for like testing automation, for unit testing, for integration, and so forth, right? And some BDD practices, some test driving development practices, and so forth, right? A lot of changes, right? If you want to adapt continuous testing or jail testing, that was, that was, that was a business problem, right? In our case, that was the scenario, okay? So basically we designed this and we, I'm going to share with you how we, how we run these, these canvas to face that problem and to design our game, right? Okay, number one, approach number one, is step number one, is team name, right? So your team name, in our case, our team name was, sorry, it was, sorry, was, okay, was the pro, right? That was our name. You can, you can put your name, whatever your name is, right? The Spiderman's or the Magnific Team or the, you know, whatever, right? The code there, the testers and so forth, right? In our case, our team name was the pro. The second step is the problem, right? So you need to define your problem, your why, right? What is the business problem that you want to sort out? You want to fix with this approach, right? This is quite important, the why, right? So in this case, we have a lot of problems. For example, one problem was fake positive in automated test results in the pipeline. So we are, we, actually we coded a lot of, a lot of tests, but unfortunately, those tests gave us fake positive when we ran the test in the pipeline. So we had problems with our tests, actually. So that was part of the game, the problem of the game. Also, another problem was lack of this coverage. Yes, we have a lot of, we have zero percent of this coverage in unit testing, for example, right? This was a huge problem. Another problem that we want to sort out with this game was to, oh, sorry, this is repeated. But basically, well, we have more problems, but basically, those problems were some of them, right? Fake positive while we run automated in the pipeline, you know, and also lack of test coverage, right? Zero percent of test coverage in some regression scenarios, in integration scenarios. So our coverage was ridiculous. So it, well, so it, it caused a lot of, a lot of issues, right? You know, where, you know, where, you know, our products. So that was the situation. Okay. Number three. Okay. Step number three, game name. So in this, in this approach, you can use a kind of brainstorming, right? To try to, okay, guys, let's, let's thinking out in a funny name, right? For, for this game, right? Whatever, right? You know, actually in the market, you have funny names, right? Donkey Kong name. Donkey Kong is a very famous game, right? From Super Nintendo, Super Nintendo thing. And the name is funny, right? Donkey Kong, right? And a lot of name, right? Resident Evil, I don't know. The Legend of Dragons and so forth, right? In our case, we, we share a lot of ideas at that time. And I remember that in that time, the Game of Thrones series was very popular, popular at that time, the Game of Thrones series. So that is why we say, hey, why not Game of Testing? Instead of Game of Thrones, you know, Game of Testing. So the name was nice, was cool. We liked the name. So we decided, okay, the game is going to call Game of Testing, right? Because at the end, we are developers, we are testers. We want to play with a game in some way. We didn't know at that time what the game would be. But we say, hey, Game of Testing is good, right? AK Got. By the way, Adidas, the, the, the, the, the, the sport company from Germany, they had, they also, they also have a, they also have a game similar to this, which is the Game of Technical Depth. It's the same idea, right? Game of Testing, Game of Technical Depth. You know, if you want to see more about it, you can check internet. The game is, is on internet, right? From Adidas. Okay. That's number three. Number four is the objective, right? The objectives. So in our case, in our case, those were our objectives. Game of Testing, Game of Testing aims to build people who is working. That was our first approach, you know, continuous testing. Second goal was Game of Testing looks for make continuous testing fun, you know, that theory of fun. So we can make enjoyable and engageable work, right? That was our approach. And our third approach or objective or purpose of the game was Game of Testing looks for improve software quality through make continuous testing problems in the pipeline. Okay. That though, those were our goals, right? Quality, robust tests, improve the ways of working, people, people have fun and so forth. That was our approach. Number four, you know, that was quite important because those are our drivers, right? The strategy. Number five is game, sorry. It's about the game levels, player levels. Remember that I share with you this, this, sorry, I'm going to share with you very quickly. Yes. In the Game of Testing, we have levels, right? Dragones, which are the best players, the best teams. And we have another levels, right? Depending on the maturity and depending on the points in the game, you have some, some levels, right? The same here, right? We need to define the levels. So, for example, we define three levels. We define the chickens, which basically are the beginners, right? The beginners of the game. They are going to have between zero and one thousand points. We have the lion level, right? Which are the intermediate players, players, which are, which they have between one thousand and six thousand points. And we have that, you know, the masters or the game, right? The dragons. The dragons have advanced level, you know, and they have more than six thousand points. Okay. That was the levels. Of course, we change the levels while we develop new features of the game, while we improve the game, right? Remember that, as I said at the beginning, as part of this framework, we use that link startup methodology, right? So, we apply this kind of round, this kind of approach that is code fast, right? Put it in production, get feedback, experiment, and then code again, right? Depending on the feedback. You apply, we apply this approach, right? Okay. Now, that was number five. Number six is this part, is how you get points and what's for, right? How you get points in a game. As I said, we get points with automated iteration tests. We get points with automated unit tests. We get points with automated iteration tests. We get points finding real bugs, you know, if we run the test in the pipeline and those tests, instead of fake positives, the test real found bugs, the player and the team got some points. And also, we get points keeping our tests in a good shape, right? In a good shape running, reading, running continuously in the pipeline, right? So, of course, depending on the test and the complexity of the code, you get more points than, then you get more points, right? So, for example, unit tests give you some points. And of course, iteration tests give you different points, you know, each type of testing, type of automated tests have different weights for the points, right? And also, you... I guess I'll interrupt time five more minutes. Ah, thank you, thank you. Thank you very much. And finally, well, break builds, right? Also, you missed some points breaking builds. Okay, number seven, very quickly, it's about visualization. It's about how you're going to present your results, right? I share with you an example, but basically, we create this game of testing board web for the game, right? It's a board web. We get some rankings for the players. We get some metrics per release, right? To present in the board rankings and metrics per release. And also, we create this player of the month, right? It's a recognition, right, for the best players. And finally, game surprises, you know, each game needs to be some surprises for team members. So, we prepare some awards for them. For example, tone hold mentions. So, in some meetings with upper managers, the managers present, hey, we are going to... We want to congratulate this team because they are doing great in the game of testing, for example, right? And also, some videos that we upload in the pages of the company. So, you can present your team about the game and we can give you... Thank you for your performance in the game. Tester season, some specific season for some security testing, or some specific testing that people enjoy more. And finally, some special points for rocking players, right? For the players that I share knowledge that they are doing their best. Okay, guys. So, basically, this was an individual canvas and just to finish at the end, right? I hope you can enjoy this talk. Just to finish, I'm going to go here, this part. Yes, my final message that I always use this message is, please remember that everybody have dreams. You have dreams, I have dreams. So, please help and share more. That is quite important. That is why I'm here. Share more, remember that. And thank you very much, guys. Thank you very much for your time. I really appreciate it. Thank you. Yeah, thank you, Arge. It was an excellent session.