Project Management

Lecture 5+6MS Saba Sahar

Outline

• PMI: PROCESS GROUPS and Knowledge Areas• SOW• Project Charter

3

PMBOK

• Structures PM by – A) Processes– B) Knowledge Areas

• Processes. 2 types– 1. Project oriented processes: describing and organizing

the work of the project– 2. Product-oriented processes: specifying and building the

project’s product

PMI: PROCESS GROUPS & KNOWLEDGE AREAS

• PMI is incorporated in 1969, was founded by five volunteers, with its headquarters in Newtown Square, to project management, manages several levels of project management certification and published a number of standards related

• The levels of certification are:• Certified Associate in Project Management

(CAPM)• Project Management Professional (PMP). • PMI manages one certification level related to

program management, namely, Program Management Professional (PgMP).

The Project Management Institute (PMI)

PMI Process Groups & Knowledge Areas

• Process Groups– When project management process are grouped

logically they from process groups• Knowledge Areas– When the project management process are grouped

by area of specialization, they form knowledge areas.• The knowledge areas described what the project

manager needs to know and process group define what the project manager needs to do.

Process groups

• Project management processes fall into five groups:– Initiating Process Group– Planning Process Group– Executing Process Group– Monitoring & Controlling Process Group– Closing Process Group

Knowledge Areas

• Project management knowledge draws on nine areas:– Project 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

10

PMI Framework

Source: Project Management Institute

11

The 5 PMI Process Groups

• 1. Initiating• 2. Planning• 3. Executing• 4. Controlling• 5. Closing• Note: these can be repeated for each phase

• Each process is described by:• Inputs• Tools & Techniques• Outputs

12

PMI Process Groups

Source: Project Management Institute

13

PMI: Process Links

14

PMI: Initiating Process

• Knowledge of Scope management.– Initiating

• Inputs– SOW• Product Description • Project Selection Criteria• Historical Information

• Outputs– Project charter– Project Manager assigned– Constraints– Assumptions

15

• Scope Planning• Scope Definition• Activity Definition• Activity Sequencing• Activity Duration

Estimating• Resource Planning• Cost Estimating• Cost Budgeting

• Risk Planning• Schedule Development• Quality Planning• Communications Planning• Organization Planning• Staff Acquisition• Procurement Planning• Project Plan Development

Devising and maintaining a workable scheme to accomplish the business need that the project was undertaken to address

PMI: Planning Process

16

PMI: Executing Process

• Project Plan Execution

• Scope Verification• Quality Assurance• Team Development

• Information Distribution

• Solicitation• Source Selection• Contract

Administration

Coordinating people and other resources to carry out the plan

17

PMI: Controlling Process

• Overall Change Control

• Scope Change Control

• Schedule Control• Cost Control• Quality Control

• Performance Reporting

• Risk Response Control

Ensuring that project objectives are met by monitoring and measuring progress and taking corrective measures when necessary

18

PMI: Closing Process

• Administrative Closure

• Contract Close-out

Formalizing acceptance of the project or phase and bringing it to an orderly end

19

Statement of Work (SOW)

• A description of the work required for the project• Sets the “boundary conditions”• SOW is description of product or service to be

supplied by a project. • For internal projects, the project initiator or sponsor

be supplied by the project.• For External Projects, the SOW can be received from

customers as a part of bid document:– For example, Request for Proposal, Request for

Information,, Request for bid, or as a part of a contract.

SOW

• SOW Indicates as:– Business Need

• The organization business need can be based on needed training, market demand, legal requirements or government standards

– Product Scope Description• Document the product requirements and characteristics

for the product or service that the project will be undertaken to create.

– Strategic Plan• All project should support organization strategic goals.

21

SOW TemplateI. Scope of Work: Describe the work to be done to detail. Specify the hardware and

software involved and the exact nature of the work.

II. Location of Work: Describe where the work must be performed. Specify the location of hardware and software and where the people must perform the work

III. Period of Performance: Specify when the work is expected to start and end, working hours, number of hours that can be billed per week, where the work must be performed, and related schedule information. Optional “Compensation” section.

IV. Deliverables Schedule: List specific deliverables, describe them in detail, and specify when they are due.

V. Applicable Standards: Specify any company or industry-specific standards that are relevant to performing the work. Often an Assumptions section as well.

VI. Acceptance Criteria: Describe how the buyer organization will determine if the work is acceptable.

VII. Special Requirements: Specify any special requirements such as hardware or software certifications, minimum degree or experience level of personnel, travel requirements, documentation, testing, support, and so on.

Project Charter

• A Project Charter is a document that formally authorize the project.

• It outlines the purpose of the project, the way the project will be structured and how it will be successfully implemented.

23

Project Charter

• A high-level project description:– Business need, product, assumptions

• Often precedes SOW• Often 2-4 pages (can be longer)• The Project Charter is also known as a "Terms

of Reference" or "Project Definition Report".

Project Charter• Companies who apply formal project only create a project charter. The project

charter will include:• Typical outline

- The project goal, and objectives - The major milestones and the deliverables - The project scope - The project success criteria - The potential risks/issues - The stakeholders: who are they and how influential is each one of them (this part should consists of a stakeholder analysis) - The estimated cost of the project - The estimated duration of the project - A description of how changes will be processed and approved - A description of how communication will work in the project - The names and the roles of the resources who are going to work on the project

25

Project Charter

• Typical outline– Overview• Business need• Objectives• Method or approach

– General scope of work– Rough schedule & budget– Roles & responsibilities– Assumptions

Reference Material

• A Guide to the Project Management Body of Knowledge, Third Edition (PMBOK Guides), ISBN-13: 978-1930699458