Did you know Cybrary has FREE video training? Join more than 2,500,000 IT and cyber security professionals, students, career changers, and more, growing their careers on Cybrary.
This lesson covers the processes and scope management aspects of Project management. With regard to planning a project, scope entails planning scope management, collection requirements, defining the scope and creating the WBS. Monitoring and controlling entails validating and controlling the scope. The scope management plan is in place to establish rules to managing scope such as the methods used to create the scope statement, creating the WBS, validating project deliverables and addressing scope change requests. [toggle_content title="Transcript"] Welcome to Cybrary. My name is Vincent McKeown. And I am the subject matter experiment for the project management professional course. Today we'll be discussing scope management. Quick background from myself. I was in the Navy for 10 and half years. I have been doing projects for about 15 years now. And I just finished a big project, which lasted four years. And since then I've been working on a whole lot of small projects dealing with audio visual. To go over project management, first we have to understand that there is five process groups, ten knowledge areas, which make up 47 processes. Within the five process groups, there is initiation, planning, executing, monitoring and controlling, and closing. Within the 10 knowledge areas there is integration, scope, time, cost, quality, human resources, communication, risk, procurement, and stakeholder. So if you take the process groups, all five of them, put them on the top and if you take the ten knowledge areas, you come up with a little bit of a matrix. what's in those matrix? There are 47 processes, which if you count them up there should be 47. Today we're going to cover scope. With scope, there are four processes within the planning group and there are two processes with monitoring and controlling. So for scope there is plan scope management. Collect requirements, define scope, and create a WBS. Under monitoring and controlling there is validate scope. And there is control scope. We're first going to talk about plan scope management. Every knowledge area-consists of a plan and how that knowledge area is to be developed. Scope management for this one is the plan and how to develop the scope for the project. So this process creates the scope management plan and the requirements management plan. One thing we'll go over is every process has an input, a set of tools and an output. Why are you doing that process? So the key input to this process is the project management plan which we'll go over that one in integration. There is the project charter which also comes from integration and then from your own company there is a thing called enterprise environmental factors and organizational processes assets. A project manager will use both expert judgement-and meetings to develop the scope management plan and the requirements management plan. So what is the scope management plan? What is the reason for doing this process? Well the scope management plan establishes rules for managing scope such as methods used to create the scope statement. How to create the WBS, how to validate the project deliverables, and how to address the scope change request. Your other output for this process is the requirements management plan. The requirements management plan helps to analyze documents and manages the projects requirements and it may include but doesn't have to, methods used to manage the requirements, methods used to create the requirements, methods used to plan, track and report requirement activities, methods used to perform configuration management activities. Methods used to prioritize requirements, methods used to determine product matrix and usage rationale. How the traceability structure will show what requirements attributes will be under the requirements traceability matrix, and methods used to create the RTM and other project documents which the requirements will be traced. So on this plan you have these four inputs. You have the project management plan. The project management plan is the basis of each knowledge area. So the project management plan is telling me that there's going to be a scope plan. Scope is going to be part of the project management plan. I like to think of the project management plan as a binder, which all the other processes and plans go into. The project charter is what gets the project started. Without a project charter there is no project. What a project charter does is provide the high-level requirements for the project. And for scope, it's basically telling you at a high level what you are going to be doing throughout this project. Enterprise environmental factors- That is the culture of the company. So not every company is the same. The culture of the company is what dictates how is going to be run. Then the organizational process assets I like to think of that as a file cabinet. So these are processes that have been created in the past. Which your company has access to. It could have been a past project, It could have been intelligence, the company could have [board] processes. You could be CMMI. So its whatever your company has and it's providing to you. Those are your organizational process assets. The tools which are going to be used are expert judgement, which is exactly that. You might have someone on the team that has expertise in scope. You may have done scope in the past, you're going to use that expert judgement as a tool for helping develop the scope management plan and the requirements management plan. Also, you may have meetings, which help develop these. I know on every project I've had I've always assembled my project team or even the client to come up with how we are going to develop scope. [/toggle_content]