Professional Documents
Culture Documents
Lecture No 1
BITS Pilani Sunil Soni
Visiting faculty
Pilani|Dubai|Goa|Hyderabad
1
Ground Rules
Text Books:
– Clifford F Grey. Erik W Larson, Gautam V Desai, “ Project
Management: The Managerial Process” Mc Graw Hill Education
(India) Private Limited, New Delhi, Sixth Edition, 2014.
– Jerome D Wiest, Ferdinand K Levy, “ A Management Guide to
PERT/CPM with GERT/PDM/DCPM, PHI Learning Private
Limited, Second Edition, 2009.
Reference Books:
– Kerzner Harold, “ Project Management: A Systems Approach to
Planning, Scheduling and Controlling”, Wiley Student Edition,
Tenth Edition, 2013.
– Kamaraju Ramakrishna, Essentials of Project Management”, PHI
Learning Private Limited, First Edition, 2012.
– Garold D Obriender, “ Project Management for Engineering and
Construction”, Mc Graw Hill Education, Second Edition, 2014.
• Scenario I:
– You are building your house and have entrusted the
work to a building contractor
• Scenario II:
– You are getting software developed by a software
house ( development company).
Building SW Project
• Designs - Yes • Designs - Yes
• Project Management? • Project Management?
• Architectural challenges • Technical challenges
• Conflict resolution • Conflict resolution
That is what I did not • No agreement on the Project’s Scope • Project Planning
ask • Limited Requirement, Design and Project • Change Management
documentation
• Failure to incorporate Changes
You spent too much • Changing Requirements increased Scope • Cost Management
and Cost to complete • Change Management
money
• No project budget
• Costs were not tracked
This does not work • No agreement on the Project’s Scope • Project Planning
• Limited Design and Project Documentation • Change Management
• Failure to incorporate Changes • Quality Management
• No Quality Management Plan
• Unclear priorities
• Poor communication
• Issue resolution takes too long
• Inconsistent project reporting
• Always reinventing the wheel
• No clear objectives & lack of Executive
support
BITS Pilani, Deemed to be University under Section 3 of UGC Act, 1956
Learning Objectives
• Understand the growing need for better project
management.
• Explain what a project is and provide examples of projects
• Describe what project management is and discuss key
elements of the project management framework
• Discuss how project management relates to other
disciplines
• Understand the history of project management
• Describe the project management profession
Complex II I
Very
Complex
Technically
Challenging
Technical Easy Client
Environment Environment
Routine Technical
Environment
Simple or
Difficult Client
Routine
Environment
Simple IV III
Projects Operations
Projects are temporary and unique Operations are ongoing and repetitive
The Purpose of a project is only to The main objectives of operations is to
attain its objectives; the project is sustain the business
terminated once objectives have been
achieved Implementation of
projects intersects with
Common Characteristics Projects and Operations operations at various
• Both are Performed by People points in a product ‘s
• Both are Planned, Executed, and Controlled. life cycle.
• Both have Limited Resources
People
Projects Executed Operations
Controlled
Projects Operations
• Create own charter, • Semi-permanent charter,
organization, and goals
organization, and goals • Maintains status quo
• Catalyst for change • Standard product or service
• Unique product or • Homogeneous teams
service • Ongoing
• Heterogeneous teams
• Start and end date
Risk Risk
Customer Business
Expectation Objective
The Project team must understand the ‘triple constraint’ relationship between
Scope, Schedule and Resources how it affects Quality and Risks .
What is Project Management?
When and
How Long
What Who
How
Why
When Projects are delivered
correctly they can…..
• Expand Product Portfolios
– Faster product to market cycle
• Improve Customer Satisfaction
– Build to customer requirements
• Reduce Production and Operating
Costs
– Modernize and automate processes
• Increase Revenue
– Reduce invoicing periods
• Accurately Report Progress
– Delivery dates
– Costs
34
36
History of Project Management
• Some people argue that building the Egyptian Pyramids was a
project, as was building the Great Wall of China.
• In the United States, the forefather of project management is
Henry Gantt who is famously known for his use of the "Gantt"
chart as a project management tool in 19th century beginning
• Most people consider the Manhattan Project to be the first
project to use “modern” project management
– This three-year, $2 billion (in 1946 dollars) project had a separate
project manager and a technical manager
– Most successful project
• In 1969, the Project Management Institute (PMI) was formed
to serve the interest of the project management industry
• Taj Mahal, Indian Railways, India atom bomb are example of
Project Management
• Development of Agile Project Management
Projects Cannot Be Run in Isolation
• Technical Dimension
– The science of project management
– This technical dimension includes
planning, scheduling, and
controlling projects.
• Socio-Cultural Dimension
– The art of managing project
– the manager must build a
cooperative social network among a
divergent set of allies with different
standards, commitments, and
perspectives.
50
Project Phases and the Project Life Cycle
• Project Life Cycle defines the beginning and end of projects and the
various milestones associated with in it.
• A Project Life Cycle is a collection of project phases that defines:
– What work will be performed in each phase.
– What deliverables will be produced and when.
– Who is involved in each phase.
– How management will control and approve work produced in each phase.
• Project phases vary by project or industry, but some general phases
include
– Concept
– Development
– Implementation
– Support
• A deliverable is a product or service produced or provided as part of a
project.
Project
Construction Industry
Pharmaceuticals Projects
Project Lifecycle in Various Industries….
Project
Definition Phase
Relationship between Project
Phases
• Sequential Relationship
• Waterfall Model top to bottom Design Construction
• e.g Coding leads to Testing
• Overlapping
• Subsequent phase starts even Requirement Gathering
before implementation of its
immediately preceding phase
• e.g Requirement Gathering
and Design can overlap Designing
• Iterative
• Phase implementation is Listen to Gather Needs
planned once, but if required Customer
the phase is executed again.
• e.g. Requirement Gathering SRS
Documentation
5. Requirements
Project Life Cycle
Testers
PMs
Programmers
Graphic Designer
59
Objectives Outputs
Gather sufficient information to assess Feasibility Study
opportunity Approved Project Charter
Clarify and define the sponsor’s Define Project Categorization
business need Perform Compliance check as per
Understand the problem to be solved org policies
Identify desired approach to solve
the problem
Purpose
Further define the business requirements and objectives. The resulting work in this phase
feeds the proposal development process and a high-level project plan.
Objectives Outputs
Identify project objective Project Initiation Session
Begin to define the business Resource & duration estimates
requirements and major deliverables Schedule for planning phase
Develop high-level estimates of High-level Work Breakdown
project scope, schedule and Structure (WBS)
resources 1st draft Project Plan Document
Provide input to the proposal and Establish Status Reporting Procedure
deal review processes Validated Quality Requirement
Perform PM Compliance check
Purpose
Project planning is of major importance to a project. Detailed project planning
establishes the plan, , processes, controls and tools which will be utilized to monitor
& control project work, quality & performance during Execution Phase.
Objectives Outputs
Core Processes
Scope Sequencing
Planning Activity
Activity Schedule
Definition Development
Activity
Duration Cost
Scope Estimating
Definition Budgeting
Resource
Planning
Cost
Estimating Project Plan
From the Development
Initiating To the
Processes Executing
Processes
Facilitating Processes
From the
Controlling
Processes
Quality Communications Risk Risk Risk Response
Planning Planning Identification Quantification Development
Objectives Outputs
Updated project schedule
Fulfill contract deliverables Updated cost tracking worksheet
successfully Approved Change Requests and
Monitor and control change Updated Change Log
Monitor and control contract / project Status/Performance Reporting, Metrics &
delivery, meeting project objectives Variance Reporting, Meeting Minutes
agreed upon by customer – Updated RAID Plans
requirements met on-time, on-budget Project Quality Reviews
Communicate progress and issues Project communications calendar
to project stakeholders Shutdown Schedule
Customer Acceptance Sign-off on
Completed Project Deliverables
Overview of Executing Process
Executing Processes
Project Plan
Execution
Facilitating Processes
Quality
Assurance
From the To the
Planning Informatio Team Controlling
Processes Distribution Development Processes
Scope
n
Verification
Source
Solicitation
Selection
Contract
From the Administration
Controlling
Processes
Overview of Controlling Processes
Controlling Processes
Performance Overall
Reporting Change Control
Facilitating Processes
To the
Planning
From the Processes
Executing Scope Change Control Cost
Control
Processes Control Schedule
To the
Closing
Processes
Purpose
Review and evaluate the project results and report the final outcome of the project.
Shutdown of all project work and processes as well as efforts to ensure future projects
benefit from the accomplishments of this project
Objectives Outputs
Review, evaluate and report project Post Project Report, includes final
accomplishments, deliverables, best project metrics and Lessons Learned
practices and lessons learned Post-Project Scorecard
Transition project staff Perform PM Compliance check
Transition to on-going operations’ Corporate Knowledge Base Updated
staff / production support
with Historical Project Data to leverage
Share project knowledge gained with
customer and Perot Systems on future projects as part of continuous
improvement
Communication Flow
Authorization
Start
Initiating Planning
Plans and
Processes Processes Updates
Changes
Status Executing
Controlling
Processes
Processes Guidance
Direction
Closing Operations
Processes
Overlap of Process Groups in a Phase
Time Finish
Feasibility
72
Typical PM’s day
Forecasting Managing
Expectations
Tracking, adjusting
Interpersonal
Problem
Solving
Team Work
BITS Pilani, Deemed to be University under Section 3 of UGC Act, 1956
Fifteen Project Management
Job Functions
• Define Scope of Project • Identify and Evaluate Risks
• Identify Stakeholders, • Prepare Contingency Plan
Decision-makers, and • Identify Interdependencies
Escalation Procedures
• Identify and Track Critical
• Develop detailed task list Milestones
(Work Breakdown Structures)
• Participate in Project Phase
• Estimate time requirements Review
• Develop initial Project • Secure Needed Resources
Management Flow Chart
• Manage the Change Control
• Identify required Resources Process
and Budget
• Report Project Status
• Evaluate Project
Requirements
Suggested Skills for Project Managers
Decision-maker n Manager
Coach n Sales person
Communication channel n PM expert
Encourager n Facilitator
Power broker n Behavior model
Disciplinarian n Other?
78
BITS Pilani, Deemed to be University under Section 3 of UGC Act, 1956
Project Manager Responsibilities
79
BITS Pilani, Deemed to be University under Section 3 of UGC Act, 1956
More Responsibilities
80
BITS Pilani, Deemed to be University under Section 3 of UGC Act, 1956
Project Management:
Relationship to Others Disciplines
The PMBOK™
Project
Management
Knowledge and
Practice
General Application
Management Area
Knowledge and Knowledge
Practice and Practice
• Knowledge
• Behaviors
• Attitude
• Organizational environment
• Project environment
• Fit
• Self-knowledge and ability to adjust
82
BITS Pilani, Deemed to be University under Section 3 of UGC Act, 1956
Project Manager Competency
Project Management Institute (PMI)
• Competence – “Demonstrated ability to perform
activities within a project environment that leads to
expected outcomes based on defined and accepted
standards”.
• Project Manager Competencies
• PM Knowledge (Process) Competencies –What the PM knows
about applying project management techniques to project
activities
• PM Performance (Technical/Scientific) Competencies - How the
PM applies knowledge to meet project requirements
• PM Personal (Leadership) Competencies – How a PM
behaves/performs in the project environment
83
85
• Project Sponsorship
• Health, Safety and Environmental
• Project Life Cycles
• Project Finance and Funding
• Legal Awareness
• Organizational Structure
• Governance of Project Management
88
89
Contact : sunilsoni@wilp.bits-pilani.ac.in
sonisunil@yahoo.com
+919810301926
BITS Pilani, Deemed to be University under Section 3 of UGC Act, 1956