In this video, we're going to take a look at sections, four, five, and six of the vision and scope document. So we wrapped up with three dot two In our last video. And now we're going to take a look at the document approval section. So in this section, we're defining who has to approve this vision and scope document. So obviously, our sponsors going to need to do that. And then also, besides the sponsor, we may have some other stakeholders that will need to approve it as well.

Then we usually want somebody from the technology side of the house to also approve it. And in this case, we're saying the TDM which stands for technology Delivery Manager, you may not have a TDM you may have at least developer, you know, it doesn't really matter what the title of the person is, it's that you have somebody from that side of the house that has reviewed this document, and is starting to understand what the project is about. And then we also want somebody from the QA department, so somebody that is going to be involved in doing the testing, it could be the manager of the QA department, it could be a lead QA person, whoever it is that the QA department has deemed needs to be the approval for this project is whose name would go on here. So you have the, you know, the business area, or the group I should say, which can be business area, the technical team, the QA team, and again, there's no right or wrong here.

As far as how many areas are included. You can have more than these areas. This is just some examples that I'm giving you. But you want to know notate who the group is, and then what the name of the stakeholder is for that area. So is it you know, Tom Jones, is it Sally Thompson, whatever their name is. And then the other thing that you want to note here is when did they give their approval for this document.

So most likely, you're not going to get all of the approvals on the same day if you've got a time period where you've told people, okay, now, you know, we need your approval by such and such date, somebody might give it to you on Monday, somebody else might give it to you on Wednesday. So you want to make sure you're documenting the date that people have approved it. The next section that we want to take a look at is change management, change management is really talking about who is it that is actually able to make changes. So we want to list stakeholders that are basically allowed to Submit Changes in the scope for this project. So obviously, your sponsor is going to be able to, they're the one that is really sponsoring this project. And they're the ones that have the biggest stake in this project.

So they certainly can make changes in the scope. But there could be other stakeholders as well, that the sponsor says can make changes to the scope too. So we want those people listed here because we don't want to allow anybody else to make changes. So if somebody else tells you this change is needed, then you would need to say, okay, that's great. I understand that. I need you to get with Sally so that Sally can submit that change for us because Sally has to be the one to approve the changes.

So that way you're managing who can make those changes. To this document, you can't just willy nilly make changes to the scope just based on any person telling you I don't like that, I think this should be that, because they may not understand the reason behind why the sponsor has said something should be a certain way. So we want to make sure that we're controlling who can submit changes in scope. Now, the next thing that we have is section six, which is our quality assurance approvals. So this is defining the name of the persons that will be responsible for signing off on the test results. So this is not the person that is doing the testing of the solution.

But the person that is saying I'm good with these test results, who's going to be responsible for signing off to say, I'm good with what we've got here. So that could be the QA lead. If you have multiple people testing. It could be the QA director, it should also be the sponsor, the sponsor should always be included in any kind of sign offs that have to happen. So we just want to define who has to approve the test results, meaning we found the 50 defects and 47 of those defects have been resolved. And two of the remaining defects are cosmetic, very low priority defects.

One of the defects is a medium level defect, but we have a workaround for it. And so we've determined that we're going to go to production with this known medium level defect that we have a workaround for. We want approvals from our sponsor, so that we make sure that they have an understanding of what exactly we're going to production with related to our QA results. So that wraps up our vision and scope template review. That is the end of our document. That's all of our sections for the vision and scope template.

And if you help to ensure that every section is complete and has concise valid, complete information in each of the sections, then this will help you be successful as the VA for the project and also help the project as a whole stay on task on target and moving towards the plan that is outlined here. So having a plan is critical to the success of the project.