In our last video, we looked at section two to scope of initial and subsequent releases. In this video, we're going to take a look at our next section, which is to dot three, and that is limitations and exclusions. So this is where the stakeholder helps define what they don't want included as part of this project. So let's take a look at what we have here as a limitation and an exclusion. So we have limitation one, the scope of this project does not go beyond the regional sites. Now, when we're talking about requirements, we always try to make it a point to not go with something that is a negative.

So when it comes to requirements, we don't want to say what something is not. We want to say what it is, but in the case where you're talking about limitations In exclusions, it's okay to define what something is not. So saying the scope of this project does not go beyond the regional sites is okay. The other way you could put this if you were trying to only look at it from the positive side, rather than the negative side would be to say, the scope of this project includes regional sites, period. But when you're talking about limitations, and exclusions, that almost makes you feel like you should be hearing something that it's not. So if somebody reads the statement, the scope of this project encompasses the regional sites they may be waiting for.

Well, okay, but what doesn't it encompass because this section is about limitations and exclusions. So it's really kind of inviting you to go with the negative rather than just looking at it from the positive. So I feel like In this area, saying that it does not go beyond the regional sites is actually a more correct way of stating what this is related to. Next we have exclusion one, any updates to the corporate site will need to be addressed at a later date as a separate project. So what we're saying here is that the corporate site is completely excluded, not just from release one, but from this project at all. Like it's never going to be released one release to release three.

It is not part of this project, they would need to start a new project for changes that they may want to make to the corporate site. This project is only about the regional sites that our customers and potential customers access. It's not about our corporate website. So this lists out Anything that we're not going to do as part of this project. So when I say anything, I don't literally mean anything. Like, you're not going to list out things here, like, Hey, we're not updating the HR site, or we're not updating payroll, you know, obviously, those things aren't included.

This project isn't about anything related to those things. So all you want to include here in your limitations, and exclusions are things that might be assumed could possibly be part of this project, and you want to spell out that they are not. So it's not a matter of dumping everything in here that could be anything related that the company might update. That's not the point of this section. It's the only limitations and exclusions, exclusions related to this particular project and what it's about