Subtitles of the Movie

In this movie, I will provide you with an overview of the Project Scope Management Knowledge Area. In PMBOK Part 2, I emphasis how important of a rule scope plays in project management. A project that doesn't adhere to the project scope is not considered to be successful. The overall purpose of the knowledge area reiterates what I just mentioned which is to ensure that the project includes all the work required and the only the work required to complete the project successfully. There are 5 processes, scope planning, scope definition, create WBS, scope verification and scope control. The Scope Knowledge Area has a very clear process flow; we start by creating the Project Scope Management Plan in the first process. It's this plan which is a subsidiary plan of the project management plan that details how to go about the other processes, especially how to go about developing the detailed project scope statement. Getting this right is of course a critical piece of a project. This was necessary to create the detailed project scope statement in this next process. Once this is done a work breakdown structure can be created. In the create WBS process the major deliverables are decomposed all the way down to the work package level and in the two monitoring and controlling process group processes take over to make sure that the deliverables meet the scope requirements and to control the scope of the project. Let's take a moment to look at a snapshot review of the processes individually. I just mentioned that the Project Scope Management Plan is created in this first process which is scope planning, specifically it documents how the project scope will be defined, verified, controlled and how the WBS will be created. This process creates the guidelines for the rest of the scope processes. Scope definition looks at alternative methods of approaching the project, for example the make or buy decisions, whether contracting an external company to do the work etc Very importantly stakeholder analysis is completed to ensure that all the scope is documented and agreed on and the key result, the Project Scope Statement. Create WBS sets the foundation for the project work, the major deliverables are taken and decomposed down to the work package level. The scope baseline is also an important output, the work within the WBS by the way represents work that has been approved and reflected through the project scope statement. Scope Verification is important because its here that approval and formal acceptance of project deliverables from stakeholders are obtained. To ensure that the deliverable meets the requirements inspection is performed and if it meets the requirements and everything is satisfactory then accepted deliverables are generated as outputs. Scope control is concerned with controlling changes and influencing the factors that create changes to the project scope. It's responsible for making sure that all of these changes have gone through the integrated change control process. Notice all the resulting updates that occur from this process and as a result of the approve change request and that wraps up our overview of the Project Scope Management Knowledge Area. Remember scope is the foundation of the project, it defines what work is to be done and placing the necessary effort into this area will by far prove itself valuable through out the project.