Project Management Life Cycle :

- Initiating
- Planning
- Executing
- Monitoring & Controlling
- Closing

Project integration management ensures to connect all the dots of processes in a structured manner irrespective of the
variation in methodologies to successfully complete the project

The main objective of project management is the coordination within all the stakeholders of the project to ensure the
team is working in the right direction to reach the same goal

A stakeholder a person or organisation who is affected by or impacted by what you are trying to do
Stakeholders may also exert influence over the project, its deliverables, and the project team in order to achieve a set of
outcomes that satisfy strategic business objectives or other needs.

Stakeholder participation is intended to improve project:

􀂃 Effectiveness 􀂃 Efficiency 􀂃 Sustainability 􀂃 Transparency 􀂃 Accountability

Purpose of Initiation Process :

1. To commit the organization to a project or phase

2. To set the overall solution direction

3. To define top-level project objectives

4. To secure the necessary approvals and resources

5. Validate alignment with strategic objectives

6. To assign a project manager

Project Charter : A document issued by senior management that provides the project manager with the authority to
apply organizational resources to project activities.

It contains : ◼ Business need ◼ Project objectives ◼ Project deliverables ◼ Assumptions ◼ Constraints ◼ Key staff ◼
Written authorization

Process : a
defined set of avtivities described through a series of steps and further broken down into tasks to bring a desired result .

Types of processes

◼ Project management processes

◼ Product-oriented processes

◼ Business-oriented processes

Organizational process assets are

• The plans, processes, • Policies, procedures, and • Knowledge bases

Knowledge: explicit + implicit

Purpose of Planning Processes:

To develop a project plan that:

◼ Facilitates later accomplishment*

◼ Ensures project wide integration

◼ Monitors change effectively

◼ Provides decision support information to stakeholders

◼ Can be updated by iterative planning activities

Project scope management processes :

1- Plan : creating a plan that documents how the project scope will be defined, validated , controlled.
2- Collect requirements : determining, documenting, and managing stakeholders needs and requirements.
3- Define scope: developing a detailed description of the project and product.
4- Create WBS: Subdividing project deliverables and project work into smaller, more manageable components.
5- Validate scope: formalizing acceptance of the completed project deliverables.
6- Control scope : monitoring the status of the project and product scope and managing changes to the scope
baseline.

Project Scope Statement Purpose :

◼ To provide a general description of the sum of the products and services to be provided by the project

◼ To develop a common understanding of project scope among stakeholders

◼ May make explicit some exclusions that, based on the audience, would be assumed to be part of the project
Work Breakdown Structure (WBS):
- A deliverable oriented grouping of project elements which organizes and defines the total scope of the project.
- Each descending level represents an increasingly detailed definition of a project component.
- Project components may be products or services.
Using the WBS to Estimate Cost:

◼ Project manager establishes work requirements by defining the ◼ What—“shalls” and “wills” ◼ When—sequence ◼
Why—dependencies

◼ Functional managers estimate cost by determining ◼ How—equipment and methods ◼ Who—type and level of
expertise ◼ Where—location, department