Managing Project Scope

1. Product scope is not project scope. A product can have multiple projects.
2. Project Scope: The work that you need to deliver, includes meetings, reports , analysis which becomes project scope management plan.
3. Stakeholder analysis: convert their needs, wants and expectations into requirement.

Work Break Down Structure:- WBS: It breakdown into smaller and more manageable pieces called "Work Packages". This is known as Top-Down Approach.

Granular Scoping

In order to manage a scope , the project budget needs to be defined. 

Accurate Time Capture

Detailed working hours are required to be calculated for entire project

Milestone Reconciliation

Milestone reconciliation is identification of project health with respect to budget. As the budget has already been defined and working hours are calculated, now it can be ascertained if the project is under budget or over budget.

Activity  Definition: Team has to break WBS into smaller manageable pieces called activity. 

Activity Sequencing  Once activities are defined, activity sequencing is the next step.

Activity Dependencies:-  There are 4 types of activity dependencies

1. Finish to start : Preceding activity must finish before successor starts.
2. Finish to Finish: Preceding activity must finish with the successor activity.
3. Start to Start :- Preceding activity must start with successor activity.
4.  Start to Finish:- Preceding activity must start after completion of succeeding activity