Unit 1- Introduction to Project Management
Project Definition (Introduction to Project Management)
A project is a temporary endeavor undertaken to create a unique product, service, or result.
Project management involves applying knowledge, skills, tools, and techniques to meet
project requirements.
A project definition clearly outlines the project’s purpose, objectives, scope, and expected
outcomes. It serves as a foundation for planning and execution by ensuring all stakeholders
share a common understanding of what the project aims to achieve, within defined time, cost,
and resource constraints.
In project management, a well-defined project helps:
Clarify goals and deliverables
Control scope and prevent misunderstandings
Improve coordination among stakeholders
Increase the likelihood of project success
Project Life Cycle
The project life cycle represents the series of phases a project goes through from start to
completion. It provides a structured approach to managing work and resources.
Typical phases of the project life cycle:
1. Initiation – Defining the project, its objectives, feasibility, and stakeholders
2. Planning – Developing detailed plans for scope, schedule, cost, quality, risk, and
resources
3. Execution – Carrying out the project work to produce deliverables
4. Monitoring and Controlling – Tracking performance, managing changes, and
ensuring alignment with the plan
5. Closing – Finalizing deliverables, obtaining acceptance, and formally closing the
project
Project Management Processes
Project management processes are activities applied across the project life cycle to manage
the project effectively. According to standard project management frameworks, these
processes are grouped into five process groups:
1. Initiating Processes – Define a new project or phase and obtain authorization
2. Planning Processes – Establish the scope, objectives, and course of action
3. Executing Processes – Complete the work defined in the project management plan
4. Monitoring and Controlling Processes – Measure performance and implement
corrective actions
5. Closing Processes – Finalize all activities and formally close the project
Project Management Knowledge Areas
Knowledge areas represent key aspects of project management expertise that must be
managed throughout the project.
The major project management knowledge areas include:
1. Integration Management – Coordinating all elements of the project
2. Scope Management – Defining and controlling what is included in the project
3. Schedule (Time) Management – Managing timelines and activities
4. Cost Management – Planning and controlling the budget
5. Quality Management – Ensuring deliverables meet required standards
6. Resource Management – Managing human and physical resources
7. Communications Management – Ensuring timely and accurate information flow
8. Risk Management – Identifying and responding to uncertainties
9. Procurement Management – Acquiring goods and services from external sources
10. Stakeholder Management – Identifying and engaging stakeholders effectively
In short
Life cycle = phases of the project
Processes = what managers do to manage the project
Knowledge areas = areas of expertise that must be controlled
Work Breakdown Structure (WBS)
A Work Breakdown Structure (WBS) is a hierarchical decomposition of the total project
scope into smaller, manageable components called work packages. It helps project
managers plan, assign, monitor, and control project work effectively.
Key features of WBS:
Breaks project deliverables into smaller tasks
Improves cost and time estimation
Clarifies responsibilities
Helps control scope and reduce risk
Types of WBS
1. Deliverable-Based WBS
o Organized around project deliverables or outputs
o Focuses on what is to be produced
o Commonly used and recommended
2. Phase-Based WBS
o Structured according to project life cycle phases
o Suitable when work is performed sequentially
3. Process-Based WBS
o Organized by activities or processes
o Focuses on how the work is done
4. Responsibility-Based WBS
o Divides work based on teams, departments, or individuals
o Useful for accountability and resource allocation
Introduction to PMBOK
The PMBOK® Guide (Project Management Body of Knowledge) is a globally recognized
standard published by the Project Management Institute (PMI). It provides guidelines, best
practices, tools, and techniques for effective project management.
Purpose of PMBOK:
Standardizes project management practices
Provides a common language for project managers
Improves project success across industries
PMBOK includes:
Project management process groups
Knowledge areas
Tools and techniques for managing projects
PMBOK is not a rigid methodology; it is a framework that can be adapted to different types
of projects.
Quick Summary
WBS = Breaking work into manageable parts
Types of WBS = Deliverable, phase, process, responsibility based
PMBOK = Standard guide for project management best practices
Portfolio Management
Portfolio Management is the centralized management of one or more portfolios to achieve
strategic organizational objectives. A portfolio is a collection of projects, programs, and
operational work grouped together to maximize value and align with business strategy.
Key Objectives of Portfolio Management
Align projects with organizational strategy
Maximize value and return on investment
Balance risk and resources
Prioritize and authorize projects
Portfolio Management in PMBOK
According to PMBOK, portfolio management focuses on:
Project selection and prioritization
Resource allocation across projects
Performance monitoring at a strategic level
Governance and decision-making
Portfolio management answers the question:
👉 “Are we doing the right projects?”
Traditional vs Modern Project Management (PMBOK Concept)
Aspect Traditional Project Management Modern Project Management
Approach Predictive (Waterfall) Adaptive / Agile / Hybrid
Planning Detailed upfront planning Rolling-wave, iterative planning
Scope Fixed and well-defined Flexible and evolving
Change Handling Changes are costly and restricted Changes are expected and embraced
Customer Involvement Limited Continuous involvement
Delivery Single final delivery Frequent incremental deliveries
Risk Management Addressed mainly during planning Managed continuously
PMBOK Alignment Focus on processes & documentation Focus on value delivery & adaptability
PMBOK Perspective
Traditional approach is suitable for projects with stable requirements (e.g.,
construction, manufacturing).
Modern approach is suitable for projects with uncertain or changing requirements
(e.g., software development, innovation projects).
PMBOK supports predictive, agile, and hybrid approaches depending on project
needs.
Quick Comparison
Traditional → “Follow the plan”
Modern → “Adapt to change”
Portfolio Management → “Choose the right projects”
UNIT I – INTRODUCTION TO PROJECT MANAGEMENT (07
Hours)
1. Project Definition
Meaning of Project
A project is a temporary activity undertaken to create a unique
product, service, or result.
It has a clear beginning and ending, specific objectives, limited
resources, and defined scope.
PMBOK Definition
A project is a temporary endeavor undertaken to create a unique
product, service, or result.
Characteristics of a Project
1. Temporary
o Projects are not ongoing operations.
o They have a defined start and end date.
2. Unique Output
o Every project produces something different.
o Even similar projects differ in context or execution.
3. Progressive Elaboration
o Project details are developed step by step.
4. Defined Objectives
o Specific goals related to cost, time, and quality.
5. Resource Constraints
o Limited budget, manpower, materials, and time.
Examples of Projects
Construction of a highway
Development of a mobile application
Conducting a national election
Setting up a new manufacturing plant
2. Project Life Cycle (PLC)
Definition
The Project Life Cycle refers to the series of phases that a project
passes through from its start to its completion.
Phases of Project Life Cycle
1. Initiation Phase
Identify project need
Feasibility study
Define objectives
Prepare Project Charter
Identify stakeholders
📌 Outcome: Project approval
2. Planning Phase
Scope definition
Schedule planning
Cost estimation
Risk identification
Communication planning
Resource allocation
📌 Outcome: Project Management Plan
3. Execution Phase
Actual work is performed
Team coordination
Procurement of resources
Quality assurance
📌 Outcome: Deliverables created
4. Monitoring and Controlling Phase
Measure performance
Compare actual vs planned
Control scope, cost, and time
Handle change requests
📌 Outcome: Corrective actions
5. Closing Phase
Final product delivery
Customer acceptance
Documentation
Release resources
Lessons learned
📌 Outcome: Formal project closure
3. Project Management Processes
PMBOK groups processes into 5 Process Groups:
Process Group Description
Initiating Defines new project
Planning Develops roadmap
Process Group Description
Executing Performs work
Monitoring & Controlling Tracks progress
Closing Finalizes project
👉 These processes interact throughout the project, not strictly
linear.
4. Knowledge Areas in Project Management
PMBOK defines 10 Knowledge Areas:
1. Integration Management
Coordinates all project elements
Develop project charter
Manage changes
2. Scope Management
Define what is included and excluded
Avoid scope creep
3. Schedule Management
Define activities
Sequence tasks
Estimate duration
4. Cost Management
Budget estimation
Cost control
5. Quality Management
Meet customer expectations
Quality planning and control
6. Resource Management
Human resources
Physical resources
7. Communication Management
Information distribution
Stakeholder communication
8. Risk Management
Identify risks
Analyze risks
Mitigate threats
9. Procurement Management
Vendor selection
Contract management
10. Stakeholder Management
Identify stakeholders
Manage expectations
5. Work Breakdown Structure (WBS)
Definition
A Work Breakdown Structure is a hierarchical decomposition of
the project work into smaller, manageable components.
Objectives of WBS
Break complex work into smaller tasks
Assign responsibility
Improve estimation accuracy
Reduce risk
Characteristics of WBS
Deliverable oriented
Follows 100% rule
Structured hierarchically
No overlapping tasks
6. Types of WBS
1. Deliverable-Based WBS
Organized around outputs
Most commonly used
2. Phase-Based WBS
Based on life-cycle phases
3. Functional WBS
Organized by departments
4. Process-Based WBS
Based on workflows
7. Introduction to PMBOK
What is PMBOK?
PMBOK is a standard framework developed by the Project
Management Institute (PMI).
Objectives of PMBOK
Provide standardized guidelines
Improve project success rate
Define best practices
PMBOK Structure
5 Process Groups
10 Knowledge Areas
ITTOs (Inputs, Tools & Techniques, Outputs)
8. Portfolio Management
Definition
Portfolio management involves selecting and managing projects and
programs to achieve strategic business objectives.
Features of Portfolio Management
Focus on value maximization
Strategic alignment
Risk balancing
Project vs Program vs Portfolio
Aspect Project Program Portfolio
Focus Deliverable Benefits Strategy
Dependency Independent Interdependent May or may not
Level Operational Tactical Strategic
9. Traditional vs Modern Project Management (PMBOK)
Traditional Project Management
Sequential (Waterfall)
Detailed upfront planning
Change is discouraged
Heavy documentation
📌 Examples: Construction, manufacturing
Modern Project Management
Agile / Hybrid approach
Adaptive planning
Change is welcomed
Continuous customer feedback
📌 Examples: Software, IT projects
Comparison Table
Aspect Traditional Modern
Flexibility Low High
Risk handling Late Early
Customer involvement Limited Continuous
Speed Slow Fast
Conclusion
Project Management using PMBOK ensures structured planning,
efficient execution, controlled risks, and successful delivery of
projects aligned with organizational goals.