Aditya Chinni, PMP

Project Management made easy!!
Home     PM Books Store     PMP Tutorial     Articles     Tell a Friend     Enroll - PMP Training     Contact Aditya     Newsletter signup     PMP Checklists      
Framework (Fundamentals)
Process groups, Knowledge Areas
Integration Management
Project Scope Management
Project Time Management
Project Cost Management
Project Quality Management
Project Human Resource Management
Project Communications Management
Project Risk Management
Project Procurement Management
Scope management
(Based on PMBOK 3rd Edition. For PMP Certification Exam preparation)
 
 

 InitiationPlanningExecutionMonitoring &
Control		Closing

 

Scope Planning

Scope Definition

Create WBS

Scope Verification
Scope Control
ment
  1. Scope Management is the process of defining what work is to be done and making sure only that work is done nothing extra (Gold Plating) is done
  2. Product scope is not Project scope. A Product can have multiple projects
  3. Project Scope: The work that you need to deliver. Includes meetings, reports, analysis which becomes project scope management plan
  4. Scope baseline: Consists of Project scope statement, WBS, WBS Dictionary. If scope baseline is met then project is successful.
  5. Scope Planning: - "How will I do this?" - results into Project Scope Management Plan
  6. Scope management plan should contain - How will scope be planned, executed and controlled
  7. Scope Definition: Take Preliminary scope statement from initiation process group and develop full blown scope statement. Includes all the needs to stakeholders, constraints and assumption - results into Project Scope Statement
  8. Stakeholders Analysis: Convert their needs, wants and expectations into requirements
  9. Product analysis is to analyze objective said by customer and turn them into tangible requirements.
  10. Work Breakdown Structure: WBS: It breaks project into smaller and more manageable pieces called "Work Packages". This is known as Top-Down approach
  11. Work packages are divided further into Scheduled activities.
    1. WBS is hierarchical Chart
    2.  
      Identify the work needs to be performed. If it is not in WBS then it is not in Project
    3. Can be reused to other projects
    4. Does not show dependencies
  12. Control Account: While calculating costs, we don't and can't calculate up to work package level. A level above the work package is known as Control Account
  13. WBS Dictionary provides a description of the work to be done for each WBS work package.
  14. Manager uses this tool to avoid scope creep.
  15. WBS Dictionary contains
    1. A number identifier
    2. Related control account
    3. A statement of the work to be done
    4. Who is responsible
    5. Any schedule mile stones
    6. Interdependencies
  16. WBSD can be uses as the part of work authorization system