Hello my name is Aditya Chinni from CertSchool**** where we prepare students for PMP Certification exam. I...
Hello my name is Aditya Chinni from CertSchool**** where we prepare students for PMP Certification exam. In this video I’d like to cover Scope Management knowledge area.
Scope is one of triple constraints along with time and cost. Even though there are multiple project constraints these 3 constraints are crucial for the project. Many authors included Quality, Risk and Customer satisfaction are also part of triple constraints. I’d say those all are key constraints and Scope, Time, Cost are triple constraints.
Scope defines the work for our project. That means what is in and what is out of our responsibilities. In generic terms we use requirements and scope as interchangeable words. But for me those two are sequential. Customers might be asking for many requirements but as a project manager we will derive project scope and stick to it. The scope that we agreed up on is called as Scope Baseline. According to PMI Scope line includes 3 items which I will cover in a minute.
When we are talking about Project Scope we need to understand 3 terms.
- Product Scope
- Scope creep and
- Gold Plating
Product scope is characteristics of the product. Project can be delivering the product in a whole or a sub set of that product. In case the project is delivering the subset of the product or upgrading the product project scope will be subset of the product scope.
Uncontrolled product changes are known as scope creep. In literal terms when we add more scope we are worried and call it as a scope creep.
Providing out of scope items for FREE is known as Gold Plating. There might be a chance that additional items are not welcome too.
Scope knowledge area has 5 processes
- Collecting requirements
- Define Scope
- Create WBS which is work break down structure
- Verify Scope
- Control Scope
Collecting Requirements process helps project managers to define and document project requirements. And as I already mentioned this is preliminary step where we collect RAW requirements
The next process Define Scope refines already collected requirements into a Project Scope statement. Scope can be bigger and complicated document for a larger project and it is very hard to control or manage as a whole.
The 3rd process Create WBS helps project managers to break down the refined scope in to smaller manageable components. The smaller components are known as work packages. These work packages are organized into a hierarchical structure which is known as Work Breakdown Structure and in short WBS. Scope baseline is part of outputs of this Create WBS process. As I Promised Scope Baseline have 3 components in it and those are Scope statement, WBS and WBS dictionary. Just like our English language dictionary WBS dictionary explains details about WBS components. Remember bottom most part of Work breakdown structure are called as “Work Packages”. Underline the term packages. Which will useful when we talk about Time management process Develop activity list
All of these 3 processes are in planning group. Once project is started execution we have to manage day to day project activities which include scope management activities too. Scope Management activities include controlling unnecessary scope changes. For these activities we have 5th process “Control Scope”
The 4th process which we skipped just now is Verify Scope formalizes the deliverables acceptance.
For each one of these 5 processes I’d suggest you to explore inputs, tools & Techniques and outputs. PMBOK guide has published Data flow diagrams in which it is clearly define process interactions. Please go through those data flow diagrams and understand those details.
In my PMP Prep classes we cover those details in depth. For more details about my class please log on to my website www.certschool****