Introduction To Project Management
Introduction To Project Management
Introduction To Project Management
This chapter provides an overview of project management, defining both projects and project
management and exploring the difference between project management and operations
management. Advances in technology are driving the speed of innovation and the ability of
organizations to shorten the time needed to develop and deliver new products and services that
increase an organization’s competitive advantage. This drive to develop new and unique
products or services creates a perfect environment for the application of project management
methodologies and skills. We also provide a brief overview of the knowledge areas of project
management and the skills needed to be a successful project manager.
“Project management is the application of knowledge, skills, tools, and techniques to project
activities to meet the project requirements.”Project Management Institute, Inc., A Guide to the
Project Management Body of Knowledge (PMBOK Guide), 4th ed. (Newtown Square, PA:
Project Management Institute, Inc., 2008), 6. This simple definition represents a compromise that
resulted from intense discussions within the Project Management Institute (PMI) during the
1980s. One of the priorities of PMI during this time was the development of project management
as a profession. Although debate continues on whether project management is a profession with
an enforceable code of conduct and other traditional criteria for recognition as a profession, the
development of A Guide to the Project Management Body of Knowledge (PMBOK Guide) and
the project management certifications that derived from these efforts helped promote the
understanding and development of the project management field.
The discussion about what should be in the definition of project management included debates
about the purpose of project management. Is the main purpose to meet client expectations or is
the main purpose to meet the written specifications and requirements? This discussion around
meeting project requirements was not easily settled. If it is assumed that the project client is the
one who defines project requirements, then maybe project management is the application of
knowledge, skills, tools, and techniques to meet client requirements or client expectations. PMI’s
definition of project management does provide a good understanding of project management, but
it does not help us understand project success. For that, we must include the client.
Figure 1.1
Project discussions include clients.
Jack Meredith and Samuel MantelJack R. Meredith and Samuel J. Mantel, Jr., Project
Management: A Managerial Approach (Hoboken, NJ: Wiley, 2006), 8. discussed project
management in terms of producing project outcomes within the three objectives of cost,
schedule, and specifications. Project managers are then expected to develop and execute a
project plan that meets cost, schedule, and specification parameters. According to this view,
project management is the application of everything a project manager does to meet these
parameters. This approach to defining project management shares PMI’s focus on the project
outcomes in terms of requirements.
Meredith and Mantel added a fourth aspect of project management—the expectations of the
client. One client-centered definition of project management is the application of knowledge,
skills, tools, and techniques to meet or exceed the expectations of the client. This definition
focuses on delivering a product or service to the client that meets expectations rather than project
specifications. It is possible to meet all project specifications and not meet client expectations or
fail to meet one or more specifications and still meet or exceed a client’s expectation.Russell W.
Darnall, The World’s Greatest Project (Newtown Square, PA: Project Management Institute,
Inc., 1996), 48–54.
Client expectations encompass an emotional component that includes many client desires that are
not easily captured within a specification document. Although closely correlated with project
specifications, client expectations are driven by different needs. It is possible for a project team
to exceed every project specification and end up with an unsatisfied client.
Highway Project
The Department of Highways in South Carolina was exploring ways to reduce the road
construction costs and developed new contracting processes to allow the road builders to bring
new ideas for cutting costs. On one project, the contractor proposed cost-cutting ideas throughout
the life of the project. At each phase, the client accepted many of the ideas and then revised the
budget. The client promoted the revised cost target of the project as an example of the success of
the new process. By the end of the project, the final cost was less than 1 percent over the newest
target. Although the total cost of the project was almost 10 percent less than the original cost
projections and contract obligations, the success of the project was connected to the new
expectations that developed during the life of the project. Even though this project performance
exceeded the original goal, the client was disappointed.
The reverse is also true. A project can be late and over budget and the client can be satisfied.
Although this may be counterintuitive, the response of a client to the events of a project is
complex and goes beyond the data related in project specifications.
Biotech Project
A biotechnology company developed a new drug that proved to have a large market demand, and
the team that developed the drug was assigned to build a new manufacturing facility to produce
the drug. The project manager for the construction company that was awarded the contract to
build the manufacturing facility managed the project effectively. Every request for a change in
scope was approved, and the result was a 20 percent increase to the total cost of the project. On
most projects, a 20 percent increase in the project cost would be considered poor performance.
For the client’s project team, who were accustomed to complex projects with a large number of
unknown issues that increase the final cost of the project, a 20 percent overrun in cost was not
unusual. Even though the project was 20 percent over budget, the client was happy. Client
satisfaction is often tied to expectations about project performance. Identifying and managing
those expectations is a primary responsibility of the project manager.
K EY TAK EAWAYS
According to PMI, project management is the application of knowledge, skills, tools, and
techniques to meet project requirements.
The role of the client is controversial. Some clients include meeting or exceeding their
expectations as part of project management.
Project scope is a document that defines the work required to complete the project
successfully.
EXERCI SES
Compare and contrast the highway and biotech examples previously described. Suggest
an approach that might have prevented client disappointment in the highway project.
Include the following in your answer:
What are the differences between the two projects? Provide a bulleted list.
Identify the single most important difference between the two projects that affected client
satisfaction.
Suggest an approach to managing client expectations in the highway project that might
have resulted in meeting or exceeding expectations rather than disappointment.
1.2 Project Defined
LEARNI NG O BJECTIVES
The Project Management Institute (PMI) defines a project by its two key characteristics. All
projects are temporary and undertaken to create a product, service, or result that is unique.Project
Management Institute, Inc., A Guide to the Project Management Body of Knowledge (PMBOK
Guide), 4th ed. (Newtown Square, PA: Project Management Institute, Inc., 2008), 5. These two
simple concepts create a work environment that mandates different management approach from
that used by an operations manager, whose work is oriented toward continuous improvement of
existing processes over longer periods of time. A project manager needs a different set of skills
to both define and successfully execute temporary projects. Because projects are temporary, they
have a defined beginning and end. Project managers must manage start-up activities and project
closeout activities. The processes for developing teams, organizing work, and establishing
priorities require a different set of knowledge and skills because members of the project
management team recognize that it is temporary. They seldom report directly to the project
manager and the effect of success or failure of the project might not affect their reputations or
careers the same way that the success or failure of one of their other job responsibilities would.
Figure 1.2
Projects are temporary.
The second characteristic of a project, the delivery of a unique product, service, or result, also
changes the management approach to the work. A project manager must take time to understand
the deliverables of a project, develop a plan for producing the deliverables in the time available,
and then execute that plan.
Projects are also defined within the context of larger projects as the following example
illustrates.
The National Energy Technology Laboratory laid out a plan for a national energy policy that had
a clear and identifiable outcome—providing reliable, affordable, and environmentally sound
energy.National Energy Technology Laboratory, “Reliable, Affordable, and Environmentally
Sound Energy for America’s Future,” The Energy Lab,
2001,http://www.netl.doe.gov/publications/press/2001/nep/nep.html (accessed June 18,
2009). The details of this plan will be revised and updated, but the general goals are likely to
remain unchanged. To accomplish these goals, the project requires the development of new
technologies, complex scheduling and cost control, coordination of a large number of
subcontractors, and skillful stakeholder management. Development of each of the major
components became a project for the winning contractors within the larger project of providing
reliable, affordable, and environmentally sound energy. Contractors for cleaner use of fossil
fuels, conservation efforts, and development of renewable energy sources would manage major
projects. Each project has to develop new technologies, manage a large number of
subcontractors, and manage the stakeholders at the Department of Energy.
Each subcontractor or work unit becomes a project for that organization. The project is defined
by the scope of work. In the energy policy, the scope of work included all activities associated
with reducing use of fossil fuels and reliance on imported energy. Using our definition that a
project is a temporary endeavor that creates a unique product or service, implementation of the
energy policy would be a project that consists of other projects, such as development of the
following:
Wind power
Solar power
Electricity transmission
Electricity storage
New nuclear reactor design and installation
Other renewable energy sources
Biofuels
Electric vehicles
Nonpolluting use of coal and natural gas
Environmental protection
K EY TAK EAWAYS
All projects are temporary and undertaken to create a product, service, or result.
Projects can contain smaller projects.
EXERCI SES
1. The project scope is the _____ required to complete the project successfully.
2. According to PMI, all projects are ________ and undertaken to create a product or service
that is unique.
3. Projects can contain ___________ projects.
4. What are two defining characteristics of a project that distinguish it from a process?
5. If you were planning to move from your current apartment or home to another location,
would this qualify as a project? Explain your answer.
1.3 Project Context
LEARNI NG O BJECTIVES
The project is affected by the type of organization in which the project is conducted and how the
organization is organized to manage projects.
Organizational Priorities
Organizations fulfill a societal role to meet economic, religious, and governance functions. Local
factories, churches, and hospitals are all organizations that provide some social or community
need. Factories create wealth and jobs, churches provide spiritual and common social needs for
communities, and government organizations provide regulations and services that allow for an
orderly society. These organizations have different views of time and each organization develops
an operational approach to accomplishing the purpose of the organization over that time horizon.
For example, a religious group might begin construction of a cathedral that would take several
lifetimes to complete, government performance is reviewed at election time, and a publicly
owned company must justify its use of money each year in the annual report.
Organizations operate to effectively and efficiently produce the product or service that achieves
the organization’s purpose and goals as defined by the key stakeholders—those who have a share
or interest. An organization seeks to develop stable and predictable work processes and then
improve those work processes over time through increased quality, reduced costs, and shorter
delivery times. Total quality management, lean manufacturing, and several other management
philosophies and methodologies have focused on providing the tools and processes for increasing
the effectiveness and efficiency of the organization. Historically, these methodologies focused on
creating incremental and continuous improvement in work processes. More recently,
organizations are increasingly focused onstep changes that take advantage of new technologies to
create a significant improvement in the effectiveness or efficiency of the organization.
Each of the initiatives meets our definition of a project. Each is a temporary endeavor and
produces a unique product or service. Managing these projects effectively entails applying
project management knowledge, skills, and tools.
Figure 1.3
Managing operations focuses on improving repetitive processes.
Project managers focus on the goals of the project. Project success is connected to achieving the
project goals within the project timeline. Project managers are goal directed and time sensitive.
Project managers apply project management tools and techniques to clearly define the project
goals, develop an execution plan to meet those goals, and meet the milestones and end date of
the project.
An operations manager may invest $10,000 to improve a work process that saves $3,000 a year.
Over a five-year period, the operations manager improved the profitability of the operations by
$5,000 and will continue to save $3,000 every year. The project manager of a one-year project
could not generate the savings to justify this kind of process improvement and would not invest
resources to explore this type of savings.
An operations manager creates a culture to focus on the long-term health of the organization.
Operations managers build teams over time that focus on standardizing and improving work
processes, that search for and nurture team members who will “fit in,” and that contribute to both
the effectiveness of the team and the team culture. Project managers create a team that is goal
focused and energized around the success of the project. Project team members know that the
project assignment is temporary because the project, by definition, is temporary. Project team
members are often members of organizational teams that have a larger potential to affect long-
term advancement potential. Project managers create clear goals and clear expectations for team
members and tie project success to the overall success of the organization. Operations managers
are long-term focused and process oriented. Project managers are goal directed and milestone
oriented.
Some organizations are designed to execute projects. Often entities contract with engineering
and construction companies to design and build their facilities or hire software companies to
develop a software solution. The major work processes within these organizations are designed
to support the acquisition and execution of projects. Functional departments such as estimating,
scheduling, and procurement create and maintain core competencies designed to support
projects. The ability of these types of organizations to successfully manage projects becomes a
competitive advantage in the marketplace.
Organizations designed to produce products or services also use projects. Major activities outside
the normal work of the organization’s department or functional units or major activities that
cross functional boundaries become a project (a temporary task undertaken to create a product or
service that is unique). As economic pressures increase the speed in which organizations must
change and adapt to new environmental conditions, leaders are increasingly chartering projects
to enable the organization to more quickly adapt. The application of a project management
approach increases the likelihood of success as organizations charter a project to facilitate
organizational change, to increase the development and introduction of new products or support
the merger or divesture of organizational units.
PMOs can provide various functions for an organization. Some possible functions include the
following:
Project management. Some organizations maintain the project manager within the PMO,
assign project managers from other departments, procure contract project managers, or
practice a combination of all three.
Center of excellence. The project office can maintain the organization’s project
management policies and procedures, maintain a historical database, maintain best
practices, and provide training and specialized expertise when needed.
Portfolio management. The project office actually supervises the project managers and
monitors project performance. Portfolio management also includes prioritizing projects
on the basis of value to the organization and maintains an inventory of projects. Portfolio
management balances the number and type of projects to create the greatest return from
the entire portfolio of projects.
Functional support. The project office maintains project management expertise to
support the project. Estimating, project scheduling, and project cost analysis are examples
of functional support.
K EY TAK EAWAYS
The purpose of an organization can affect its view of the time allowed for projects.
In an organization, project management can be used to make step changes to take
advantage of new technologies or make significant improvements in effectiveness or
efficiency.
Operations managers are long-term focused and process oriented. Project managers are
goal directed and milestone oriented.
Projects can be handled by outside contractors or by an internal group in a PMO.
EXERCI SES
1. The type of organization can influence the ____ frame allowed for projects.
2. Operations managers are focused on __________, while project managers are focused on
the goals of the project.
3. If projects are routinely handled internally, the group that manages the projects might be
called the ______ ______ _____ (three words).
4. A friend of yours has a forty-five-minute commute to work. She decides to spend some
time evaluating the different options she has for routes and possible carpooling to reduce
the cost or time it takes to get to work. Is this task an example of something that uses the
skills of an operations manager, or does it need the additional skills of a project manager?
Explain your answer and refer to the definitions provided.
5. Business managers focus on improving efficiency and effectiveness, but sometimes they
use a project management approach to make significant changes. What often prompts
them to use the project management approach? What would be an example?
The manager of a sales department must meet annual sales goals, manage personnel in the
department, and develop and deliver product training for clients. How is this type of
operations management different from project management? Address each of the
following issues in your answer:
How is the relationship between the operations manager and the sales staff different from
the relationship between a project manager and the project team members?
Which of the duties described above is most like project management and might be
contracted to an outside firm?
What is the biggest difference between project management and the sales manager’s job?
Every project is unique, and most projects will encounter unexpected technical challenges. Each
project management team is a group of individuals who need motivation and coordination.
Planning is vital, but the ability to adapt to changes and work with people to overcome
challenges is just as necessary. A project manager must master the skills that are necessary to be
successful in this environment.
Often the difference between the project that succeeds and the project that fails is the leadership
of the project manager. The leadership skills needed by the successful project manager include
all the skills needed by operations managers of organizations. These skills include:
Good communication
Team building
Planning
Expediting
Motivating
Political sensitivity
Because project managers generally operate in a project environment that is more time sensitive
and goal driven, the successful project manager requires additional knowledge, skills, and
abilities.
Figure 1.4
Project managers must have additional skills.
Credibility
Creativity as a problem solver
Tolerance for ambiguity
Flexibility in management style
Effectiveness in communicating
Thamhain’s work provides a taxonomy for better understanding the skills needed by project
managers.
Traditionally, the project manager has been trained in skills such as developing and managing
the project scope, estimating, scheduling, decision making, and team building. Although the
level of skills needed by the project manager depends largely on the project profile, increasingly
the people skills of the project manager are becoming more important. The skills to build a high-
performing team, manage client expectations, and develop a clear vision of project success are
the type of skills needed by project managers on more complex projects. “To say Joe is a good
project manager except he lacks good people skills is like saying he’s a good electrical engineer
but doesn’t really understand electricity.”Russell W. Darnall, “The Emerging Role of the Project
Manager,” PMI Journal (1997): 64.
K EY TAK EAWAYS
Project managers need the same skills as an operations manager, such as good
communications, team building, planning, expediting, and political sensitivity.
Project managers need additional skills in establishing credibility, creative problem
solving, tolerance for ambiguity, flexible management, and very good people skills.
EXERCI SES
Rate your personal project management skills using the following scale:
S Strong
M Moderate
I Improvement needed
Operational management skills:
1. Good communication
2. Team building
3. Planning
4. Expediting
5. Motivating others
6. Sensitive to the politics of a situation
Projects are divided into components, and a project manager must be knowledgeable in each
area. Each of these areas of knowledge will be explored in more depth in subsequent chapters.
The start-up of a project is similar to the start-up of a new organization. The project leader
develops the project infrastructure used to design and execute the project. The project
management team must develop alignment among the major stakeholders—those who have a
share or interest—on the project during the early phases or definition phases of the project. The
project manager will conduct one or more kickoff meetings or alignment sessions to bring the
various parties of the project together and begin the project team building required to operate
efficiently during the project.
During project start-up, the project management team refines the scope of work and develops a
preliminary schedule and conceptual budget. The project team builds a plan for executing the
project based on the project profile. The plan for developing and tracking the detailed schedule,
the procurement plan, and the plan for building the budget and estimating and tracking costs are
developed during the start-up. The plans for information technology, communication, and
tracking client satisfaction are all developed during the start-up phase of the project.
Flowcharts, diagrams, and responsibility matrices are tools to capture the work processes
associated with executing the project plan. The first draft of the project procedures manual
captures the historic and intuitional knowledge that team members bring to the project. The
development and review of these procedures and work processes contribute to the development
of the organizational structure of the project.
This is typically an exciting time on a project where all things are possible. The project
management team is working many hours developing the initial plan, staffing the project, and
building relationships with the client. The project manager sets the tone of the project and sets
expectations for each of the project team members. The project start-up phase on complex
projects can be chaotic, and until plans are developed, the project manager becomes the source of
information and direction. The project manager creates an environment that encourages team
members to fully engage in the project and encourages innovative approaches to developing the
project plan.
Project Scope
The project scope is a document that defines the parameters—factors that define a system and
determine its behavior—of the project, what work is done within the boundaries of the project,
and the work that is outside the project boundaries. The scope of work (SOW) is typically a
written document that defines what work will be accomplished by the end of the project—the
deliverables of the project. The project scope defines what will be done, and the project
execution plan defines how the work will be accomplished.
No template works for all projects. Some projects have a very detailed scope of work, and some
have a short summary document. The quality of the scope is measured by the ability of the
project manager and project stakeholders to develop and maintain a common understanding of
what products or services the project will deliver. The size and detail of the project scope is
related to the complexity profile of the project. A more complex project often requires a more
detailed and comprehensive scope document.
The scope document is the basis for agreement by all parties. A clear project scope document is
also critical to managing change on a project. Since the project scope reflects what work will be
accomplished on the project, any change in expectations that is not captured and documented
creates the opportunity for confusion. One of the most common trends on projects is the
incremental expansion in the project scope. This trend is labeled scope creep. Scope creep
threatens the success of a project because the small increases in scope require additional
resources that were not in the plan. Increasing the scope of the project is a common occurrence,
and adjustments are made to the project budget and schedule to account for these changes. Scope
creep occurs when these changes are not recognized or not managed. The ability of a project
manager to identify potential changes is often related to the quality of the scope documents.
Events do occur that require the scope of the project to change. Changes in the marketplace may
require change in a product design or the timing of the product delivery. Changes in the client’s
management team or the financial health of the client may also result in changes in the project
scope. Changes in the project schedule, budget, or product quality will have an effect on the
project plan. Generally, the later in the project the change occurs, the greater the increase to the
project costs. Establishing a change management system for the project that captures changes to
the project scope and assures that these changes are authorized by the appropriate level of
management in the client’s organization is the responsibility of the project manager. The project
manager also analyzes the cost and schedule impact of these changes and adjusts the project plan
to reflect the changes authorized by the client. Changes to the scope can cause costs to increase
or decrease.
Figure 1.5
Project managers must track the schedules of several activities at the same time.
The definition of project success often includes completing the project on time. The development
and management of a project schedule that will complete the project on time is a primary
responsibility of the project manager, and completing the project on time requires the
development of a realistic plan and the effective management of the plan. On smaller projects,
project managers may lead the development of the project plan and build a schedule to meet that
plan. On larger and more complex projects, a project controls team that focuses on both costs and
schedule planning and controlling functions will assist the project management team in
developing the plan and tracking progress against the plan.
To develop the project schedule, the project team does an analysis of the project scope, contract,
and other information that helps the team define the project deliverables. Based on this
information, the project team develops a milestone schedule. The milestone schedule establishes
key dates throughout the life of a project that must be met for the project to finish on time. The
key dates are often established to meet contractual obligations or established intervals that will
reflect appropriate progress for the project. For less complex projects, a milestone schedule may
be sufficient for tracking the progress of the project. For more complex projects, a more detailed
schedule is required.
To develop a more detailed schedule, the project team first develops a work breakdown structure
(WBS)—a description of tasks arranged in layers of detail. Although the project scope is the
primary document for developing the WBS, the WBS incorporates all project deliverables and
reflects any documents or information that clarifies the project deliverables. From the WBS, a
project plan is developed. The project plan lists the activities that are needed to accomplish the
work identified in the WBS. The more detailed the WBS, the more activities that are identified to
accomplish the work.
After the project team identifies the activities, the team then sequences the activities according to
the order in which the activities are to be accomplished. An outcome from the work process is
the project logic diagram. The logic diagram represents the logical sequence of the activities
needed to complete the project. The next step in the planning process is to develop an estimation
of the time it will take to accomplish each activity or the activity duration. Some activities must
be done sequentially, and some activities can be done concurrently. The planning process creates
a project schedule by scheduling activities in a way that effectively and efficiently uses project
resources and completes the project in the shortest time.
On larger projects, several paths are created that represent a sequence of activities from the
beginning to the end of the project. The longest path to the completion of the project is
the critical path. If the critical path takes less time than is allowed by the client to complete the
project, the project has a positive total float or project slack. If the client’s project completion
date precedes the calculated critical path end date, the project has negative float. Understanding
and managing activities on the critical path is an important project management skill.
To successfully manage a project, the project manager must also know how to accelerate a
schedule to compensate for unanticipated events that delay critical activities. Compressing—
crashing—the schedule is a term used to describe the techniques used to shorten the project
schedule. During the life of the project, scheduling conflicts often occur, and the project manager
is responsible for reducing these conflicts while maintaining project quality and meeting cost
goals.
Project Costs
The definition of project success often includes completing the project within budget.
Developing and controlling a project budget that will accomplish the project objectives is a
critical project management skill. Although clients expect the project to be executed efficiently,
cost pressures vary on projects. On some projects, the project completion or end date is the
largest contributor to the project complexity. The development of a new drug to address a critical
health issue, the production of a new product that will generate critical cash flow for a company,
and the competitive advantage for a company to be first in the marketplace with a new
technology are examples of projects with schedule pressures that override project costs.
The accuracy of the project budget is related to the amount of information known by the project
team. In the early stages of the project, the amount of information needed to develop a detailed
budget is often missing. To address the lack of information, the project team develops different
levels of project budget estimates. The conceptual estimate (or “ballpark estimate”) is developed
with the least amount of knowledge. The major input into the conceptual estimate is expert
knowledge or past experience. A project manager who has executed a similar project in the past
can use those costs to estimate the costs of the current project.
Figure 1.6
Early project decisions are based on rough estimates.
When more information is known, the project team can develop a rough order of magnitude
(ROM) estimate. Additional information such as the approximate square feet of a building, the
production capacity of a plant, and the approximate number of hours needed to develop a
software program can provide a basis for providing a ROM estimate. After a project design is
more complete, a project detailed estimate can be developed. When the project team knows the
number of rooms, the type of materials, and the building location of a home, the project team can
provide a detailed estimate. A detailed estimate is not a bid.
The cost of the project is tracked relative to the progress of the work and the estimate for
accomplishing that work. Based on the cost estimate, the cost of the work performed is compared
against the cost budgeted for that work. If the cost is significantly higher or lower, the project
team explores reasons for the difference between expected costs and actual costs.
Project costs may deviate from the budget because the prices in the marketplace were different
from what was expected. For example, the estimated costs for lumber on a housing project may
be higher than budgeted or the hourly cost for labor may be lower than budgeted. Project costs
may also deviate based on project performance. For example, the project team estimated that the
steel design for a bridge over the Hudson River would take 800 labor hours, but 846 hours were
actually expended. The project team captures the deviation between costs budgeted for work and
the actual cost for work, revises the estimate as needed, and takes corrective action if the
deviation appears to reflect a trend.
The project manager is responsible for assuring that the project team develops cost estimates
based on the best information available and revises those estimates as new or better information
becomes available. The project manager is also responsible for tracking costs against the budget
and conducting an analysis when project costs deviate significantly from the project estimate.
The project manager then takes appropriate corrective action to assure that project performance
matches the revised project plan.
Project Quality
Project quality focuses on the end product or service deliverables that reflect the purpose of the
project. The project manager is responsible for developing a project execution approach that
provides for a clear understanding of the expected project deliverables and the quality
specifications. The project manager of a housing construction project not only needs to
understand which rooms in the house will be carpeted but also what grade of carpet is needed. A
room with a high volume of traffic will need a high-grade carpet.
The project manager is responsible for developing a project quality plan that defines the quality
expectations and assures that the specifications and expectations are met. Developing a good
understanding of the project deliverables through documenting specifications and expectations is
critical to a good quality plan. The processes for assuring that the specifications and expectations
are met are integrated into the project execution plan. Just as the project budget and completion
dates may change over the life of a project, the project specifications may also change. Changes
in quality specifications are typically managed in the same process as cost or schedule changes.
The impact of the changes is analyzed for impact on cost and schedule, and with appropriate
approvals, changes are made to the project execution plan.
The Project Management Institute’s A Guide to the Project Management Body of Knowledge
(PMBOK Guide) has an extensive chapter on project quality management. The material found in
this chapter would be similar to material found in a good operational management text. Although
any of the quality management techniques designed to make incremental improvement to work
processes can be applied to a project work process, the character of a project (unique and
relatively short in duration) makes small improvements less attractive on projects.
Rework on projects, as with manufacturing operations, increases the cost of the product or
service and often increases the time needed to complete the reworked activities. Because of the
duration constraints of a project, the development of the appropriate skills, materials, and work
process early in the project is critical to project success. On more complex projects, time is
allocated to developing a plan to understand and develop the appropriate levels of skills and
work processes.
Project management organizations that execute several similar types of projects may find the
process improvement tools useful in identifying and improving the baseline processes used on
their projects. Process improvement tools may also be helpful in identifying cost and schedule
improvement opportunities. Opportunities for improvement must be found quickly to influence
project performance. The investment in time and resources to find improvements is greatest
during the early stages of the project, when the project is in the planning stages. During later
project stages, as pressures to meet project schedule goals increase, the culture of the project is
less conducive to making changes in work processes.
Another opportunity for applying process improvement tools is on projects that have repetitive
processes. A housing contractor that is building several identical houses may benefit from
evaluating work processes in the first few houses to explore the opportunities available to
improve the work processes. The investment of $1,000 in a work process that saves $200 per
house is a good investment as long as the contractor is building more than five houses.
Staffing the project with the right skills, at the right place, and at the right time is an important
responsibility of the project management team. The project usually has two types of team
members: functional managers and process managers. The functional managers and team focus
on the technology of the project. On a construction project, the functional managers would
include the engineering manager and construction superintendents. On a training project, the
functional manager would include the professional trainers; on an information technology
project, the software development managers would be functional managers. The project
management team also includes project process managers. The project controls team would
include process managers who have expertise in estimating, cost tracking, planning, and
scheduling. The project manager needs functional and process expertise to plan and execute a
successful project.
Because projects are temporary, the staffing plan for a project typically reflects both the long-
term goals of skilled team members needed for the project and short-term commitment that
reflects the nature of the project. Exact start and end dates for team members are often negotiated
to best meet the needs of individuals and the project. The staffing plan is also determined by the
different phases of the project. Team members needed in the early or conceptual phases of the
project are often not needed during the later phases or project closeout phases. Team members
needed during the execution phase are often not needed during the conceptual or closeout phases.
Each phase has staffing requirements, and the staffing of a complex project requires detailed
planning to have the right skills, at the right place, at the right time.
Typically a core project management team is dedicated to the project from start-up to closeout.
This core team would include members of the project management team: project manager,
project controls, project procurement, and key members of the function management or experts
in the technology of the project. Although longer projects may experience more team turnover
than shorter projects, it is important on all projects to have team members who can provide
continuity through the project phases.
Figure 1.7
The core team is dedicated to the project from start-up to closeout.
For example, on a large commercial building project, the civil engineering team that designs the
site work where the building will be constructed would make their largest contribution during the
early phases of the design. The civil engineering lead would bring on different civil engineering
specialties as they were needed. As the civil engineering work is completed and the structural
engineering is well under way, a large portion of the civil engineers would be released from the
project. The functional managers, the engineering manager, and civil engineering lead would
provide expertise during the entire length of the project, addressing technical questions that may
arise and addressing change requests.
Project team members can be assigned to the project from a number of different sources. The
organization that charters the project can assign talented managers and staff from functional units
within the organization, contract with individuals or agencies to staff positions on the project,
temporarily hire staff for the project, or use any combination of these staffing options. This
staffing approach allows the project manager to create the project organizational culture. Some
project cultures are more structured and detail oriented, and some are less structured with less
formal roles and communication requirements. The type of culture the project manager creates
depends greatly on the type of project.
Communications
Completing a complex project successfully requires teamwork, and teamwork requires good
communication among team members. If those team members work in the same building, they
can arrange regular meetings, simply stop by each other’s office space to get a quick answer, or
even discuss a project informally at other office functions. Many complex projects in today’s
global economy involve team members from widely separated locations, and the types of
meetings that work within the same building are not possible. Teams that use electronic methods
of communicating without face-to-face meetings are called virtual teams.
Communicating can be divided into two categories: synchronous and asynchronous. If all the
parties to the communication are taking part in the exchange at the same time, the
communication is synchronous. A telephone conference call is an example of synchronous
communication. When the participants are not interacting at the same time, the communication is
asynchronous. The letter a at the beginning of the word means not. Communications
technologies require a variety of compatible devices, software, and service providers, and
communication with a global virtual team can involve many different time zones. Establishing
effective communications requires a communications plan.
Project Risk
Risk exists on all projects. The role of the project management team is to understand the kinds
and levels of risks on the project and then to develop and implement plans to mitigate these risks.
Risk represents the likelihood that an event will happen during the life of the project that will
negatively affect the achievement of project goals. The type and amount of risk varies by
industry type, complexity, and phase of the project. The project risk plan will also reflect the risk
profile of the project manager and key stakeholders. People have different comfort levels with
risk, and some members of the project team will be more risk adverse than others.
The first step in developing a risk management plan involves identifying potential project risks.
Some risks are easy to identify, such as the potential for a damaging storm in the Caribbean, and
some are less obvious. Many industries or companies have risk checklists developed from past
experience. The Construction Industry Institute published a one-hundred-item risk
checklistConstruction Industry Institute Cost/Schedule Task Force, Management of Project Risks
and Uncertainties (Austin, TX: Construction Industry Institute, 1989). that provides examples
and areas of project risks. No risk checklist will include all potential risks. The value of a
checklist is the stimulation of discussion and thought about the potential risks on a project.
The project team then analyzes the identified risks and estimates the likelihood of the risks
occurring. The team then estimates the potential impact of project goals if the event does occur.
The outcome from this process is a prioritized list of estimated project risks with a value that
represents the likelihood of occurrence and the potential impact on the project.
The project team then develops a risk mitigation plan that reduces the likelihood of an event
occurring or reduces the impact on the project if the event does occur. The risk management plan
is integrated into the project execution plan, and mitigation activities are assigned to the
appropriate project team member. The likelihood that all the potential events identified in the
risk analysis would occur is extremely rare. The likelihood that one or more events will happen
is high.
Figure 1.8
A risk mitigation plan reduces the impact of an unwanted event.
The project risk plan reflects the risk profile of the project and balances the investment of the
mitigation against the benefit for the project. One of the more common risk mitigation
approaches is the use of contingency. Contingency is funds set aside by the project team to
address unforeseen events. Projects with a high-risk profile will typically have a large
contingency budget. If the team knows which activities have the highest risk, contingency can be
allocated to activities with the highest risk. When risks are less identifiable to specific activities,
contingency is identified in a separate line item. The plan includes periodic risk plan reviews
during the life of the project. The risk review evaluates the effectiveness of the current plan and
explores for possible risks not identified in earlier sessions.
Project Procurement
The procurement effort on projects varies widely and depends on the type of project. Often the
client organization will provide procurement services on less complex projects. In this case, the
project team identifies the materials, equipment, and supplies needed by the project and provides
product specifications and a detailed delivery schedule. When the procurement department of the
parent organization provides procurement services, a liaison from the project can help the
procurement team better understand the unique requirements of the project and the time-sensitive
or critical items of the project schedule.
On larger, more complex projects, personnel are dedicated to procuring and managing the
equipment, supplies, and materials needed by the project. Because of the temporary nature of
projects, equipment, supplies, and materials are procured as part of the product of the project or
for the execution of the project. For example, the bricks procured for a construction project
would be procured for the product of the project, and the mortar mixer would be equipment
procured for the execution of the project work. At the end of the project, equipment bought or
rented for the execution of the work of the project are sold, returned to rental organizations, or
disposed of some other way.
Figure 1.9
Procurement is obtaining the materials, equipment, and services needed for the project.
© Thinkstock
More complex projects will typically procure through different procurement and management
methods. Commodities are common products that are purchased based on the lowest bid.
Commodities include items like concrete for building projects, office supplies, or even lab
equipment for a research project. The second type of procurement includes products that are
specified for the project. Vendors who can produce these products bid for a contract. The
awarding of a contract can include price, ability to meet the project schedule, the fit for purpose
of the product, and other considerations important to the project. Manufacturing a furnace for a
new steel mill would be provided by a project vendor. Equipment especially designed and built
for a research project is another example. These vendors’ performances become important parts
of the project, and the project manager assigns resources to coordinate the work and schedule of
the vendor. The third procurement approach is the development of one or more partners. A
design firm that is awarded the design contract for a major part of the steel mill and a research
firm that is conducting critical subparts of the research are examples of potential project partners.
A partner contributes to and is integrated into the execution plan. Partners perform best when
they share the project vision of success and are emotionally invested in the project. The project
management team builds and implements a project procurement plan that recognizes the most
efficient and effective procurement approach to support the project schedule and goals.
K EY TAK EAWAYS
During the start-up phase, the project leader develops the project infrastructure used to
design and execute the project. A team is formed to create agreement among project
stakeholders on the goals, cost, and completion date. Plans for executing the project,
managing the schedule and quality, and controlling the budget are created.
The scope statement establishes project parameters that define what will be done.
The project schedule begins with a milestone schedule followed by a WBS and a project
diagram. The shortest path through the project diagram is the critical path, and the
difference between the completion of the critical path and the project finish date is the
float. Shortening the critical path is called crashing the project.
Cost estimating begins with a conceptual or ballpark estimate that is followed by a ROM
estimate. A project budget is determined from the cost of the tasks in the WBS. Costs are
monitored during the project and estimates updated if the costs vary from expectations.
Project quality begins with the specifications of materials and labor. A quality plan
creates a process for assuring the requirements and specifications of the project are met.
Quality improvement tools can be applied to projects if the company has several similar
projects.
Team members are selected to manage functions and processes. The staffing plan assigns
people as needed. Sources of team members are company employees, contractors, new
hires, and partners.
The risk on a project reflects the number of things that can possibly happen that will have
a negative effect on the project and the probability of those events happening.
The provider of procurement management depends on the size of the project and the
organization. Commodities are purchased from the lowest bidder, while specialty items
are purchased from bids or from partners.
EXERCI SES
1. During the start-up phase, the first estimate of the cost of the project is called the
__________ or ballpark estimate.
2. Shortening the schedule to meet the project completion date is called ___________the
schedule.
3. Why would it be important to get the stakeholders in a project to actually sign the scope
statement?
4. What is the difference between a milestone schedule and a work breakdown schedule?
Areas of Knowledge
Write one or two sentences in which you describe each area of project management
knowledge—as defined by the Project Management Institute.
1. Start-up
2. Scope
3. Time
4. Cost
5. Quality
6. Team selection (human resources)
7. Communications
8. Risk
9. Procurement
1.6 Exercises
Exercises at the end of the chapter are designed to strengthen your understanding and retention
of the information recently acquired in the chapter.
ESSAY Q UESTIO NS
Write several paragraphs to provide more in-depth analysis and consideration when
answering the following questions.
1. If you were planning to change the landscaping around the location where you or a friend
lives and decided to approach it like a project, describe the start-up activities you would
use. Refer to the elements of a project start-up as described in this chapter.
2. Describe a project you have worked on where you experienced scope creep. Begin by
defining scope creep in your own words. Describe the project, how the scope creep
occurred, and the effect it had on the project cost, quality, and completion date.
DISC USS IO N
The exercises in this section are designed to promote exchange of information among
students in the classroom or in an online discussion. The exercises are more open ended,
which means that what you find might be completely different from what your classmates
find, and you can all benefit by sharing what you have learned.
1. Client satisfaction. Should the project manager go beyond the written requirements in the
project scope statement to satisfy the client? Does the answer to this question depend on
the role of the project in the organization? For example, does it matter if the organization
is a consulting firm that sells project management or if the project is done for another
department in the same organization? Form an opinion on this topic, and write a few
paragraphs on it to organize your thoughts on the subject. Be prepared to share your
thoughts with classmates. Submit the work as directed by your instructor.
2. Organizational priorities. Consider that three different organizations are planning to
construct a building for their own use. The organizations are a for-profit company, a
religious group, and a local school district. Choose three project knowledge areas, and
consider how the project might be affected in each of these areas by the different types of
organizations behind the project. Write a few paragraphs on this topic to organize your
thoughts on the subject, and be prepared to share your thoughts with classmates. Submit
the work as directed by your instructor.