WHAT IS APROJECT?
A project is a temporary endeavor undertaken to create a
unique product, service, or result.
5.
Characteristics of aProject
Is temporary
Creates unique products, services, or results
Provides progressive elaboration
The outcome may be tangible or intangible
A product that can be a component of another item
An enhancement of an item,
Or an end item in itself;
An improvement in the existing product or service
A result, such as an outcome or document
6.
Examples of Projects
Creating a new product
Creating a new service
Constructing a new building
Deploying a new business process
Buying a new information system
7.
Operations, Programs, Plans&
Portfolios
Both projects and operations:
1. Have people perform them
2. Are constrained by limited resources
3. Are planned, executed, and controlled
Operations differ from projects because they:
a. Are ongoing and repetitive
b. Have objectives that are continuous
c. Adapt to new objectives so work continues to sustain business.
8.
Operations, Programs, Plans&
Portfolios
Programs are groups of projects managed in a coordinated
way to obtain greater benefits and control, which could not
be achieved from managing the project separately. They are
a combination of related projects.
Plans are characterized and classified according to:
1. Their function or use to which they are applied
2. Their objectives, policies, procedures, methods and rules
3. Whether they short-term or long-term in duration
9.
Operations, Programs, Plans&
Portfolios
Portfolios are collections of projects or programs and their
associated operations that are grouped together to facilitate
effective management, as well as to meet strategic
objectives.
Portfolio management:
1. Satisfies strategic business objectives
2. Aids in selecting appropriate projects and programs to
maximize the portfolio value
3. Typically requires senior managers to be responsible for an
organization’s portfolio management.
10.
Projects and StrategicPlanning
Projects are often utilized as a means of directly or
indirectly achieving objectives within an organization’s
strategic plans.
Market Demand
Strategic opportunity/business need
Social need
Environmental consideration
Customer request
Technological advance
Legal requirement
11.
Project Management Office
The Project Management Office (PMO) can be
referred to as a program management Office, Project
office, or Program Office.
A Project Management Office (PMO) is a management
structure that standardizes the project-related
governance processes and facilitates the sharing of
resources, methodologies, tools, and techniques.
There are several types of PMO structures:
1. Supportive
2. Controlling
3. Directive
12.
Interpersonal Skills ofa Project
Manager
Leadership
Motivation
Communication
Conflict
management
Coaching
Team building
Influencing
Decision making
Political and
cultural awareness
Negotiation
#13 PMBOK Guide section 1.2
Project:
It has a definite beginning and an end
Performed by people
Constrained by resources
Creates a unique end result
#14 PMBOK Guide section 1.4.3, 1.6, 2.1 and 2.3.4
Knowledge Area
There are 9 knowledge areas in the PMBOK guide that make up chapters 4 to 12.
Project Life Cycle
The prior phase may create deliverables that are needed in subsequent phases. Different from product life cycles.
#15 PMBOK Guide 2004 section 3.0 See figures 3-6 to 3-10
#16 PMBOK Guide section 1.4.3, 1.6, 2.1 and 2.3.4
Knowledge Area
There are 9 knowledge areas in the PMBOK guide that make up chapters 4 to 12.
Project Life Cycle
The prior phase may create deliverables that are needed in subsequent phases. Different from product life cycles.
#17 PMBOK Guide section 1.4.3, 1.6, 2.1 and 2.3.4
Knowledge Area
There are 9 knowledge areas in the PMBOK guide that make up chapters 4 to 12.
Project Life Cycle
The prior phase may create deliverables that are needed in subsequent phases. Different from product life cycles.
#24 Rank reasons in the order of most significant reason to least significant reason
NOTE to instructor:
Use this as an exercise with class to rank what they think is important
Adapted from Source: Joint study Wister Polytech and Syracuse University
[insert the results from the Joint Study—need the date it was completed] – can’t find actual research. Will need to be replaced
From studies done, #3. Unclear project objectives is the number one reason for project failure
#25 # 3 and 6 - Delighted customers is the key indication of project success
#26 PMBOK Guide section 1.3
Managing the competing demands of time vs cost vs scope is key skill in achieving successful projects. Increased performance in one area may adversely affect performance in another area.
#31 Beyond PMBOK Guide
Liaison between the team and other entities
#32 Beyond PMBOK Guide
Examples of other items:
- Ownership of work
- Timely completion of work as promised
- Reasonable estimate
- Communication of red-flags or issues
- Accurate reporting of progress
- Follow-up & Follow thru
(Can be more based on class discussion)
#33 PMBOK Guide section 2.1
Projects usually are divided into several project phases to improve management control and provide for links to the ongoing operations.
#34 PMBOK Guide section 2.1
Projects usually are divided into several project phases to improve management control and provide for links to the ongoing operations.
#35 PMBOK Guide section 2.1.1
NEED to change process groups figure
#36 PMBOK Guide section 2.2. Stakeholders ability to influence the project outcomes are high at project start and decreases as the project goes through its life cycle. See PMBOK guide figure 2-2.
Stakeholders have different needs and expectations that must be managed for successful project acceptance. Both positive and negative stakeholders exist.
#37 PMBOK Guide section 2.2. Stakeholders ability to influence the project outcomes are high at project start and decreases as the project goes through its life cycle. See PMBOK guide figure 2-2.
Stakeholders have different needs and expectations that must be managed for successful project acceptance. Both positive and negative stakeholders exist.
#38 PMBOK Guide section 2.1.1
Similar to PMBOK Guide figure 2-2.
#43 PMBOK Guide section 2.3, figures 2-6 to 2-12.
Typified by the level of formal authority accorded the project manager. (ADAMS, Page 11)
Project Expeditor – Staff assistant to the exec. Who ultimately has responsibility for the project; a facilitator role
Project Coordinator – Auth to assign work to individuals in the functional organization; shared authority with functional manager
#48 PMBOK Guide section 2.3.3 Figure 2-9 for weak matrix and Figure 2-10 for balanced matrix organizations.
Note the difference between a Strong matrix and a composite organization.
#50 PMBOK Guide section 2.3.3, Figure 2-6.
Principles of Project Management, Adams page 20.
Levels at which the project and involved functional managers report and the backing they receive from top management
Collocation (tight matrix)
Percentage of time spent on project.
#51 PMBOK Guide section 2.3.3, Figure 2-6.
Principles of Project Management, Adams page 20.
Levels at which the project and involved functional managers report and the backing they receive from top management
Collocation (tight matrix)
Percentage of time spent on project.
#52 Interpreted from PMBOK Guide section 2.3.4
Project Management System is explained in PMBOK Guide section 2.3.5
#53 Principles of Project Management, Adams pg 24
Regardless of the organization
#54 PMBOK Guide Section:
1.2 and 1.3 What is a Project? What is Project Management
1.4.3 The PM Knowledge Areas
1.3 What is Project Management?
2.1.1 Characteristics of the Project Life Cycle
2.3.3 Organizational Structure
2.3.4 The role of the PMO