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
Product scope is not Project scope. A Product can have multiple projects
Project Scope: The work that you need to deliver. Includes meetings, reports, analysis which becomes project scope management plan
Scope baseline: Consists of Project scope statement, WBS, WBS Dictionary. If scope baseline is met then project is successful.
Scope Planning: - "How will I do this?" - results into Project Scope Management Plan
Scope management plan should contain - How will scope be planned, executed and controlled
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
Stakeholders Analysis: Convert their needs, wants and expectations into requirements
Product analysis is to analyze objective said by customer and turn them into tangible requirements.
Work Breakdown Structure: WBS: It breaks project into smaller and more manageable pieces called "Work Packages". This is known as Top-Down approach
Work packages are divided further into Scheduled activities.
WBS is hierarchical Chart
Identify the work needs to be performed. If it is not in WBS then it is not in Project
Can be reused to other projects
Does not show dependencies
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
WBS Dictionary provides a description of the work to be done for each WBS work package.
Manager uses this tool to avoid scope creep.
WBS Dictionary contains
A number identifier
Related control account
A statement of the work to be done
Who is responsible
Any schedule mile stones
Interdependencies
WBSD can be uses as the part of work authorization system