2. What is a project?
Aunique undertaking composed of interrelated activities which
hasawell defined beginning andend, often involving staff
from cross-functional groups, that operates under
specific constraints of resources,schedules, and requirements
3. What is a project?
Aunique undertaking composed of interrelated activities which
hasawell defined beginning and end, often involving staff
from cross-functionalgroups, that operates under
specific constraints of resources, schedules, and
requirements
4. What is Project?
Aproject is defined as any temporary endeavor undertaken
to create a unique product or service.
A project is a sequence of unique, complex, and connected
activities having one goal or purpose and that must be completed
by a specific time, within budget, and according to specification.
Attributes of projects
âąunique purpose
âątemporary
âąrequire resources, often from various areas
âąshould have a primary sponsor and/or customer
âąinvolve uncertainty
5.
6. Operations
Projects
Project & Operations
Perform Some Work
Change Routine
UNIQUE:
Not Done Before
TEMPORARY:
Definite START & END
REPETETIVE:
Identical Replication
CONTINUOUS:
Non-Stop
Build a Road
Construct a Dam
Build a Refinery
Change Accounting System
Construct Home
Use a Road
Daily Water Supply
Produce / Refine Oil
Daily Accounting Entries
Live in Home
7. There is a âneedâ
Project is âbornâ
Why Projects Initiate?
8. Why Projects Initiate?
T
o meet strategic business goals & objectives:
â«Strategic opportunity
â«Business needs
â«Market Demand
â«Technological advance
â«Legal requirements
â«??
Examples
9. What is a Project?(Certain Objective)
What is a Project?
â Certain Objective that is planned and organized carefully over a period of time â
Three Elements of Project (Triple Constraints)
Letâs Discuss about the Elements of Project
?
? ?
10. What is a Project?(Cont..)
Time
(Duration)
Resource
(Man power,
Facilities,
CostâŠ)
âą What are the requirements?
âą How much the cost?
âą Benefit Basis
Three Elements of Project
âą Start Date
âą End Date ?
âą What is the Output ?
âą Purpose & Scope
âą Product Performance Specification
O
O
u
u
t
t
p
p
u
u
t
t
(O
(
O
bb
jej
e
cc
tt
i
iv
v
e
e&
&
S
S
c
c
o
o
p
p
e
e
)
)
14. Project Management
Project management is the discipline of planning, organizing, and managing
resources to bring about the successful completion of specific project goals and
objectives.
OR
Project Management is the application of knowledge, skills, tools and
techniques to project activities in order to meet project requirement. (PMBOK
Fourth Edition)
The purpose of project management is prediction and
prevention, NOT recognition and reaction
15. The goal of Project Management
. . . Delivering a quality
Product/Services/Solution
. . . Providing business value and
meeting customer needs
16. What Is Program Management?
Program:
â« Group of related projects
â« Projects managed together to harness greater opportunities and control
â« Can include elements that would ordinarily be out of scope for the
projectsbeingintegrated
Program Management:
The management of a collection of projects, often with a
focus on the efficient coordination of resources and
priorities
17. What Is Portfolio Management?
â« Portfolio Management:
The central management of one or more portfolios, which includes identifying,
prioritizing, authorizing, managing, and controlling projects, programs, and other
related work to achievestrategic businessobjectives
18. Enterprise Project Management
Enterprise Project Management (EPM), in broad terms, is the field of
organizational development that supports organizations in managing projects,
program, portfolio; integrative & collaborative environment.
Enterprise Project Management is not simply an application or a concept
âIt is a set of uniform processes, methods, skills, and application solutions
that provide discrete benefits supported and managed by Peopleâ
Microsoft
19. Project Manager
â«Someone responsible for
â«Planning
â« Strategic
â«Schedulingand coordinating
â« Tactical
â«W
orking with people
â« Art
â« Soft skills
20. Personal Benefits of Project Management
â«Provides focus and clarity
â«Helps prevent fire-fighting
â«Builds oneâsreputation and network
â«Develops portable skills and experience
â«Allows you to be more strategicin your thinking/planning
â«Enhances both professional and personal growth
opportunities
â«Minimizes overtime and Helps you be more successful
with projects,which isgood for your career
21. Organizational Benefits of Project Management
â« Proper alignmentof projects to strategic objectives
â« Better wayof controllingbusiness/Enterprise
â« Better control of financial,physical,and human resources.
â«Improved customer relations.
â«Shorter development times.
â«Lower costs.
â«Higher quality and increased reliability
.
â«Improved productivity
.
â«Better internal coordination.
â«Higher worker morale (less stress).
23. Project Management Body Of .
Knowledge (PMBOK Guide)
PMBOK recognizes 5 basic process groups and 10 knowledge
areas typical of almost all projects. The basic concepts are
applicable to projects, programs and operations.
The five basic process groups are:
ï”Initiating
ï”Planning
ï”Executing
ï”Controlling and Monitoring
ï”Closing.
Processes are described in terms of:
Inputs (documents, plans, designs, etc.)
Tools and Techniques (mechanisms applied to inputs)
Outputs (documents, products, etc.)
25. Project Management Process Groups
â«Aprocess is aseries of actions directed toward aparticular result.
â«Project management can be viewed asanumber of interlinked
processes.
â«The project management process groups include:
â«Initiating processes
â«Planning processes
â«Executing processes
â«Monitoring and controlling processes
â«Closing processes
28. PMBOK Guide â Knowledge Areas
In previous Slide, I discussed the project life cycle. There are 49 processes of project
management are divided into five process groups and these processes are also
divided among ten knowledge areas.
These are the 10 Project Management knowledge areas:
1. Project Integration Management
2. Project Scope Management
3. Project Schedule Management
4. Project Cost Management
5. Project Quality Management
6. Project Resource Management
7. Project Communications Management
8. Project Risk Management
9. Project Procurement Management
10. Project Stakeholder Management
29. Initiating
â« Weneed to determine what the customer wants
â« W
e do this byidentifying:
â« Requirements
â« Goals
â« Deliverables
â« Successcriteria
â« Scope
â« Risks
â« Impact
â« Probability
30. Planning
â« W
e know what we want
â« Now
, we figure out how to do the work required
â« W
e do this by:
â« Performingarchitecture &design
â« Identifying activities:work breakdown structure (WBS)
â« Identifying dependencies between activities
â« Estimatingactivity duration
â« Estimating activity resource requirements
â« Schedulingactivities (start date, duration)
31. Executing
â« W
e have adetailed work plan
â« Now
, we get the work underway
â« W
e do this by:
â« Identify&Choose team members
â« Makingmembers available for the project
â« Organizingmembers into team(s)
â« Assigningwork to team(s)
â« Providingresources to the team(s)
â« Establishconstraints andfreedoms for the team(s)
32. Monitoring & Controlling
â« W
e have people working on activities
â« Now,we must ensure we are making adequate progress
â« W
e do this by:
â« Interviewingand observingprogressreports
â« Implementingversion control software
â« Providingmechanisms for requesting changes
â« Continuallyupdating plans (e.g.schedules)
33. Closing
â« W
e have completed all activities
â« The result should be that
â« All overall goalsare satisfied
â« Allconditions of satisfaction are met
â« Alldeliverables are ready for roll-out
â« Now
, we need to complete hand-over
â« W
e do this by:
â« Obtainingclient acceptance
â« Deployingdeliverables
â« e.g.media disks,printed manuals,online deployment/downloads
â« Performingapost-mortem analysis
â« How did we do?
35. Project Life Cycle â Overview
â« Collection of project phases that are generally sequential and
sometimes overlapping
â« A Project life cycle can be documented with a methodology
â« The unique aspects of the organization, industry or technology
can determine or shaped the project life cycle.
â« The life cycle provides the basic framework for managing the
project, regardless of the specific work involved
37. Project Life Cycle â Characteristics
â« Vary in Size and Complexity
â« No matter what is size & complexity level, it is mapped in:
â« Starting Project
â« Organizing & Preparing
â« Carry out / Execution of Project Work and
â« Closing the Project
â« Cost & Staffing Level (Low / Peak / Drop)
â« Stakeholdersâ influences, risk, and uncertainty are greatest at
the start of the project. These factors decrease over the life
of the project.
â« Cost of Change increases as the project progresses and the
product is getting maturity.
39. Project Life Cycle â Project Phases
â« Divisions within a project to have extra control for
effective completion of a major deliverable.
â« Project phases are typically completed sequentially,
but can overlap in some project situations.
â« The high level nature of project phases makes them
an element of the project life cycle.
â« A project phase is not a Project Management Process
Group
â« Number of phases, their Need and the degree of
control depend on the size, complexity, and potential
impact of the project.
â« All phases have similar characteristics.
40. Project Phases: Characteristics
â« When phases are sequential,at close of aphase some work product is
transfer or handoff asphasedeliverable.
â« This phaseend represents anatural point to reassess the effort
underway and to change or terminate the project if necessary.
â« These points are referred to as phase exits, milestones, phase
gates, decision gates, stage gates, or kill points.
â« DistinctWork &Responsibilitiesin different phases
â« Repetition of processes across all five Process Groups, provides the
desired additional degree of control, and defines the
boundaries of the phase.
41. Project Phases: Characteristics
â« Project Governance across life cycle.
â« Phase to Phase Relationship (3-types)
â« Sequential
â« Overlapping
â« Iterative
â« more than one phase-to-phase relationship may occur
during the project life cycle.
43. Organizational Influence on Project Management
Organizational Structure:
â«Organizational structure is an enterprise
environmental factor which can affect the
availability of resources and influence how
projects are conducted.
â«Organizational structures range from
functional to projectized, with a variety of
matrix structures between them.
44. Functional Organization
â« T
op driven
â« Eachemployee reports to onlyone manager and ultimately one
person is at theTOP
â« Normallyculture is Dictate and Follow - Bureaucracydoes exists
â« Each department is managed independentlyand has limited span
of control
â« People with similar skills and experience â easier to manage
â« Work assignment is easier &clear upward career path
â« Lines of reporting &information distribution are clear
â« Roles are clear &ability to develop skillsare better in aparticular
â« functional area
45. Projectized Organization
â« Organization that earns its revenue by doing projects
for others
â« Project manager has full authority to assign priorities
and to direct work of individuals assigned to the
project
â« For many complex / large and long term projects, this
is generally preferred organization
â« The success of such organization largely depends
upon clarity of purpose / quality of leadership and
level of motivation of the work force & excellent
communication systems within the stake holders
46. Organizational Influence on Project Management
Organizational ProcessAssets:
â« Include anyor all processrelated assets,
â« From anyor all of the organizations involved in the project
â« These process assets include formal and informal plans,policies,
procedures,and guidelines.
â« The process assets also include the organizationâsknowledge bases
suchaslessonslearned andhistoricalinformation / data.
â« Updating and adding to the organizationalprocess assetsis
necessary throughout the project.
â« Generally is the responsibilityof the project team members.
47. Organizational Influence on Project Management
â«Organizational ProcessAssets:
â«Organizational processassets maybe grouped into two
categories:
â«1 - Processes and Procedures
â«The organizationâs processes and procedures for conducting
work
â«2 - Corporate Knowledge Base
â«The organizationalcorporate knowledge base for storing and
retrievinginformation â Historicaldata
48. Enterprise Environmental Factors
â« Refer to both internal and external environmental factorsthat
surround or influence aprojectâs Manager.
â« Enterprise environmental factors mayenhanceor constrain
project management optionsand mayhave apositive or negative
influence on the outcome.
â« They are considered asinputs to most planning processes.
â« Cultural and Socialenvironment
â« Understanding of economic, demographic, educational,
ethical, ethnic,religion and other characteristic of people
â« Political and International environment
â« Understanding of international, national,local laws and customs as
well as political aspects
â« Physicalenvironment
â« Local geography
, surrounding, etc
49. Most Important Skills and
Competencies for Project Managers
1. People skills
2. Leadership
3. Listening
4. Integrity, ethical behavior, consistent
5. Strong at building trust
6. Verbal communication
7. Strong at building teams
8. Conflict resolution, conflict management
9. Critical thinking, problem solving
10. Understands, balances priorities
65
50. Different Skills Needed in Different Situations
â« Large projects: leadership, relevant prior experience,
planning, people skills, verbal communication, and team-
building skills are most important
â« High uncertainty projects: risk management, expectation
management, leadership, people skills, and planning skills
are most important
â« Very novel projects: leadership, people skills, having vision
and goals, self-confidence, expectations management, and
listening skills are most important