Now that we have gone through the portfolio structure in one of the previous lessons, we're going to look at the safe structure safe again stands for scaled agile framework, and we're going to get more into this methodology. So, why do we need need the scaled agile framework? Well, so, to understand that let's kind of you know, we talked about the portfolio the understand that you know, some of the complexities as you may have imagined from one of the previous lessons that a portfolio has multiple products and a product can have multiple releases and the release has multiple sprints and sprint has, you know, daily scrums, etc. So, this kind of pictorial kind of gives you a sense of that one once again. So portfolio products releases Sprint's with initially is and then the daily scrums. So if you remember this portion is really what the scrum is about what we have been talking about within the scrum that you have the sprints and the Sprint's make up a release and each sprint has multiple, or has a daily Scrum every day.

So that's kind of what the scrum is about. How do you deal with this whole thing, though, because again, this is, you know, in bigger companies or in different companies, you don't have a single product that you're working on single release, you have multiple projects you're working on. So if you're dealing with it the agile way, how do you work, what kind of process what kind of framework that you need to apply and that's where I save comes in. The issue is basically the coordination. So that relief example, we had the combination between the different product teams, if you will, and then vertically we have the issue between the coordination between the portfolio and then the product teams working on different releases. So those are the two coordination challenges that we have absolute addresses in see if this level so release down is basically if you have a project that basically requires this one release and then you know you're working with multiple sprints, etc.

That's a key that's called a team level if you go in say, the next level in safe is the programmer and value stream level these are different value stream programs at the front end, we learn about it as we go through future lessons value stream basically you can think about it is a bigger program. And and a program is just a single program if you will, so so you have the smallest level in safe as well. As the group or the resource group is concerned is the team level that basically deals with the release down. The next level is at the product level, which is the value stream and or program. And then the final final level in safe is basically portfolio. So those are the four levels in safe portfolio.

Next is value stream. Next is program. And then the final one is a team team as a smallest level in say, if you think about Scrum, we have been dealing with it at a team level because that's, you know, you're dealing with a release and multiple specs within a release, etc. So that's kind of a team that will, what you're adding to it is basically the program then stream at the portfolio level, let's say, and we'll see in the in the next few slides in the next few lessons, that how safe helps the coordination laterally and vertically as well. So here's kind of another pictorial representation. Have those four hierarchy levels that I mentioned in the previous slide, you have the team level.

Then the next is the program level. Above that is the value stream level and finally, the portfolio level. So those are the different levels in in safe and we'll learn as we go through these lessons there. What is the difference? What's the difference between these levels of evil as we saw in the previous slide, the team level is basically the leaves down the program and value stream level are at a product level if you will, and then the finally the portfolio level as that is at a portfolio level. And from the previous lesson, we went through you know, what the what exactly worked for us, which is exactly what is represented here, that portfolio has multiple products in it and each product has multiple releases, etc.

So, this slide shows an example of what we have kind of gone through, you know, in some of the previous case, you have the portfolio level you Have the value stream program. And then the team level, these are the four levels that we're talking about. So you may have multiple value streams. So in this case, I'm just showing one example that you may have, for example, taking a Boeing example, the value stream, maybe Boeing 747 100 series, if you will, and then the program, maybe kind of the engine of this plane, the conflict of this plane, the fuselage of this plane, maybe is at a program level, and then, you know, each engine can be, you know, may have its own components that different teams are dealing with, to add a team level, if you will, so, that has kind of the multiple releases, if you will, so, that's kind of just giving you an example regarding what we have talked about before, hopefully this this is helpful to kind of explain the the structure of safe if you will, we started from portfolio we saw that you know what, what are the different things within portfolio, you have multiple products, multiple releases, multiple sprints within a release, and then you know, each sprint has multiple scrums going on.

And then we saw the challenges laterally and vertically that you have in, you know, in in a portfolio, you know, kind of coordinating between products and also coordinating from portfolio down between the different teams. And we'll see. So this slide basically shows an example of that. And then we'll see in future lessons, how does save help coordinate all that together. If you