Scope management

It is about doing the right stuff

It is about set the team goals and keep everybody on track

Product scope; it is about the product features and functions that you and your team are building

Project scope; it is about the work that need to be done to build your product, it is what the PM concerned with

Scope creep; uncontrolled changes that cause the team to do extra work

The project scope include every single thing that made by you and the team and that includes the project plan and other project management documents

There are a plenty of things that are deliverables but the end user will not even see it like project schedule, specifications, blueprints and budget, although some of them you made as PM and some aren't you have made, your job only to ensure they got done

Your job as PM to worry about the work the team does to build the product, and your team job is to worry about actually building it - but that doesn't mean you can't get their cooperation to write down all the work needed to build the product

It is not your job as PM to decide which feature is the best for the product, it just to help everybody involved to keep their priorities in mind and do what is best for the project

You always have to know what the work to be done to build your product before starting your project

The scope management plan; describes how will you write down the scope, ensure it is right and keep it up to date

The scope management plan is the solution of the following problems

1. The team had trouble getting the project off the ground
   
   
2. There were a lot of false starts
   
   
3. The sponsors and stakeholders are unpredictable
   
   
4. There were a whole lot of changes
   

The 5 scope management processes; each process in the scope management processes is designed to help to avoid the scope problems that may get your project off-track

1. Collect requirements;
   It is the process of defining and documenting stakeholders needs to meet the project objectives
   
   
2. Define scope;
   
   Is the process of develop detailed description of the project and product
   
   The project scope statement is built upon the major deliverables, assumptions and constraints that are documented during the initiation process
   
   Existing risk, constraints and assumptions are analyzed for completeness
   
   Additional risk, constrains and assumptions are added
   
   
   When you do this right your stakeholders will never be unpredictable because you already understand their needs
   
   

   

   
   

   
   

3. Create WBS process;
   
   It is about organizing the team work into work packages or discrete pieces of work
   
   By doing this you will keep the momentum of the project form the start
   
   

   

   
   

   
   

4. Control scope;
   
   The scope changes must controlled using the integrated change control
   
   The most frustrating problems comes as a result to uncontrolled changes
   
   

   

   
   

   
   

5. Verify scope;
   
   It is about comparing what you have done against what you had been written down in the scope statement