In this lesson, we're going to go over the different roles that are in safe and the team sizes. So what I've tried to do is basically on the left hand side is the different levels that we haven't saved the four different levels that we talked about earlier as well, teen program value stream and portfolio. Here we have the team sizes that basically each of these levels have. And then here in the middle, we have the different roll heights that are at the different levels of safe if you will. Now, notice also that I have color coded them so that the green color for example, is it related. All these green color roles are related each other at the different levels if you go the gray is related to the, to each other at different levels, if you will, it's kind of the equivalent of of that role at that particular level.

Okay. So, with that again, the left hand side is a different levels of safe portfolio value stream program team, we have talked about this before, on the right hand side is the approximate team size to be at different levels. And then in the middle is the different roles and the color coding basically safe and you know, shows the relation So, a scrum master is at a team level at a program level. A similar role is a release train engineer or archy. Okay, so with that premise, let's kind of go through each of these roles if you Oh, team level role in save is basically the same thing that we have talked about in Scrum. If you remember the three main roles that were in Scrum is the product owner scrum master and the development team.

And so those are the roles that are at the team level. The size, that safe basically recommends for our team levels is from five to 49 people. So that's kind of you know, the same thing that we have talked about during Scrum. If the team says get more to be more than nine people then the starts doing Scrum of scrums, etc, so that we don't have a huge scrum team, if you will. That with the team size based on safe if it goes beyond 49 from 50 people to 125 people that's a program level and then if it goes beyond 145, then it is at a value value stream level and we're going to see how you know the organization in safe helps with the you know, keeping so many different people alive. And keeping the visibility over the number of members of people.

So, so, again a team level we have delta product owners Scrum Master and development team at a program level instead of a product owner we have a program manager. So, what a program manager does is kind of similar to a product owner role, but he or she is is coordinating the multiple different teams now. So, it is a much larger role. The program manager works with the product owners of the different teams if you will, in order to keep that product ownership, coordinated, release train engineer RP works with the different Scrum Master of the different teams under a program. A system architect is a new role which is not defined at the team level. This is so that It's an overall architect role that is making sure that the design is is is kept in sync between the different teams if you will.

So it's it's a collaboration architectural collaboration role that is defined at a program level which is called system architect. And then you have a new role another new role called a business owner, again a business owner is a is a role that works with the program management team or the product owners if you are the program manager just he or she is this me to provide any directions to the program manager if you will, for the for the product. System team, again is at a at a program level, they have similar cast as the development team they are used for, like integrating the products that the development that different teams kind of produce, that's kind of their role. So they are kind of The integrators they're making sure that you know, everything kind of works together. And that's the role of the system team. If the team gets above 125 resources, then we have a value stream level if your solution manager role is a role that basically works with the multiple different program managers, again value stream has more than one program under it.

So, the solution manager is working is coordinating the different program managers, a value stream engineer is coordinating the different release train engineers which in turn are coordinating the different Scrum masters under them. And then last role here and the value stream level as a solution architect level role, which is basically coordinating the different system architects to make sure that the overall architecture remains intact. And then the final role that we have is is a portfolio role portfolio again is it has all the different value streams of programs under underneath it. What you have here is an epic owner, which is making sure that the that the coordination between the solution managers is intact. They're making sure that the epics that were defined in the original portfolio or the strategy for the organization are are in line which with the with the breakdown of those epics at these different levels, if you will.

So, the epic owner is coordinating with the different solutions managers. And then you have a program portfolio manager, who is whose role is to basically coordinate with the different value stream engineers or if you don't have a value stream, you have just a program then they this person coordinates with the different RTS or the different release train engineers. And then you have an Enterprise Architect that is making sure that That the architecture the design of, of the overall solutions, because there are multiple different programs, multiple different value streams are kept intact with, you know, the overall policy or the overall market architecture that is supposed to be based on on the different organization. It's kept intact with the overall architecture for the organization or the planned architecture for the organization. And that's kind of the role of the Enterprise Architect. So, these are the different roles that are in safe at the different levels.

And this, these are the different team sizes. Now, if you do not have, if the team size is just, you know, 49 or less than basically it's just going to be a scrum project, if you will. Again, if the program level if the team size is 50 to 145 then it's At a program level and and if you don't have for example, if the if the team size is you know 50 to 145, you will not have a value stream level. So this portfolio level will directly interact with the program level, if you will. So that's kind of little bit about the team size, the different roles and the different levels that we have inside. The other piece of it is basically the what is called art or agile release train.

Basically, what you have is at a program level, you have all the resources that are part of the program. Again, remember that people that are part of a program are not only the people and the program level, but also they are part of it. They are part of the team so they have program resources and the team resources the count needs to be handled. Five or less, though all those people are part of what is called an agile release train. So that's kind of where the the word art comes from. And we'll see at a value stream level you actually have since you have multiple programs underneath it, you will have multiple artists are multiple agile release trains.

As you can see from here, as I just mentioned, we have the program level. So you just have one agile release train. So all the people the hundred and 25 or less people are sitting on this one agile release train two are coordinated based on the different roles that we talked about. And then if you have a value stream, you have multiple agile release, train one for each program, if you will. So that's kind of at a high level, what the roles are sizes and what are our agile release trains me will be learning more about these iterations etc In the next lesson.