Chapter 1 – Modern Project Management

1. Define a project. What are five characteristics that help differentiate projects from other functions carried out in
the daily operations of the organization?
– A complex, nonroutine, one-time effort limited by time, budget, resources, and performance specifications
designed to meet customer needs.
– A project is a temporary endeavor undertaken to create a unique product, service, or result (IPM)
– The characteristics of a project help differentiate it from other endeavors of the organization. The major
characteristics of a project are as follows:
1. An established objective.
2. A defined lifespan with a beginning and an end.
3. Usually, the involvement of several departments and professionals.
4. Typically, doing something that has never been done before.
5. Specific time, cost, and performance requirements.
First, projects have a defined objective—whether it is constructing a 12-story apartment complex by January 1 or
releasing version 2.0 of a specific software package as quickly as possible. This singular purpose is often lacking in daily
organizational life in which workers perform repetitive operations each day.
Second, because there is a specified objective, projects have a defined endpoint, which is contrary to the ongoing
duties and responsibilities of traditional jobs. Instead of staying in one job, individuals often move from project to project,
working with different groups of people. For example, after helping to install a security system, an IT engineer may be
assigned to develop a database for a different client.
Third, unlike much organizational work that is segmented according to functional specialty, projects typically
require the combined efforts of a variety of specialists. Instead of working in separate offices under separate managers,
project participants, whether they be engineers, financial analysts, marketing professionals, or quality control specialists,
work together under the guidance of a project manager to complete a project.
The fourth characteristic of a project is that it is nonroutine and has some unique elements. This is not an either/or
issue but a matter of degree. Obviously, accomplishing something that has never been done before, such as building an
electric automobile orlanding two mechanical rovers on Mars, requires solving previously unsolved problems and using
breakthrough technology. On the other hand, even basic construction projects that involve established sets of routines and
procedures require some degree of customization thatmakes them unique. See Snapshot from Practice 1.3: London
Calling: Seattle Seahawks versus Oakland Raiders for an unusual change in routine.
Finally, specific time, cost, and performance requirements bind projects. Projects are evaluated according to
accomplishment, cost, and time spent. These triple constraints impose a higher degree of accountability than typically
found in most jobs. These three also highlight one of the primary functions of project management, which is balancing the
trade-offs among time, cost, and performance while ultimately satisfying the customer.

2. What are some of the key environmental forces that have changed the way projects are managed? What has
been the effect of these forces on the management of projects? (page 16-17)
In Project Management, some key environmental forces that have changed the way projects are managed include:
1. Globalization:
 Impact: Organizations and projects today are no longer confined to a single country or region; they extend to
multiple markets and cultures. This requires project managers to develop strategies for cross-national and cross-
cultural communication and collaboration, as well as adjust project plans to comply with varying legal and
cultural requirements.
 Effect: Projects are often more complex, involving teams from different countries and time zones. This
necessitates the use of online communication tools and effective remote management practices.
2. Technological Advancements:
 Impact: Technology has transformed how projects are executed and tracked. Project management software, data
analytics, simulations, and automation help accelerate and enhance the accuracy of planning, resource allocation,
and progress tracking.
 Effect: New technologies such as project management software, big data analytics, and AI improve decision-
making, reduce errors, and optimize workflows. However, this also requires project managers to continuously
update their knowledge and technological skills.
3. Customer Expectations:
 Impact: Customers have increasingly high demands for quality, delivery timelines, and value. They require
products and services to be customized, flexible, and capable of adapting quickly to changing needs.
 Effect: This has led to the adoption of methods like Agile or Scrum for project management to better respond
quickly and efficiently to changing customer requirements.
4. Regulations and Compliance:
 Impact: Legal requirements, regulatory standards, and industry compliance have become more stringent,
requiring projects to adhere closely to regulatory frameworks.
 Effect: Project management now includes comprehensive plans for quality control and legal compliance from the
early stages of the project. Projects must undergo rigorous monitoring to ensure that they meet these standards and
regulations.
5. Economic Factors:
 Impact: Economic conditions can have a significant impact on project budgets, resource allocation, and strategic
decisions throughout the project lifecycle.
 Effect: Projects need to be flexible in adjusting budgets and resources in response to economic changes, such as
inflation, fluctuating material costs, or financial crises.
6. Social and Cultural Changes:
 Impact: Social and cultural trends are changing rapidly, from the growing focus on sustainability and corporate
social responsibility (CSR) to demands for diversity and inclusion in teams.
 Effect: Project management must address cultural aspects in team dynamics and partnerships, as well as ensure
that the project aligns with modern ethical and social standards, including environmental protection and
community welfare.
Summary of Impact:
These environmental forces have made project management more flexible, requiring project managers to adapt to rapid
changes, work effectively with diverse teams, and leverage advanced technology to ensure that projects are completed on
time, within budget, and with high quality.

3. Describe the four phases of the traditional project life cycle. Which phase do you think would be the most
difficult one to complete?
Another way of illustrating the unique nature of project work is in terms of the project life cycle. The life cycle
recognizes that projects have a limited lifespan and that there are predictable changes in level of effort and focus over the
life of the project.
The project life cycle typically passes sequentially through four stages: defining, planning, executing, and closing.
The starting point begins the moment the project is given the go-ahead. Project effort starts slowly, builds to a peak, and
then declines to delivery of the project to the customer.
1. Defining stage. Specifications of the project are defined; project objectives are page 10
page 11 established; teams are formed; major responsibilities are assigned.
2. Planning stage. The level of effort increases, and plans are developed to determine whatthe project will entail,
when it will be scheduled, whom it will benefit, what quality level should be maintained, and what the budget will be.
 3. Executing stage. A major portion of the project work takes place—both physical and mental. The physical
product is produced (e.g., a bridge, a report, a software program). Time, cost, and specification measures are used for
control. Is the project on schedule, on budget, and meeting specifications? What are the forecasts of each of these
measures? What revisions/changes are necessary?
4. Closing stage. Closing includes three activities: delivering the project product to the customer, redeploying
project resources, and conducting a post-project review. Delivery of the project might include customer training and
transferring documents. Redeployment usually involves releasing project equipment/materials to other projects and
finding new assignments for team members. Post-project reviews include not only assessing performance but also
capturing lessons learned
Most difficult phase: The Execution phase can be the most difficult because it involves implementing the
detailed plans in real-world conditions, coordinating various teams, managing unexpected risks, and ensuring that project
objectives are met while adhering to time, cost, and quality constraints.

4. What kinds of projects is Agile PM best suited for and why?

Agile Project Management (Agile PM) is best suited for projects with high levels of uncertainty and evolving
requirements. Specifically, Agile PM works well for projects where:
1. Unstable or Changing Scope:
o Agile is ideal for software development or any project where end-user requirements are not fully defined
upfront and may evolve over time. Since the scope is often unclear or subject to change, Agile's iterative
and incremental approach allows teams to adapt and refine the project as it progresses.
o For example, software systems engineers, product designers, and problem-solving engineers face
such uncertainty, where project requirements often change as the work unfolds.
2. Frequent Feedback and Collaboration:
o Agile PM emphasizes active collaboration between the project team and customer representatives,
making it effective for projects where ongoing feedback is essential. The iterative cycles allow teams to
demonstrate tangible progress regularly, such as defining key requirements or solving technical problems,
and incorporate feedback into the next iteration.
o Explorers, doctors, and lawyers—where the outcomes and needs can change based on new information
—can also benefit from Agile's flexibility in responding to evolving situations.
3. Complex and Innovative Solutions:
o Agile is suited for projects that involve complex or innovative solutions, where the final outcome is not
fully known in advance and needs to be developed over time. Designers and engineers working on
innovative or exploratory projects often encounter such ambiguity, making Agile's “rolling wave”
approach of continuous development ideal.
4. Small, Self-Managing Teams:
o Agile works best in small teams (typically 4 to 8 members) where the team is self-managing and can
make decisions collectively on how work is to be done. This type of team structure is more agile and
adaptable to change, which is critical in high-uncertainty environments.
o The project manager's role in Agile is to facilitate and coach rather than direct the work, allowing the
team to take ownership and make necessary adjustments during the project.
In summary, Agile PM is best suited for projects with high uncertainty, evolving requirements, and a need for
continuous collaboration and feedback, such as software development, product design, and other creative or technical
problem-solving environments. Its iterative, flexible nature allows teams to adapt to change and deliver value
incrementally throughout the project.
5. The technical and sociocultural dimensions of project management are two sides of the same coin. Explain.
The technical and sociocultural dimensions of project management are considered two sides of the same coin because
both are essential to successfully managing a project, but they focus on different aspects of the process.
1. Technical Dimension (The "Science" of Project Management):
 This dimension is concerned with the formal, structured, and logical aspects of managing a project. It includes
activities like planning, scheduling, controlling, and ensuring that the project is completed within scope, time,
and budget constraints.
 The technical side involves the creation of detailed work breakdown structures, clear project scope
statements, and systems to track progress and monitor performance. It ensures that the project is organized,
measurable, and can be controlled systematically.
 Examples include using project management software, Gantt charts, and network diagrams to track the
progress of tasks, manage dependencies, and analyze performance against the plan. This "science" is focused on
process, control, and efficiency.
2. Sociocultural Dimension (The "Art" of Project Management):
 In contrast, the sociocultural dimension focuses on the human and social aspects of project management. It deals
with the interaction between people, the development of team culture, and the ability to motivate and manage
stakeholders effectively.
 Project managers must shape a project culture that fosters teamwork, high motivation, and the ability to
resolve conflicts and problems quickly. The sociocultural dimension requires skills in communication,
leadership, negotiation, and managing relationships among a diverse set of project stakeholders.
 It also involves managing the project’s external environment, such as customer relationships, maintaining
political support from top management, and negotiating with subcontractors or other parties involved.
Balancing Both Dimensions:
 Both dimensions are interdependent and need to be balanced for a project to succeed. The technical side ensures
the project is structured, measurable, and progressing according to plan, while the sociocultural side ensures that
the team is motivated, aligned, and capable of overcoming challenges that arise during execution.
 If a project manager focuses solely on the technical side, they may become too consumed with tools and
processes, losing sight of the need to manage people and relationships. On the other hand, focusing only on the
sociocultural side might lead to lack of control, poor planning, and inefficiencies.
 Effective project managers must be skilled in both aspects: using the science of project management to stay on
track, while also leveraging the art of managing people and fostering collaboration to adapt to changing
conditions and ensure successful outcomes.
In summary, the technical and sociocultural dimensions of project management are two sides of the same coin because a
successful project requires both: structured processes and tools (technical) as well as strong leadership and interpersonal
skills (sociocultural). Balancing both ensures the project is not only well-planned but also well-executed with the active
collaboration of all involved.
Chapter 2 – Organization strategy and Project selection
1. Describe the major components of the strategic management process. (4 activities)
Strategic management is the process of assessing “what we are” and deciding and implementing “what we
intend to be and how we are going to get there.” The major generic components of the process include the following:
a. Defining the mission of the organization
b. Analysis of the external and internal environments
c. Setting objectives
d. Formulating strategies to reach objectives
e. Implementing strategies through projects

1. Environmental analysis: Assessing the external and internal environment to understand the current situation and
opportunities.
2. Strategy formulation: Identifying the organization's mission, goals, and objectives and determining the
appropriate strategy to achieve them.
3. Strategy implementation: Putting the strategy into action by allocating resources, establishing structures, and
creating systems to support it.
4. Evaluation and control: Monitoring and assessing the strategy's performance and making adjustments as
necessary.

The four major component of the strategic management process are (1) review and define theorganizational
mission, (2) Set long-range goals and objectives, (3) Analyze and formulatestrategies to reach objectives, (4)
Implement strategies through projects

2. Explain the role projects play in the strategic management process.

Projects need to be linked with the firm's overall strategy and provides theme and focus for the firm's future
direction

Strategy is implemented primarily through projects. Successful implementation of projects means reaching the
goals of the organization and thus meeting the needs of its customers. Projects that do not contribute to the strategic plan
waste critical organization resources

Projects play a crucial role in the strategic management process as they help organizations to implement their
strategies. Projects are temporary endeavours with specific goals, resources, and timelines, which can be used to achieve
specific strategic objectives. Projects can help organizations to:
1. Translate strategies into action: Projects provide a structured way to take the strategies and plans developed
during the strategy formulation stage and turn them into reality.
2. Allocate resources effectively: Projects allow organizations to allocate personnel, money, and materials to
specific initiatives, ensuring that resources are used in a focused and efficient manner.
3. Monitor progress: Project management provides a means of tracking and measuring progress towards strategic
goals and objectives, enabling organizations to adjust their strategies and initiatives as necessary.
4. Foster innovation: Projects can also be used to test and implement new ideas and initiatives, allowing
organizations to stay ahead of their competitors and innovate within their industries.
Overall, projects are an essential tool for organizations to implement their strategies and achieve
their strategic objectives, and as such, they play a critical role in the strategic management
process
3. How are projects linked to the strategic plan?
The most important criteria for selecting a project is that the project will fit with the organization strategy.
Organization s need to maximize the use of their resources by allocating resources to projects that will contribute to the
strategic plan.
Projects are linked to the strategic plan because projects represent how a strategy is to be implemented. Since some
projects are more important than others, the best way to maximize the organization’s scarce resources is through a priority
scheme which allocates resources to a portfolio of projects which balance risk and contribute the most to the strategic
plan

Projects are linked to the strategic plan in several ways:

1. Aligning with strategic objectives: Projects should align with and contribute to achieving the organization's
strategic objectives. For example, a project aimed at improving the efficiency of a production process could be linked to a
strategic goal to increase profitability.
2. Supporting the overall strategy: Projects should support the organization's overall strategy, not just individual
objectives. For example, a project to launch a new product may support a larger strategic goal to diversify the
organization's product line.
3. Allocating resources: Resources, including personnel, budget, and equipment, are often limited, and projects
should be selected and managed in a way that supports the strategic plan. This means prioritizing projects that align with
the strategic plan and contribute to the organization's success.
4. Measuring success: Projects can be used to measure the strategic plan's success. For example, if a project aimed
at reducing costs is completed on time and within budget, this can be seen as a positive outcome and an indicator of the
strategic plan's success.
Overall, projects should be linked to the strategic plan to ensure that they are aligned with the organization's
goals and objectives, support the overall strategy and contribute to its success.

4. The portfolio of projects is typically represented by compliance, strategic, andoperations projects. What impact
can this classification have on project selection?
Strategic = support org in long run; increase rev & MS
Compliance = meet regulatory conditions to operate; must do
Operational = improve effice ncy & delivery

It can impact project selection because all these of these classifications have a specific value, and if a compliance
classified project is pushed behind a strategic compliance it may be detrimental for the company

By carefully aligning your project proposal with one classification, you may increase the chances of it being
selected. Remember, senior management typically allots budgets for each category independent of actual project selection.
Knowledge of funds available, risk portfolio, senior management bias, etc. may cause some to attempt to move their
project proposal to a different classification to improve the chances of the project being selected

Classifying projects into compliance, strategic, and operations projects can impact project selection by affecting
the prioritization and allocation of resources.
1. Compliance projects: Compliance projects are required to meet legal, regulatory, or contractual obligations.
These projects typically have a high priority and may be mandated, so they can consume significant resources and may
impact the selection of other projects.
 2. Strategic projects: Strategic projects are those that support the organization's overall strategy and objectives.
These projects often have a high priority, as they can significantlyimpact the organization's success. Organizations may
allocate more resources to strategic projects, depending on their importance to the strategic plan.
3. Operations projects: Operations projects are those that support the day-to-day functioningof the organization.
These projects are typically focused on improving efficiency and mayhave a lower priority than strategic or compliance
projects.
By classifying projects into these categories, organizations can prioritize and allocate resources effectively,
ensuring that the most important tasks are given the attention and resources they need to succeed. This classification can
also help organizations balance short-term and long-term goals and legal, regulatory, and contractual obligations.

5. Why does the priority system described in this chapter require that it be open and published? Does the process
encourage bottom-up initiation of projects? Does it discourage some projects? Why?
Without a strong priority system it can lead to problems within the organization. Having an open priority system
ensures that projects are selected based on their contribution to the organization. If it isn't open it can create 3 specific
issues:
1) Implementation Gap
2) Organization Politics
3) Resource conflicts and multitasking

An open, published priority system ensures projects are selected on the basis of their contribution to the
organization. If the priority system is not open, squeaky wheels, strong people, and key departments all get their projects
selected for the wrong reasons. Bottom-up evaluation is encouraged because every organization member canself-evaluate
their project idea against priorities – and so can everyone else in the organization. To some, this approach may look
intimidating but it rarely is in practice;however, it does discourage projects that clearly will not make positive, significant
contributions to the organization vision.

The priority system described in the chapter requires that it be open and published for several
reasons:
1. Transparency: An open and published priority system promotes transparency and fairnessin project selection
and allocation of resources. All stakeholders, including employees, customers, and partners, have visibility into the
process and can understand why specific projects are given priority.
2. Encourages bottom-up initiation of projects: An open and published priority system can encourage bottom-up
initiation of projects, as employees and other stakeholders may propose projects that align with the organization's strategic
objectives and that they believe should be given priority.
3. Discourages some projects: An open and published priority system can also prevent someprojects, as projects
that do not align with the organization's strategic objectives or are not considered a priority may not be given the resources
they need to be successful.
Overall, an open and published priority system can help organizations allocate resources effectively and make
informed decisions about projects to prioritize and pursue. Being transparent and honest can also encourage bottom-up
initiation of projects and discourage projects that need to be aligned with the organization's goals and objectives

6. Why should an organization not rely only on ROI to select projects?

Even though financials help evaluate a projects return, pure financial models fail to include projects where financial return
is impossible to measure companies need to be disciplined in saying no to potentially profitable projects outside of the
realm of their core mission maintaining core competencies need to be considered it is best to use a multiple screening
criteria to evaluate projects
Financial criteria, like ROI alone, will not ensure that selected projects contribute to the mission and strategy of a firm.
Other considerations such as developing new technology, public image, brand loyalty, ethical position, and maintaining
core competencies should be considered. Furthermore, it is difficult or next to impossible to assess ROI for many
important projects (e.g., projects to develop new technologies). While ROI is likely to be a key consideration for many
organizations, multiple screening criteria are recommended for selecting and prioritizing projects

7. Discuss the pros and cons of the checklist versus the weighted factor method of selecting projects (p44-46).
Checklist (p44):
- have flexibility
- can be used across different divisions and locations
- doesn't answer relative importance or value of a project
- doesnt let you compare with other projects

Flexible
Applies over a wide range of different types of projects, divisions, and
locations
Impossible to rigorously compare and rank project by priority
Politics, power, and manipulation of project selection is very possible

Weighted
- allows comparison and ranking of potential projects
- open system
-allows self evaluation
- power and politics are exposed
Allows comparison and ranking of potential projects
Open system
Allows for self-evaluation of proposed project
Power and politic games are exposed
Chapter 3 – Organization: Structure and Culture
1. What are the relative advantages and disadvantages of the functional, matrix, and dedicated team approaches to
managing projects?
Functional Approach:
 Advantages: The functional approach ensures that each department can focus on its specific expertise, which can
lead to efficiency and specialization. It also operates within the existing organizational hierarchy, making
coordination more straightforward.
 Disadvantages: Projects may experience delays due to coordination issues between departments. The focus on
functional areas can lead to siloed thinking, and the project may not receive the attention it needs from each
department.
Matrix Approach:
 Advantages: The matrix approach balances the needs of both functional departments and project goals, allowing
for resource sharing across multiple projects. It provides a more flexible and integrated approach to managing
projects.
 Disadvantages: The dual reporting structure (to both project and functional managers) can lead to confusion,
conflicts, and power struggles. Managing resources across multiple projects can also be challenging.
Dedicated Team Approach:
 Advantages: With a dedicated team, the project manager has more control over the project, ensuring focused
attention, clear direction, and timely completion. This structure is ideal for complex or urgent projects that require
full-time commitment.
 Disadvantages: Dedicated teams can be resource-intensive, and the project may be isolated from the rest of the
organization. It may also result in inefficiencies if resources are underutilized or if the project is relatively small.

2. What distinguishes a weak matrix from a strong matrix?

In a weak matrix, the project manager has limited authority and mainly acts as a coordinator or facilitator, relying
heavily on functional managers to make decisions and allocate resources. The project manager’s role is largely supportive,
focusing on tasks such as creating schedules and monitoring progress.
In a strong matrix, the project manager has much more authority and control, with the ability to make key
decisions regarding project scope, resources, and personnel. Functional managers play a more consultative role and may
only be involved when specialized knowledge is required. The project manager has final say over the project.

3. Under what conditions would it be advisable to use a strong matrix instead of a dedicated project team?
A strong matrix would be advisable when:
 The project requires significant input from multiple departments, and coordination across these departments is
critical.
 There is a need for ongoing communication between functional areas and the project team, but the project
manager needs more control over decision-making.
 The organization cannot afford to create fully dedicated teams for each project, but needs more authority and
control within the project management structure to maintain momentum.
A dedicated project team would be better for projects that require full-time focus, urgent completion, or the development
of highly specialized products or services that require concentrated effort from a distinct group of experts.

4. How can project management offices (PMOs) support effective project management?
Project Management Offices (PMOs) can support effective project management by:
 Standardizing project management processes and methodologies across the organization.
 Providing tools, templates, and resources to assist project teams.
  Offering guidance and support for project managers, ensuring they have the knowledge and resources to succeed.
 Monitoring and ensuring that projects align with organizational goals and deliver expected outcomes.
 Facilitating training and professional development in project management for team members.

5. Why is it important to assess the culture of an organization before deciding what project management structure
should be used to complete a project?
It is important to assess the organizational culture because culture influences how people interact, make decisions,
and approach work. If the culture promotes collaboration and flexibility, a matrix or dedicated project team structure
might be more successful. On the other hand, if the culture is more hierarchical and focused on control, a functional
approach might be more appropriate. Understanding culture helps ensure that the project management structure aligns
with organizational values, enabling smoother communication, decision-making, and project execution.

6. Other than culture, what other organizational factors should be used to determine which project management
structure should be used?
Other factors include:
 The scale and complexity of the project: Larger, more complex projects may require dedicated teams or a
matrix structure to ensure proper coordination and resource allocation.
 Resource availability: If resources are limited or need to be shared across multiple projects, a matrix system can
help optimize resource use.
 Project urgency: For urgent projects requiring focused attention, a dedicated project team may be necessary.
 Organizational goals and strategy: The project management structure should align with the overall strategic
objectives of the organization to ensure that projects support business priorities effectively.

7. What do you believe is more important for successfully completing a project—the formal project management
structure or the culture of the parent organization?
Both are important, but the culture of the parent organization can be more influential in the long-term success
of a project. A supportive and collaborative culture can help overcome the challenges posed by any project management
structure. However, the formal project management structure is also essential to ensure that projects are well-
organized, resources are allocated appropriately, and clear roles and responsibilities are established. In most cases, a
strong alignment between the project management structure and organizational culture will lead to the best results.
Chapter 4 – Defining the Project
1. WHAT ARE THE EIGHT ELEMENTS OF A TYPICAL SCOPE STATEMENT?
1. Project objective. The first step of project scope definition is to define the overall objective to meet your
customer’s need(s). For example, as a result of extensive market research a computer software company decides to
develop a program that automatically translates verbal sentences in English to Russian. The project should be completed
within three years at a cost not to exceed $1.5 million. Another example is to design and constructa portable hazardous-
waste thermal treatment system in 13 months at a cost not to exceed $13 million. The project objective answers the
questions of what, when, how much, and at times where.
2. Product scope description. This step is a detailed description of the characteristics of the product, service, or
outcome of the project. The description is progressively elaborated throughout the project. The product scope answers the
question “What end result is wanted?” For example, if the product is a cell phone, its product scope will be its screen
size, battery, processor, camera type, memory, and so on.
3. Justification. It is important that project team members and stakeholders know why management authorized
the project. What is the problem or opportunity the project is addressing? This is sometimes referred to as the business
case for the project, since it usually includes cost/benefit analysis and strategic significance. For example, on a newrelease
project, the justification may be an expected ROI of 30 percent and an enhanced reputation in the marketplace.
4. Deliverables. The next step is to define major deliverables—the expected, measurable outputs over the life of
the project. For example, deliverables in the early design phase of a project might be a list of specifications. In the second
phase deliverables might be software coding and a technical manual. The next phase might be the prototype. The final
phase might be final tests and approved software. Note: Deliverables and requirements are often used interchangeably.
5. Milestones. A milestone is a significant event in a project that occurs at a point in time. The milestone
schedule shows only major segments of work; it represents first, rough-cut estimates of time, cost, and resources for the
project. The milestone schedule is built using the deliverables as a platform to identify major segments of work and an end
date—for example, testing complete and finished by July 1 of the same year. Milestones should be natural, important
control points in the project. Milestones should be easy for all project participants to recognize.
6. Technical requirements. More frequently than not, a product or service will have technical requirements to
ensure proper performance. Technical requirements typically clarify the deliverables or define the performance
specifications. For example, a technical requirement for a personal computer might be the ability to accept 120-volt
alternating current or 240-volt direct current without any adapters or user switches. Another well-known example is the
ability of 911 emergency systems to identify the caller’s phone number and the location of the phone. Examples from
information systems projects include the speed and capacity of database systems and connectivity with alternative
systems.
7. Limits and exclusions. The limits of scope should be defined. Failure to do so can lead to false expectations
and to expending resources and time on the wrong problem. The following are examples of limits: work on-site is allowed
only between the hours of 8:00 p.m. and 5:00 a.m.; system maintenance and repair will be done only up to one month
after final inspection; and the client will be billed for additional training beyond that prescribed in the contract. Exclusions
further define the boundary of the project by stating what is not included. Examples include: data will be collected by the
client, not the contractor; a house will be built, but no landscaping or security devices added; software will be installed,
but no training given.
8. Acceptance criteria. Acceptance criteria are a set of conditions that must be met before the deliverables are
accepted. The following are examples: all tasks and milestones are complete, new service processes begin with a less than
1 percent defect rate, third-party certification is required, and customer on-site inspection is required

2. WHAT QUESTIONS DOES A PROJECT OBJECTIVE ANSWER? WHAT WOULD BE AN EXAMPLE OF A

GOOD PROJECT OBJECTIVE?
The project objective answers the questions of what, when, how much, and at times where.
 What: What is the specific goal or deliverable of the project?
 When: What is the timeline for completing the project?
  How much: What are the financial or resource constraints?
 Where (if applicable): Where will the project be implemented or delivered?
Example of a Good Project Objective
A good project objective is specific, measurable, achievable, relevant, and time-bound (SMART).
Example:
"Develop and launch an AI-powered mobile application that assists users in learning Spanish by providing real-time
speech-to-text translations and grammar corrections. The project will be completed within 18 months with a budget not
exceeding $2 million."
This objective clearly specifies:
 What: AI-powered mobile application for learning Spanish.
 When: 18 months.
 How much: $2 million.
 Where: (Implicitly for mobile users worldwide).

3. WHAT DOES IT MEAN IF THE PRIORITIES OF A PROJECT INCLUDE TIME-CONSTRAIN, SCOPE-

ACCEPT, AND COST-ENHANCE?
If the priorities of a project include Time-Constrain, Scope-Accept, and Cost-Enhance, it means:
1. Time-Constrain:
o The project must meet the set timeline. Completing the project on or before the deadline is the highest
priority.
o Delays are not acceptable, even if they result in increased costs or reduced scope.
2. Scope-Accept:
o The project’s scope (performance and features) is flexible and can be adjusted or reduced if necessary to
meet the timeline or reduce costs.
o Certain non-critical requirements or features can be deferred or removed without jeopardizing the overall
project objectives.
3. Cost-Enhance:
o The project should aim to optimize costs, but spending more is acceptable if it helps meet the constrained
timeline or improve the project's performance.
o For example, resources may be added, or faster but more expensive methods may be employed to ensure
timely delivery.

Example Scenario
Suppose a company is launching a new product for a major trade show happening in three months. The timeline (time-to-
market) is constrained because missing the event would result in significant lost opportunities. To meet the deadline, the
team is willing to:
 Accept a reduced feature set or lower performance quality in the initial release.
 Enhance costs by using overtime labor, hiring additional staff, or purchasing more expensive equipment to speed
up development.
In this scenario, the priority matrix ensures that everyone understands the trade-offs and focuses efforts on completing the
project by the set deadline, even if it means higher costs and a reduced scope.

4. WHAT KINDS OF INFORMATION ARE INCLUDED IN A WORK PACKAGE?

Each item in the WBS needs a time and cost estimate. With this information it is possible to plan, schedule, and budget the
project. The WBS also serves as a framework for tracking cost and work performance

5. WHEN WOULD IT BE APPROPRIATE TO CREATE A RESPONSIBILITY MATRIX RATHER THAN A

FULL-BLOWN WBS?
In many cases, the size and scope of the project do not warrant an elaborate WBS or OBS. One tool that is widely used by
project managers and task force leaders of small projects is the responsibility matrix (RM).
Key Differences Between Responsibility Matrix and WBS
Aspect Responsibility Matrix Work Breakdown Structure (WBS)
Purpose Clarify roles and responsibilities Break down project deliverables into tasks
Focus Who does what What needs to be done
Level of Detail Less detailed Highly detailed
Project Complexity Suitable for simpler or smaller projects Necessary for larger and more complex projects
In summary, a Responsibility Matrix is appropriate when the emphasis is on roles and collaboration, while a WBS is
better for detailed task planning and execution.

A Responsibility Matrix (e.g., RACI matrix) is appropriate when the focus is on clarifying roles and responsibilities
rather than breaking down tasks in great detail. It is typically used in smaller or less complex projects, or when there’s a
need to ensure accountability and collaboration among stakeholders.
Here are specific situations when a Responsibility Matrix is more suitable than a Work Breakdown Structure (WBS):
1. When the Project Is Small or Simple
 If the project has a limited number of tasks or deliverables, creating a full WBS might be unnecessary and time-
consuming.
 A Responsibility Matrix is sufficient to assign accountability and ensure everyone knows their roles for the
limited tasks.
Example: Organizing a small team meeting or creating a marketing flyer.

2. When the Focus Is on Clarifying Roles and Responsibilities

 If the main challenge is ensuring clarity around who is responsible for specific tasks or decisions, a Responsibility
Matrix is ideal.
 This is especially useful in cross-functional teams where confusion about roles could cause delays or conflict.
Example: A project requiring input from multiple departments, such as product development involving design,
engineering, and marketing.

3. When Stakeholder Involvement Is High

 For projects with many stakeholders, a Responsibility Matrix ensures that everyone knows their level of
involvement (Responsible, Accountable, Consulted, or Informed).
 This prevents miscommunication and streamlines decision-making processes.
Example: A project to implement a new company policy requiring buy-in from various managers.

4. When There Are Few Deliverables but Many Contributors

 If the project’s deliverables are minimal but require contributions from multiple people or teams, a Responsibility
Matrix is useful for coordinating efforts.
Example: A software upgrade where different teams handle testing, deployment, and training.
5. During the Planning Phase of Larger Projects
 In larger projects, a Responsibility Matrix can be a preliminary tool before creating a full WBS. It helps identify
key players and their roles in initial planning stages.
Example: Preparing for a product launch before breaking tasks into detailed WBS levels.

6. HOW DOES A COMMUNICATION PLAN BENEFIT THE MANAGEMENT OF PROJECTS?

A communication plan benefits the management of projects in several key ways, ensuring the smooth flow of
information and mitigating potential risks caused by miscommunication. Here’s how:

1. Enhances Coordination Among Stakeholders

 Clearly defines who needs to know what and when.
 Ensures stakeholders—such as team members, sponsors, or customers—receive relevant and timely information
to make decisions or perform tasks.
 Avoids confusion and duplication of efforts by aligning expectations.

2. Mitigates Risks and Reduces Miscommunication

 Provides a structured approach to sharing updates, changes, and critical information.
 Minimizes misunderstandings that can lead to delays, errors, or conflicts.
 Identifies and prioritizes stakeholders using tools like the Power/Interest Matrix to ensure the most critical
parties receive appropriate communication.

3. Improves Efficiency and Productivity

 Standardizes communication processes, reducing unnecessary interruptions and ad-hoc information requests.
 Allows the project team to focus on deliverables rather than answering repetitive questions.
 Automates information sharing through modern tools (e.g., SharePoint, project management software), saving
time.

4. Tracks Project Progress and Performance

 Provides regular updates on project status, milestones, and deliverables, helping stakeholders monitor progress.
 Facilitates early identification and resolution of issues, ensuring alignment with project goals.

5. Builds Trust and Accountability

 Ensures transparency by maintaining open lines of communication among all parties.
 Assigns clear responsibilities for disseminating information, fostering accountability.
 Regular updates reassure stakeholders, reducing micromanagement and interference.

6. Enables Informed Decision-Making

 Provides management and stakeholders with critical information (e.g., progress reports, gating decisions) to make
timely and informed decisions.
 Ensures data accuracy by centralizing information sources and defining collection methods.

7. Adapts to Changing Priorities

  Establishes flexible communication channels that can adapt to shifting stakeholder needs or project
circumstances.
 Allows project managers to control the flow of information effectively, even when priorities or requirements
evolve.

Example
In a project to launch a new software product:
 Without a communication plan: Team members might miss updates on scope changes, stakeholders could
receive inconsistent information, and deadlines might be delayed due to poor coordination.
 With a communication plan: Updates on changes are shared via scheduled reports, responsibilities are clear, and
stakeholders receive consistent, timely communication, reducing delays and misunderstandings.

Conclusion
A communication plan is a vital tool that fosters clarity, efficiency, and collaboration in project management. It ensures
stakeholders are informed, reduces risks, and helps the project team stay aligned with goals and objectives.
CHAP 5
1. WHY ARE ACCURATE ESTIMATES CRITICAL TO EFFECTIVE PROJECT MANAGEMENT?
Estimating is the process of forecasting or approximating the time and cost of completing project deliverables.
Estimates are needed to support good decisions.
Estimates are needed to schedule work.
Estimates are needed to determine how long the project should take and its cost.
Estimates are needed to determine whether the project is worth doing.
Estimates are needed to develop cash flow needs.
Estimates are needed to determine how well the project is progressing.
All project stakeholders prefer accurate cost and time estimates, but they also understand the inherent uncertainty in all
projects. Inaccurate estimates lead to false expectations and consumer dissatisfaction. Accuracy is improved with greater
effort, but is it worth the time and cost? Estimating costs money! Project estimating becomes a trade-off, balancing the
benefits of better accuracy against the costs for securing increased accuracy.

2. HOW DOES THE CULTURE OF AN ORGANIZATION INFLUENCE THE QUALITY OF ESTIMATES?

Organizational culture can significantly influence project estimates. In some organizations padding estimates is
tolerated and even privately encouraged. Other organizations place a premium on accuracy and strongly discourage
estimating gamesmanship. Organizations vary in the importance they attach to estimates. The prevailing belief in some
organizations is that detailed estimating takes too much time and is not worth the effort or that it’s impossible to predict
the future. Other organizations subscribe to the belief that accurate estimates are the bedrock of effective project
management. Organizational culture shapes every dimension of project management; estimating is not immune to this
influence.

3. WHAT ARE THE DIFFERENCES BETWEEN BOTTOM-UP AND TOP-DOWN ESTIMATING

APPROACHES? UNDER WHAT CONDITIONS WOULD YOU PREFER ONE OVER THE OTHER?
Top-down estimates usually are derived from someone who uses experience and/or information to determine the project
duration and total cost. However, these estimates are sometimes made by top managers who have very little knowledge of
the component activities used to complete the project.
If possible and practical, you want to push the estimating process down to the work package level for bottom-up
estimates that establish low-cost, efficient methods. This process can take place after the project has been defined in
detail. Good sense suggests project estimates should come from the people most knowledgeable about the estimate
needed. The use of several people with relevant experience with the task can improve the time and cost estimate. The
bottom-up approach at the work package level can serve as a check on cost elements in the WBS by rolling up the work
packages and associated cost accounts to major deliverables. Similarly, resource requirements can be checked. Later, the
time, resource, and cost estimates from the work packages can be consolidated into timephased networks, resource
schedules, and budgets that are used for control.

The bottom-up approach also provides the customer with an opportunity to compare the low-cost, efficient method
approach with any imposed restrictions. For example, if the project completion duration is imposed at two years and your
bottom-up analysis tells you the project will take two and one-half years, the client can now consider the trade-off of the
low-cost method versus compressing the project to two years—or in rare cases canceling the project. Similar trade-offs
can be compared for different levels of resources or increases in technical performance. The assumption is any movement
away from the low-cost, efficient method will increase costs—e.g., overtime. The preferred approach in defining the
project is to make rough top-down estimates, develop the WBS/OBS, make bottom-up estimates, develop schedules and
budgets, and reconcile differences between top-down and bottom-up estimates. These steps should be done before final
negotiation with either an internal or external customer. In conclusion, the ideal approach is for the project manager
to allow enough time for both the top-down and bottom-up estimates to be worked out so that a complete plan based on
reliable estimates can be offered to thecustomer. In this way false expectations are minimized for all stakeholders and
negotiation is reduced.

4. WHAT ARE THE MAJOR TYPES OF COSTS? WHICH COSTS ARE CONTROLLABLE BY THE PROJECT
MANAGER?
Direct costs
a. Labor
b. Materials
c. Equipment
d. Other
2. Direct project overhead costs
3. General and administrative (G&A) overhead costs
The total project cost estimate is broken down in this fashion to sharpen the control process and improve decision making.
Direct Cost
These costs are clearly chargeable to a specific work package. Direct costs can be influenced by the project manager,
project team, and individuals implementing the work package. These costs represent real cash outflows and must be paid
as the project progresses; therefore, direct costs are usually separated from overhead costs. Lower-level project rollups
frequently include only direct costs.
Direct Project Overhead Costs
Direct overhead rates more closely pinpoint which resources of the organization are being used in the project. Direct
project overhead costs can be tied to project deliverables or work packages. Examples include the salary of the project
manager and temporary rental space for the project team. Although overhead is not an immediate out-of-pocket expense, it
is real and must be covered in the long run if the firm is to remain viable. These rates are usually a ratio of the dollar value
of the resources used—e.g., direct labor, materials, equipment. For example, a direct labor burden rate of 20 percent
would add a direct overhead charge of 20 percent to the direct labor cost estimate. A direct charge rate of 50 percent for
materials would carry an additional 50 percent charge to the material cost estimate. Selective direct overhead charges
provide a more accurate project (job or work package) cost than does using a blanket overhead rate for the whole project.
General and Administrative (G&A) Overhead Costs
These represent organization costs that are not directly linked to a specific project. They are carried for the duration of the
project. Examples include organization costs across all products and projects such as advertising, accounting, and senior
management above the project level. Allocation of G&A costs varies from organization to organization. However,
G&A costs are usually allocated as a percent of total direct cost or a percent of the total of a specific direct cost such as
labor, materials, or equipment. Given the totals of direct and overhead costs for individual work packages, it is possible
to cumulate the costs for any deliverable or for the entire project. A percentage can be added for profit if you are a
contractor.

Costs Controllable by the Project Manager

1. Direct Costs
o These are the most controllable by the project manager as they involve specific activities within the
project.
o Control Measures:
Managing labor hours and ensuring productivity.
 Efficient procurement and usage of materials.
 Optimizing the use of equipment to avoid unnecessary expenses.
2. Direct Project Overhead Costs
o While less directly controllable, the project manager can influence these costs by:
Monitoring resource usage tied to the project (e.g., office supplies, temporary rentals).

 Adjusting project schedules to minimize overhead expenses.
3. General and Administrative (G&A) Overhead Costs
o These costs are not directly controllable by the project manager since they are organization-wide
expenses allocated to the project.

Summary
The major types of costs in a project include direct costs, direct project overhead costs, and general and
administrative (G&A) overhead costs. Among these, the project manager has the most control over direct costs and
some influence over direct project overhead costs but little to no control over G&A overhead costs.

5. WHY IS IT DIFFICULT TO ESTIMATE MEGA PROJECT (E.G., AIRPORT, STADIUM) COSTS AND
BENEFITS?
1. High Complexity and Scale
Mega projects are inherently large-scale and involve multiple stakeholders, complex designs, and extensive resources. The
sheer size and scope of such projects make it difficult to predict all variables involved, leading to significant uncertainty in
both cost estimation and benefit forecasting. The complexity also means that tasks and dependencies are hard to account
for in a linear way, making it more likely that unforeseen costs will arise during execution.
2. Long Time Horizons
Mega projects typically span several years or even decades. Over such long periods, the political, economic, and
technological landscapes can change significantly. These changes introduce risks, such as shifts in labor costs, material
prices, or regulatory requirements, all of which are difficult to predict accurately at the outset.
3. Hidden Interaction Costs
Mega projects often involve multiple tasks and stakeholders, and tasks are rarely completed in isolation. For example,
different teams or contractors must collaborate, and the time required for coordination and communication is often not
captured in initial estimates. As the number of people and disciplines involved increases, so too does the cost of managing
interactions and addressing disconnects between tasks.
4. Resource Shortages and Availability
Estimations are typically based on "normal conditions," but resource shortages—whether in terms of labor, equipment, or
materials—can extend timelines and escalate costs. For example, the availability of bulldozers, workers, or critical
materials may not align with the assumptions made during the planning phase, causing delays and budget overruns.
5. Unforeseen Risks and Events
The unpredictability of external events, such as accidents, design flaws, or extreme weather, complicates cost and benefit
estimations. Although risks may be identified during planning, the exact timing and impact of such events are difficult to
forecast, and they often lead to increased costs and delays.
6. Changing Project Scope and Plans
As a project progresses, the understanding of what needs to be done evolves, leading to potential changes in the project
scope. In commercial projects, the scope may change in response to new customer demands or competition. Such scope
changes are a common source of cost overruns, as the project evolves beyond initial estimates.
7. Over-Optimism and Strategic Misrepresentation
Project promoters, driven by optimism or personal, political, or economic motives, may intentionally understate costs and
overstate benefits in order to secure approval for the project. This strategic misrepresentation is particularly common in
large public works projects, where there is a tendency to downplay challenges and exaggerate the potential benefits to
gain support. The promoters may rationalize that the project would never be approved if the real costs and difficulties
were fully disclosed.
8. Difficulty in Estimating Long-Term Benefits
Estimating the long-term benefits of mega projects, such as the economic impact of a new airport or the return on
investment for a stadium, is notoriously difficult. Factors such as future demand, the competitive landscape, and the
changing nature of the surrounding area can all affect the actual benefits realized, making initial benefit projections highly
uncertain.
9. Use of Deception or Overzealousness
In many cases, the cost and benefit estimates are influenced by the promoters’ desire to secure funding or political
backing. Deception, whether intentional or not, may lead to over-optimistic projections about benefits and
underestimation of costs. The belief that something "great" needs to be built despite the known challenges often leads to
distorted estimates to avoid scaring off investors or stakeholders.
Conclusion
The difficulty in estimating the costs and benefits of mega projects stems from a combination of their complexity, long
duration, inherent uncertainties, and the human tendency to either misrepresent or overestimate aspects of the project.
These factors lead to significant gaps between initial estimates and actual outcomes, resulting in budget overruns, delays,
and underperformance of the expected benefits.

6. DEFINE A WHITE ELEPHANT IN PROJECT MANAGEMENT. PROVIDE A REAL-LIFE EXAMPLE

On some mega projects, there is a triple whammy. Not only are they over budget and under value, but the cost of
maintaining them exceeds the benefits received. These kinds of projects are called white elephants. A “white elephant”
suggests a valuable, but burdensome, possession, which its owner cannot easily dispose of and whose cost (particularly
upkeep) is out of proportion with its usefulness. The term derives from the story that the Kings of Siam (now Thailand)
would often make a present of a white elephant to courtiers who had fallen out of favor with the king. At first glance, it
was a great honor to receive such a revered beast from the king. However, the true intent was to ruin the recipient by
forcing him to absorb the costs of taking
care of the animal
1. Trade Expo Buildings in Southern China
 Description: Each city in southern China built massive, palatial Trade Expo buildings, aiming to outshine their
neighboring cities. These buildings, though grand, were used only once or twice a year.
 White Elephant Characteristics:
o Excessive investment for limited use: The cities invested heavily in these grandiose buildings, which
were intended to create an image of progress and prosperity. However, the actual usage was minimal,
leading to underutilization.
 o High maintenance costs: The cost of maintaining these buildings, including utilities, repairs, and staff
salaries, likely far exceeded any economic benefits derived from their rare use.
o Opportunity cost: Money spent on these underused structures could have been better utilized elsewhere,
like improving infrastructure with more consistent, practical benefits for the public.
2. FIFA World Cup Stadiums in South Africa (2010)
 Description: South Africa invested heavily in the construction of six new world-class stadiums for the 2010
FIFA World Cup. These stadiums were built with the expectation that they would drive economic growth, tourism,
and local development.
 White Elephant Characteristics:
o Overestimation of post-event utility: Despite the global attention and tourism generated by the event,
none of the post-World Cup revenue generated by the stadiums surpassed the cost of maintaining these
world-class structures. The stadiums have largely remained underused, highlighting a disconnect between
the initial investment and long-term sustainability.
o Excessive long-term costs: Maintenance, staffing, and operational costs for such large stadiums are high,
and their underutilization has made it challenging for South Africa to justify the costs, leaving them with
substantial ongoing financial burdens.
o Failed economic stimulus: The expected economic boost from hosting such an event did not materialize
as expected, and the stadiums became symbols of wasted resources rather than assets that could generate
sustainable economic activity.
CHAP 6
1. HOW DOES THE WBS DIFFER FROM THE PROJECT NETWORK?
The project network is the tool used for planning, scheduling, and monitoring project progress. The network is
developed from the information collected for the WBS and is a graphic flow chart of the project job plan.
The Work Breakdown Structure (WBS) and the project network differ in their purpose and scope. The WBS is
a hierarchical structure that breaks down the project into smaller, manageable work packages. It defines the deliverables
and organizes the project scope but does not include information on the sequence, timing, or dependencies of the
activities.
In contrast, the project network is a graphic flow chart that illustrates the sequence and interrelationships of the
activities required to complete the project. It shows how the work packages from the WBS should be arranged and
provides the scheduling and timing details. While the WBS answers "what" needs to be done, the project network answers
"how" and "when" the tasks should be performed.

2. HOW ARE WBS AND PROJECT NETWORKS LINKED?

Project networks are developed from the WBS. The WBS and project network are closely linked through the work
packages.
The project network is a visual flow diagram of the sequence, interrelationships, and dependencies of all the activities that
must be accomplished to complete the project. An activity is an element in the project that consumes time—for example,
work or waiting.
Work packages from the WBS are used to build the activities found in the project network. An activity can include one or
more work packages. The activities are placed in a sequence that provides for orderly completion of the project. Networks
are built using nodes (boxes) and arrows (lines).

Integrating the work packages and the network represents a point where the management process often fails in practice.
The primary explanations for this failure are that (1) different groups (people) are used to define work packages and
activities and (2) the WBS is poorly constructed and not deliverable/output oriented. Integration of the WBS and project
network is crucial to effective project management. The project manager must be careful to guarantee continuity by
having some of the same people who defined the WBS and work packages develop the network activities.

Networks provide the project schedule by identifying dependencies, sequencing, and timing of activities, which the WBS
is not designed to do. The primary inputs for developing project network plan are work packages. Remember, a work
package is defined independently of other work packages, has definite start and finish points, requires specific resources,
includes technical specifications, and has cost estimates for the package. However, dependency, sequencing, and timing of
each of these factors are not included in the work package.

A network activity can include one or more work packages

3. WHY BOTHER CREATING A WBS? WHY NOT GO STRAIGHT TO A PROJECT NETWORK AND
FORGET THE WBS?
The network is developed from the information collected for the WBS
Creating a Work Breakdown Structure (WBS) is crucial for several reasons, even though it might seem tempting to go
straight to the project network. Here are key reasons why the WBS is necessary:
1. Clarifies Project Scope: The WBS helps define and organize the project's scope by breaking it down into smaller,
manageable work packages. This ensures that nothing is overlooked and that all deliverables and tasks are clearly
defined before developing the project network.
 2. Provides a Structured Approach: The WBS establishes a clear hierarchical structure that allows for better
planning, control, and monitoring of the project. Without the WBS, it's easy to miss key components or create
confusion about the project's overall scope.
3. Identifies Deliverables: The WBS focuses on the deliverables, which are the tangible outputs of the project.
These deliverables must be defined before creating the network, as the project network will show the
dependencies and sequencing of activities related to these deliverables.
4. Prevents Overlooking Important Tasks: Without the WBS, there’s a risk of jumping straight into sequencing
and scheduling activities without fully understanding all the tasks that need to be accomplished. The WBS ensures
that all tasks and work packages are accounted for.
5. Foundation for the Project Network: The project network is built upon the work packages identified in the
WBS. The WBS serves as the foundation for defining activities, their dependencies, and their sequencing. Without
the WBS, the network may lack clarity regarding the scope and deliverables of the project.
In summary, the WBS provides a critical step in defining the project scope and breaking it down into actionable
components. This clarity and structure are essential before moving to the project network, which organizes the sequencing
and timing of tasks. Without the WBS, the project network could lack important context and details, leading to confusion
and potential risks in project execution.

4. WHY IS SLACK IMPORTANT TO THE PROJECT MANAGER?

Slack can be important to managing your project. ==> How long can the activity be delayed

Slack, also known as float, is the amount of time that a project task or activity can be delayed without affecting the
overall project schedule or the project's critical path. It is an important concept for project managers for several reasons:
1. Flexibility in Scheduling: Slack provides project managers with flexibility in scheduling activities. If delays
occur in non-critical tasks, slack allows them to adjust the schedule without affecting the project's completion
date, helping manage unforeseen issues or resource constraints.
2. Buffer Against Delays: Slack acts as a buffer, giving the project manager a cushion for potential delays or
unexpected events. Having slack built into the schedule can help prevent the entire project from being derailed
due to minor setbacks in non-critical tasks.
3. Resource Management: Slack allows project managers to manage resources more effectively. For example, if
one task has slack time, resources can be redirected to other tasks that may be critical or need more attention,
optimizing the overall project flow.
4. Focus on Critical Path: The critical path, which consists of tasks with zero slack, dictates the minimum project
duration. By identifying slack in non-critical tasks, project managers can prioritize their attention and resources on
critical tasks, ensuring that the project stays on track and meets deadlines.
5. Risk Management: Slack helps in mitigating project risks. By providing extra time for non-critical tasks, it
reduces the likelihood of disruptions affecting the project's overall timeline. This allows the project manager to
respond proactively to changes and risks.
6. Improved Decision-Making: Slack provides project managers with more information to make better decisions. If
a task is delayed, the project manager can assess whether it will impact the overall schedule or if there is enough
slack to absorb the delay, leading to more informed decisions about adjustments.
In essence, slack is important because it helps project managers manage uncertainty, reduce risks, optimize resources, and
maintain flexibility, all while ensuring that critical tasks are prioritized to meet the project’s overall goals and deadlines.

5. WHAT IS THE DIFFERENCE BETWEEN FREE SLACK AND TOTAL SLACK?

Total slack tells us the amount of time an activity can be delayed and not delay the project. Stated differently, total
slack is the amount of time an activity can exceed its early finish date without affecting the project end date or an imposed
completion date. Use of total slack must be coordinated with all participants in the activities that follow in the chain.
Free slack (FS) is unique. It is the amount of time an activity can be delayed without delaying any immediately following
(successor) activity. Or free slack is the amount of time an activity can exceed its early finish date without affecting the
early start date of any uccessor(s). Free slack can never be negative. Only activities that occur at the end of a chain of
activities, where you have a merge activity, can have free slack. Free slack occurs at the last activity in a chain of
activities.

Again, note that total slack is shared across the whole path. Alternatively if you are responsible for an activity that has free
slack when you start, you do not need to notify anyone as long as your work does not absorb all of the slack!

6. WHY ARE LAGS USED IN DEVELOPING PROJECT NETWORKS?

The use of lags has been developed to offer greater flexibility in network construction. A lag is the minimum amount of
time a dependent activity must be delayed to begin or end. The use of lags in project networks occurs primarily for two
reasons:
1. To Avoid Long Delays in Successor Activities: When activities of long duration delay the start or finish of successor
activities, the network designer normally breaks the activity into smaller activities to avoid the long delay of the successor
activity. Use of lags can avoid such delays and reduce network detail.
2. To Constrain the Start and Finish of Activities: Lags can be used to constrain the start and finish of an activity. The
most commonly used relationship extensions are start-to-start, finish-to-finish, and combinations of these two. These
relationship patterns are discussed in this section.

7. WHAT IS A HAMMOCK ACTIVITY AND WHEN IS IT USED?

hammock activity. This type of activity derives its name because it spans over a segment of a project. The
hammock activity duration is determined after the network plan is drawn.
Hammock activities are frequently used to identify the use of fixed resources or costs over a segment of the
project. Typical examples of hammock activities are inspection services, consultants, and construction management
services
A hammock activity derives its duration from the time span between other activities. For example, a special color
copy machine is needed for a segment of a tradeshow publication project. A hammock activity can be used to indicate the
need for this resource and to apply costs over this segment of the project. This hammock is linked from the start of the
first activity in the segment that uses the color copy machine to the end of the last activity that uses it. The hammock
duration is simply the difference between the EF for the last activity and the ES of the first activity. The duration is
computed after the forward pass and hence has no influence on other activity times.

Key characteristics of hammock activities:

 Resource or Cost Tracking: Hammock activities are often used to track fixed resources or costs that span a
certain period within the project. For example, they can represent the usage of consultants, inspection services, or
construction management services over a period.
 Duration Calculation: The duration of a hammock activity is calculated after performing the forward pass in the
project network. It is the difference between the Earliest Start (ES) of the first activity and the Earliest Finish
(EF) of the last activity in the segment. Since its duration is calculated after the forward pass, it does not influence
the timing of other activities in the project network.
When is a hammock activity used? Hammock activities are used when (after the network plan is drawn):
1. Tracking resources or costs that need to be applied over a specific segment of the project but don’t belong to a
single task or activity.
2. Simplifying the network by grouping related tasks under a single activity that spans multiple tasks, especially
when the timing of these activities is tied together (e.g., for equipment or resource allocation).
In summary, hammock activities are useful for managing resources or costs that span across several project activities,
providing a way to track them without complicating the network with too many individual tasks.
CHAP 7
1. Project risks can/cannot be eliminated if the project is carefully planned. Explain.

2. The chances of risk events occurring and their respective costs increasing change over the project life cycle. What is the
significance of this phenomenon to a project manager?

3. WHAT IS THE DIFFERENCE BETWEEN AVOIDING A RISK AND RETAINING A RISK?

Avoiding risk is changing the project plan to eliminate the risk or condition. Although it is impossible to
eliminate all risk events, some specific risks may be avoided before you launch the project. For example, adopting proven
technology instead of experimental technology can eliminate technical failure. Choosing an Australia supplier as opposed
to an Indonesian supplier would virtually eliminate the chance that political unrest would disrupt the supply of critical
materials. Likewise, one could eliminate the risk of choosing the wrong software by developing web applications using
both [Link] and PHP. Choosing to move a concert indoors would eliminate the threat of inclement weather.
Retaining risk occurs when a conscious decision is made to accept the risk of an event occurring. Some risks are
so large it is not feasible to consider transferring or reducing the event (e.g., an earthquake). The project owner assumes
the risk because the chance of such an event occurring is slim. In other cases risks identified in the budget reserve can
simply be absorbed if they materialize. The risk is retained by developing a contingency plan to implement if the risk
materializes. In a few cases a risk event can be ignored and a cost overrun accepted, should the risk event occur.

4. WHAT IS THE DIFFERENCE BETWEEN RISK MITIGATION AND CONTINGENCY PLANNING?

The difference between risk mitigation and contingency planning lies in how and when each strategy is applied to deal
with risks:
1. Risk Mitigation
 Proactive Action: Risk mitigation involves taking proactive measures before a risk occurs to reduce the
likelihood of the risk event happening or to minimize its impact if it does occur.
 Objective: The main goal of risk mitigation is to either reduce the probability of a risk occurring or minimize the
severity of its consequences. If successful, mitigation may eliminate the need for other responses to the risk.
 Methods Applied:
o Reducing the likelihood of risks: For example, choosing reputable suppliers, using proven technology
instead of experimental technology, or conducting tests or prototypes before full implementation.
o Reducing the impact of risks: If a risk cannot be avoided, another approach is to prepare measures that
minimize the impact when the risk does occur, such as having backup materials or equipment available.
o Example: In a bridge construction project, building additional portable cement plants near the site to
ensure a continuous supply of concrete if the main supply is interrupted is a form of risk mitigation.
 Advantages: Risk mitigation helps minimize negative effects before the risk occurs and can save time and money
for the project.
2. Contingency Planning
 Reactive Action: Contingency planning, on the other hand, involves creating a plan for what to do if a risk event
becomes a reality. It is a backup plan that is activated only when the risk event happens, to reduce the negative
impact when the risk occurs.
 Objective: The goal of contingency planning is to define the actions to take if a risk occurs, ensuring that the
project can be managed effectively and with minimal disruption. The plan is prepared in advance but is only
executed after the risk event happens.
 Methods Applied:
o Identifying specific conditions for activation: The contingency plan needs to clearly specify when it
will be triggered and what actions will be taken.
 o Example: A contingency plan for a project might include having an alternative supplier ready in case of
delays, or having a chartered plane on standby if there are transportation delays due to bad weather.
 Advantages: Contingency planning provides a clear course of action when unexpected events occur, ensuring the
project can continue without excessive delays or costs.
Key Differences
 Timing of Application:
o Risk mitigation is a proactive strategy used before the risk occurs to prevent or reduce the risk's
likelihood or impact.
o Contingency planning is a reactive strategy that is implemented only after the risk has materialized,
focusing on managing the impact of the risk event.
 Purpose and Nature:
o Risk mitigation is about prevention and preparedness to avoid or reduce the likelihood of risks
occurring.
o Contingency planning is about response and managing the consequences once the risk has already
occurred.
 Application:
o Risk mitigation focuses on taking actions such as changing designs, improving supplier relationships, or
selecting proven technology to avoid or minimize the risk before it happens.
o Contingency planning prepares alternative courses of action that will be used if the identified risks
actually occur, such as having a backup supplier or an emergency transportation plan.
Example:
1. Risk Mitigation: A construction project might choose to use high-quality materials and conduct thorough safety
checks before beginning work to reduce the risk of material failure during construction.
2. Contingency Planning: If a key material supplier faces an issue and cannot deliver on time, the contingency plan
might involve having a secondary supplier or emergency transportation in place to avoid project delays.
In conclusion, risk mitigation is a proactive method aimed at preventing or reducing the likelihood and impact of risks
before they occur, while contingency planning is a reactive approach that is implemented when the risk has already
happened, focusing on minimizing its effects.

5. EXPLAIN THE DIFFERENCE BETWEEN CONTINGENCY RESERVES AND MANAGEMENT

RESERVES.
1. Contingency Reserves
 Purpose: Contingency reserves are set up to cover identified risks that have been anticipated and are specific to
particular segments or deliverables of the project.
 Allocation: These reserves are allocated to specific work packages or segments of the project, as outlined in the
baseline budget or work breakdown structure (WBS). For example, a reserve may be allocated to "computer
coding" to cover the risk of testing revealing coding problems.
 Control: Contingency reserves are managed and controlled by the project manager and the team members
responsible for implementing the specific segment of the project. The reserves should be communicated to the
project team to ensure transparency and encourage good cost performance.
 Activation: Contingency reserves are activated only when a specific identified risk occurs. If the risk does not
materialize, the funds are removed from the contingency reserves, thus reducing the total available reserve as the
project progresses.
 Independence: Contingency reserves should be independent of the original time and cost estimates for the project
to avoid any manipulation or confusion of project resources.
2. Management Reserves
  Purpose: Management reserves are set up to cover unidentified risks, which are risks that were not anticipated
during the planning phase and apply to the entire project.
 Allocation: These reserves are applied to the total project and are established after the contingency reserves have
been identified and allocated. They are typically used for major unforeseen risks, such as a significant scope
change that was not anticipated.
 Control: Management reserves are controlled by the project manager and the project owner (either internal or
external to the project organization). The owner, typically top management, has the authority to approve the use of
these reserves.
 Activation: Management reserves are activated when a major unforeseen event occurs, and these funds are used
for risks that go beyond the scope of identified risks covered by the contingency reserves.
 Independence: Management reserves are independent of the contingency reserves and are managed separately to
cover unforeseen events or changes. These reserves are often set based on historical data and the complexity or
uniqueness of the project.
Key Differences:
 Scope of Coverage:
o Contingency reserves cover identified risks specific to project segments.
o Management reserves cover major unforeseen risks that apply to the entire project.
 Control:
o Contingency reserves are controlled by the project manager and team members.
o Management reserves are controlled by the project manager and project owner (top management).
 Allocation:
o Contingency reserves are allocated to specific work packages or deliverables.
o Management reserves are set up to cover the overall project and major unforeseen events.
In summary, contingency reserves are used to manage identified risks specific to certain parts of the project, while
management reserves are used for unforeseen risks that affect the entire project, and they are controlled by higher-level
management.

6. HOW ARE THE WORK BREAKDOWN STRUCTURE AND CHANGE CONTROL CONNECTED?
The Work Breakdown Structure (WBS) and Change Control are closely connected in the project management process,
as changes to the project often affect the structure, scope, schedule, or costs outlined in the WBS.
1. Change Control and the WBS: When a change request is approved, the WBS needs to be updated to reflect the
new scope or changes to deliverables. This ensures that any alterations to the project are documented within the
project’s scope and can be monitored in terms of time, cost, and quality.
2. Plan of Record: The WBS forms part of the plan of record, which is the current official plan for the project. The
plan of record includes the scope, budget, and schedule, and it serves as a benchmark for evaluating progress. Any
changes to the scope, as identified by the change control process, will result in an updated plan of record that
integrates the changes into the WBS and baseline schedule.
3. Impact Assessment: Change control processes assess the impact of proposed changes on the WBS, ensuring that
changes are understood in terms of their effect on project scope, schedule, and costs. This helps ensure that the
WBS remains aligned with the project’s goals after changes are made.
4. Change Tracking: Change requests are logged, tracked, and evaluated to determine how they affect the work
packages in the WBS. This ensures that any modifications are reflected in the WBS structure and performance
measures.
In summary, the WBS is the foundation for organizing the project’s work and scope. The change control process ensures
that any changes are incorporated into the WBS and that the project’s scope, schedule, and costs are accurately updated
and tracked. This connection ensures that the project remains controlled and aligned with its goals.
7. WHAT ARE THE LIKELY OUTCOMES IF A CHANGE CONTROL PROCESS IS NOT USED? WHY?
If the change control system is not integrated with the WBS and baseline, project plans
and control will soon self-destruct.
If a change control process is not used in a project, several negative outcomes are likely to occur, impacting the project’s
scope, schedule, budget, and overall success. Here’s why:
1. Scope Creep
 Without a formal change control process, unauthorized or unapproved changes can be introduced into the project.
This leads to scope creep, where the project scope expands beyond its original objectives without proper
evaluation or adjustment to the schedule or budget.
 As a result, the project might end up delivering more than originally planned, causing confusion and
misalignment with stakeholders' expectations.
2. Budget and Schedule Overruns
 Changes that are not controlled or documented properly can cause significant budget and schedule overruns.
For example, when scope changes are made without formal approval, they can lead to additional costs, missed
deadlines, and overall inefficiency.
 The project team may not be aware of the need for additional resources or time, which can result in unanticipated
expenditures and delays.
3. Inconsistent Project Deliverables
 A lack of a change control process can result in inconsistent project deliverables. If changes are implemented
without proper assessment and communication, the quality of deliverables may vary, leading to confusion about
what is expected and what is actually delivered.
 This inconsistency can reduce stakeholder satisfaction and lead to problems during project implementation or
handover.
4. Miscommunication and Misalignment
 Changes made without a structured process can lead to miscommunication and misalignment among project
stakeholders, including team members, clients, and other parties involved.
 If changes are not communicated effectively, team members may not be aware of updated requirements or
priorities, leading to confusion, duplication of effort, or incorrect work.
5. Loss of Control
 Without a change control process, project control becomes more difficult. There would be no formal mechanism
to track and approve changes, making it hard to understand the current state of the project.
 This lack of control can result in decisions being made reactively, under pressure, or based on incomplete
information, leading to costly mistakes and a less successful project outcome.
6. Difficulty in Tracking and Managing Risks
 Without a formal process for managing changes, risks associated with those changes may not be properly
identified, evaluated, or mitigated. Changes introduced without proper analysis could introduce new risks to the
project or worsen existing ones, impacting its overall success.
7. Inability to Meet Stakeholder Expectations
 If a change control process is not implemented, stakeholders may become frustrated when changes are introduced
that they were unaware of or did not approve. Stakeholder dissatisfaction can increase, as the project may not
meet their expectations in terms of scope, quality, or timelines.
 In the absence of a formal process, it becomes more challenging to maintain stakeholder trust and ensure the
project aligns with business objectives.
Conclusion:
In summary, without a change control process, projects are more likely to experience uncontrolled scope changes,
budget and schedule issues, miscommunication, and misalignment with stakeholders. These outcomes can
significantly affect the project’s success and lead to inefficiencies, delays, and dissatisfaction among all parties involved.
The change control process is crucial to managing risks, ensuring that changes are evaluated and approved appropriately,
and keeping the project on track.

8. WHAT ARE THE MAJOR DIFFERENCES BETWEEN MANAGING NEGATIVE RISKS AND MANAGING
POSITIVE RISKS (OPPORTUNITIES)?
1. Objectives
 Negative risks aim to minimize or avoid the potential adverse effects of risks on the project's scope, schedule,
and budget. The objective is to reduce the likelihood and impact of these risks.
 Positive risks, on the other hand, focus on maximizing or exploiting the potential benefits or opportunities that
may arise from uncertain events. The goal is to capitalize on opportunities to improve the project's outcomes, such
as enhancing value or achieving better-than-expected results.
2. Approach
 The approach to managing negative risks generally involves preventive actions. The goal is to identify these
risks early, evaluate their potential impact, and put measures in place to either avoid, transfer, mitigate, or reduce
them. Common strategies include:
o Avoid: Alter the project plan to eliminate the risk or condition that causes the threat.
o Mitigate: Reduce the likelihood or impact of the threat.
o Transfer: Shift the risk to a third party (e.g., through insurance or outsourcing).
o Accept: Acknowledge the risk and choose not to take action unless it occurs.
 The approach to managing positive risks (opportunities) involves enhancing or exploiting the potential benefits.
The goal is to identify opportunities early and actively take steps to maximize their positive effects on the project.
Common strategies include:
o Exploit: Ensure that the opportunity is realized and fully taken advantage of, often by changing the
project plan.
o Enhance: Increase the probability or positive impact of the opportunity.
o Share: Allocate ownership of the opportunity to a third party who can capture more value from it (e.g.,
partnerships or joint ventures).
o Accept: Acknowledge the opportunity but take no immediate action, allowing it to unfold naturally.
3. Timing of Actions
 Negative risks usually require timely interventions to prevent the risk event from occurring or to minimize its
effects if it happens. Early identification and preventive action are key to managing threats.
 Positive risks often benefit from early recognition and action to seize opportunities before they dissipate. The
project manager might seek to enhance these opportunities as soon as they are identified to gain the most benefit.
5. Stakeholder Engagement
 When managing negative risks, the project manager typically works with stakeholders to avoid or reduce the
negative impacts. There may be a need for negotiation or conflict resolution when risks affect key stakeholders.
 In managing positive risks, the project manager engages with stakeholders to exploit or enhance the opportunity,
which often requires collaborative efforts to maximize the potential benefits for all parties involved.
Conclusion:
In summary, negative risks are managed by focusing on avoiding, mitigating, or transferring their negative impacts,
while positive risks are managed by exploiting, enhancing, or sharing their potential benefits. The strategies and actions
taken for each type of risk are aimed at either protecting the project from harm (negative risks) or leveraging uncertainties
to improve the project’s outcomes (positive risks).
CHAP 8
1. How does resource scheduling tie to project priority?
There are always more project proposals than there are available resources. The priority system needs to select
projects that best contribute to the organization’s objectives, within the constraints of the resources available. If all
projects and their respective esources are computer scheduled, the feasibility and impact of adding a new project to those
in process can be quickly assessed. With this information the project priority team will add a new project only if resources
are available.

2. How does resource scheduling reduce flexibility in managing projects?

3. Present six reasons scheduling resources is an important task.

4. How can outsourcing project work alleviate the three most common problems associated with multiproject resource
scheduling?

5. Explain the risks associated with leveling resources, compressing or crashing projects, and imposed durations or “catch-
up” as the project is being implemented.

6. Why is it critical to develop a time-phased baseline?

The many systems found in the real world that use only planned funds (a constant burn rate) and actual costs can
provide false and misleading information. There is no way to be certain how much of the physical work has been
accomplished. These systems do not measure how much work was accomplished for the money spent! Hence, without
time-phasing cost to match your project schedule, it is impossible to have reliable information for control purposes
CHAP 9
1. What are five common reasons for crashing a project? P320
There are many good reasons for attempting to reduce the duration of a project.
One of the more important reasons today is time-to-market. Intense global competition and rapid technological
advances have made speed a competitive advantage. To succeed, companies have to spot new opportunities, launch
project teams, and bring new products or services to the marketplace in a flash. Perhaps in no other industry does speed
matter as much as in hightech industries.
Business survival depends not only on rapid innovation but also on adaptability. Global recession and energy
crises have stunned the business world, and the companies that survive will be those that can quickly adapt to new
challenges. This requires speedy project management! For example, the fate of the U.S. auto industry depends in part on
how quickly they shift their efforts to develop fuel-efficient, alternative forms of transportation.
Another common reason for reducing project time occurs when unforeseen delays—for example, adverse weather,
design flaws, and equipment breakdown—cause substantial delays midway in the project. Getting back on schedule
usually requires compressing the time on some of the remaining critical activities. The additional costs of getting back on
schedule need to be compared with the consequences of being late. This is especially true when time is a top priority.
Incentive contracts can make the reduction of project time rewarding—usually for both the project contractor and
the owner.
“Imposed deadlines” is another reason for accelerating project completion. Sometimes very high overhead costs
are recognized before the project begins.
Finally, there are times when it is important to reassign key equipment and/or people to new projects. Under these
circumstances, the cost of compressing the project can be compared with the opportunity costs of not releasing key
equipment or people.

2. What are the advantages and disadvantages of reducing project scope to accelerate a project? What can be done
to reduce the disadvantages? 326
Advantages:
1. Time Savings:
o Reducing scope allows the project team to focus only on the essential requirements, enabling the project
to be completed faster.
o This can help meet tight deadlines and deliver the product on time.
2. Cost Savings:
o By eliminating non-essential tasks or features, the project may require fewer resources, reducing overall
costs.
3. Increased Focus:
o Narrowing the scope allows the team to direct their efforts and resources toward high-priority objectives,
improving efficiency.
4. Flexibility:
o Provides an opportunity to reassess requirements and eliminate unnecessary complexities, potentially
improving project alignment with customer priorities.
Disadvantages:
1. Reduced Functionality:
o Removing features or components may decrease the value of the final product, potentially making it less
competitive or appealing to users.
2. Customer Dissatisfaction:
o Stakeholders or customers may feel disappointed if promised features or deliverables are removed.
3. Long-term Costs:
 oScope reduction might delay critical features or functionality, requiring additional development later,
which could increase long-term costs.
4. Reputation Impact:
o If the delivered product does not meet customer expectations, it could harm the company’s reputation.
5. Misalignment of Priorities:
o Rushed decision-making during scope reduction may lead to overlooking essential requirements or
misinterpreting customer priorities.

Reducing the Disadvantages

1. Engage Stakeholders Early:
o Hold discussions with customers or sponsors to reassess priorities and ensure that scope reduction aligns
with their expectations.
2. Prioritize Essential Features:
o Use techniques such as MoSCoW (Must-have, Should-have, Could-have, Won’t-have) analysis to clearly
define what is essential and what can be deferred.
3. Transparent Communication:
o Clearly explain the reasons for scope reduction, outlining trade-offs and how the revised scope will meet
core objectives.
4. Incremental Delivery:
o Implement a phased approach where essential features are delivered first, with additional features planned
for future updates.
5. Document Changes:
o Maintain detailed records of scope adjustments, including agreements from stakeholders, to avoid
misunderstandings later.
6. Reassess Long-term Impact:
o Evaluate whether scope reduction might harm the project's competitive position or necessitate future
rework, and plan accordingly.
7. Consider Alternative Solutions:
o Explore other ways to meet the deadline, such as increasing resources, extending hours, or leveraging
technology, before cutting scope.
By carefully managing the scope reduction process, you can minimize the disadvantages while delivering a valuable
product that aligns with customer needs and project goals.

3. Why is scheduling overtime a popular choice for getting projects back on schedule? What are the potential
problems of relying on this option? 324
Why is Scheduling Overtime a Popular Choice for Getting Projects Back on Schedule?
1. Quick Implementation:
o Scheduling overtime can be applied immediately without the need for hiring, training, or onboarding
additional resources.
2. Maintains Team Familiarity:
o By using the existing team, you avoid the communication and coordination challenges that arise when
adding new people.
3. Increased Productivity:
 o Extending work hours allows the team to achieve more output in a shorter timeframe, which is especially
beneficial when deadlines are approaching.
4. Lower Short-term Costs (for Salaried Employees):
o For salaried workers, overtime does not incur additional direct costs, making it a cost-effective solution
compared to hiring or outsourcing.
5. Fewer Distractions:
o Teams working outside regular hours often experience fewer interruptions, allowing for more focused
work.

Potential Problems of Relying on Scheduling Overtime

1. Diminishing Returns:
o Productivity declines during extended work hours due to fatigue, meaning the additional hours may not
yield proportional output.
2. Increased Costs for Hourly Workers:
o Overtime for hourly workers incurs additional expenses (e.g., time-and-a-half or double pay), raising the
project budget.
3. Employee Burnout:
o Prolonged overtime can lead to physical and mental exhaustion, reducing overall efficiency and quality of
work.
4. Higher Turnover Rates:
o Sustained overtime can lead to employee dissatisfaction, increasing the likelihood of turnover, which can
disrupt the project and increase replacement costs.
5. Negative Work-Life Balance:
o Extended hours can strain personal relationships, potentially impacting morale and long-term team
stability.
6. Quality Risks:
o Fatigued employees are more likely to make mistakes, which could lead to rework or errors that affect the
project outcome.
7. Short-term Focus:
o Over-reliance on overtime can provide a temporary fix without addressing underlying issues like poor
planning or resource allocation.

Recommendations to Mitigate the Problems

 Use Overtime Sparingly:
Limit overtime to critical phases of the project to avoid long-term negative effects.
 Rotate Work Hours:
Distribute overtime among team members to reduce individual burnout and maintain productivity.
 Monitor Productivity:
Track performance during overtime to identify diminishing returns and adjust schedules accordingly.
 Address Root Causes:
Analyze why the project is behind schedule and implement long-term solutions, such as improving planning or
resource allocation.
 Ensure Fair Compensation:
For hourly workers, budget for overtime pay to ensure fair treatment and avoid resentment.
By balancing the use of overtime with a focus on team well-being, project managers can leverage its benefits while
minimizing its downsides.

4. Identify four indirect costs you might find on a moderately complex project. Why are these costs classified as
indirect? 328
Four Indirect Costs in a Moderately Complex Project
1. Project Supervision and Management Costs:
o These include the salaries of project managers, supervisors, and other administrative personnel overseeing
the project.
o Why Indirect?
These individuals support the entire project and cannot be tied to specific tasks or work packages.
2. Office Overheads:
o Costs for office space, utilities, equipment, and supplies used by the project team.
o Why Indirect?
 These expenses support the project as a whole and are not directly attributable to any particular
activity.
3. Consulting and Legal Fees:
o Payments to external consultants or legal advisors providing guidance across various aspects of the
project.
o Why Indirect?
 Their contributions typically span multiple areas of the project, making it difficult to assign their
costs to specific activities.
4. Interest on Financing:
o Costs incurred from loans or credit used to fund the project.
o Why Indirect?
 Interest accumulates over the duration of the project and is not linked to specific tasks but rather
to the project timeline as a whole.

Why These Costs Are Classified as Indirect

Indirect costs are shared across the entire project and cannot be easily traced to specific tasks or deliverables. They
generally support the project's overall functioning rather than contributing directly to the production or completion of
individual activities. As a result, they are grouped as overhead costs and vary with the project's duration.

5. How can a cost-duration graph be used by the project manager? Explain

How a Cost-Duration Graph Can Be Used by the Project Manager
A cost-duration graph is a valuable tool that helps project managers make informed decisions about the trade-offs between
project time and cost. It combines direct and indirect costs for various project durations, enabling project managers to
identify the most cost-effective project schedule. Here's how it can be used:

1. Balancing Time and Cost

 Purpose: The graph helps project managers assess the overall project cost at different durations.
 Usage:
o Managers can identify the optimal project duration that minimizes total costs (direct + indirect).
o It shows the point where shortening the project further increases costs disproportionately.
2. Identifying Activities to Crash
 Purpose: To select critical path activities that can be shortened with minimal cost.
 Usage:
o The slope of each activity's cost-time relationship indicates the cost per time unit to crash the activity.
o Activities with lower slopes are prioritized for crashing as they are more cost-effective to shorten.

3. Decision-Making for Trade-Offs

 Purpose: To analyze trade-offs between schedule acceleration and cost increases.
 Usage:
o Managers can evaluate whether crashing the project to meet a deadline justifies the additional cost.
o It helps in scenarios like deciding between overtime, additional resources, or scope reduction to meet time
constraints.

4. Resource Allocation
 Purpose: To ensure efficient use of project resources.
 Usage:
o By understanding the cost implications of accelerating activities, managers can allocate resources to
critical tasks without exceeding the budget unnecessarily.

5. Communicating with Stakeholders

 Purpose: To provide clear, data-driven insights into project cost and schedule trade-offs.
 Usage:
o The graph helps explain the financial implications of schedule changes to stakeholders, aiding in
negotiation and decision-making.

6. Managing Indirect Costs

 Purpose: To reduce overall project costs by minimizing indirect costs like supervision and overhead.
 Usage:
o By reducing project duration, managers can save on daily indirect costs, which is reflected in the graph.

Conclusion
The cost-duration graph is a powerful tool for balancing project costs and timelines. It helps project managers identify
cost-efficient strategies for shortening schedules, make trade-offs between time and cost, and communicate effectively
with stakeholders. By understanding the relationship between time and cost, managers can deliver projects within budget
and on schedule while minimizing unnecessary expenses.

6. Reducing the project duration increases the risk of being late. Explain.
Slack reduction in a project with several near-critical paths increases the risk of being late.
Why Reducing Project Duration Increases the Risk of Being Late
Reducing project duration (also known as crashing) often increases the risk of being late due to the following factors:
1. Slack Reduction:
o When project duration is reduced, slack in non-critical activities is also minimized.
 o This makes the project schedule less flexible, meaning delays in non-critical activities can quickly turn
them into critical activities, jeopardizing the overall schedule.
2. Creation of New Critical Paths:
o Shortening activities on the current critical path can cause other near-critical paths to become critical.
o This increases the number of critical activities that must be completed on time, heightening the risk of
project delays.
3. Sensitivity of the Project Network:
o In sensitive networks with multiple near-critical paths, reducing duration makes it more likely that small
delays in any path will cause the project to miss its deadline.
4. Increased Pressure on Resources:
o Crashing often requires additional resources, overtime, or new team members, which may reduce
productivity or increase coordination challenges.
o This can lead to inefficiencies or mistakes, further increasing the likelihood of delays.
5. Potential Rework:
o Accelerated schedules may lead to errors or lower-quality work that requires rework, ultimately delaying
the project.

When to Move Toward Optimum Cost-Time

The decision to reduce project duration to the optimum cost-time point depends on the sensitivity of the project network
and the associated risks:
1. Sensitive Networks:
 Characteristics: Multiple near-critical paths and reduced slack.
 Risks:
o High risk of new critical paths forming.
o Small delays in non-critical activities can become significant.
 Recommendation:
o Only partially reduce duration, as moving too far toward the optimum cost-time increases the risk of
delays and higher total costs.
2. Insensitive Networks:
 Characteristics: A dominant critical path with no or few near-critical paths.
 Risks:
o Low risk of new critical paths forming.
o Minimal impact on slack reduction for non-critical activities.
 Recommendation:
o Aggressively reduce project duration to realize significant cost savings with minimal risk.

Summary
 Reducing project duration increases the risk of delays by compressing the schedule, reducing slack, and
potentially creating new critical paths.
 The decision to reduce duration should be guided by the sensitivity of the network:
o In sensitive networks, move cautiously and only partially toward the optimum cost-time.
o In insensitive networks, move more confidently toward the optimum cost-time to achieve cost savings
with lower risk.
  Careful judgment and analysis are required to balance the trade-offs between cost, risk, and the importance of
meeting deadlines.

7. It is possible to shorten the critical path and save money. Explain how.
CÂU HỎI TRẮC NGHIỆM
1. How many types of project management structures? 3
2. Which is (are) not a characteristic(s) of a project?
- Projects are repetitve
- Project exists overtime
3. Which is (are) a characteristic(s) of a project?
- Has an identified life span with a beginning and an ending
- Project requires specific time, cost, and performance requirements
4. Which types of project management structures address the problem of staff transition after a project completed?
- Maxtrix structure
- Functional organization
5. Which types of project management structures may consume more organization’s resources?
- Projectized organization
6. Which is (are) a project(s) among following headlines?
- Compose a new guitar piece
- Invest a 10,000m2 office building with 10 floors at 207 Giai Phong, Ha Noi
7. In a project portfolio, projects can be classified as
- Operational projects
- Compliance projects
8. Financial models used in selecting projects include?
- Payback
- NPV
9. Which types of project management structure having an advantage of flexibility?
- Maxtrix structure
- Functional organization
CHAP 6 – DEVELOPING A PROJECT SCHEDULE
Drawing AON Networks
Ex 2
 Burst activity: B
 Merge activity: E

Ex 3

 Burst activity: C
 Merge activity: G

Ex 4

 Burst activity: A, B, C
 Merge activity: D, H

Ex 5

 Burst activity: A
 Merge activity: F, G, H
AON Network Times
Ex 6

Critical path:
A–B–D–E
Take: 14 days

Ex 7

Critical path:
A–D–F–G–H

Ex 8
  Critical path: A – B – C – D – H – J – K
 Penalty: $100 (late 1 day)

Ex 9

 Take: 10 days
 3 critical paths
 The network schedule is highly sensitive because all activities are critical
 Free slack and total slack for noncritical activities are both 0

Ex 10
Critical path: A – D – G – I – J – K – L

Ex 13

Ex 14
2 critical paths:
A–B–D–E–G–J
A–B–D–F–I–J

Ex 19
Critical path: A – C – E – F
Ex 20

Critical path: A – B – D – E – F – G – H – J

Ex 21
Critical path: A – B (finish only) – C – D – F
CHAP 8 - SCHEDULING RESOURCES AND COSTS
Ex 4

Ex 5
⟹ The critical activities after adjusting: 1, 2, 4, 5, 6
⟹ The project duration now is 17 days

Ex 6
Ex 7
Ex 8

Ex 9
Ex 10
CHAP 9

Duration Activity reduced Direct cost Critical path

13 1,000 A-B-D-E-F
12 D – 1 day 1,040 A-B-C-F
Increase 40 A-B-D-E-F
11 B – 1 day 1,140 A-B-C-F
Increase 100 A-B-D-E-F
10 E – 1 day 1,240 A-B-C-F
Increase 50 A-B-D-E-F
& C – 1 day
Increase 50
⟹ không giảm tiếp C vì duration vẫn là 10
Duration Activity reduced Direct cost Critical path

16 G - 1 day 1,420 A-B-D-G-H

Increase 20

15 D - 1 day 1,460 A-B-D-G-H

Increase 40

14 B - 1 day 1,560 A-B-D-G-H

Increase 100
 Duration Activity Direct cost Indirect cost Total cost Critical path
reduced
14 1,200 700 1,900 A-C-E-G
13 E – 1 day 1,220 650 1,870 A-C-E-G
Increase 20 A-C-F-G
12 C – 1 day 1,260 600 1,860 A-C-E-G
Increase 40 A-C-F-G
Because at duration 12, all activities except activity F have reached the maximum crash time. Even when we reduce the
activity F to 3 days, the total duration stays the same. Therefore, the optimum time-cost point is 12 days with a total cost
$1,860.
Exercise 7 - 450

Duration Activity Direct cost Indirect cost Total cost Critical path
reduced
20 6,000 2,000 8,000 A-B-C-E-F-H
A-B-D-E-F-H
19 F - 1 day 6,040 1,900 7,940 A-B-C-E-F-H
increase 40 A-B-D-E-F-H
A-B-C-E-G-H
A-B-D-E-G-H
18 B - 1 day 6,090 1,800 7,890 A-B-C-E-F-H
increase 50 A-B-D-E-F-H
A-B-C-E-G-H
A-B-D-E-G-H
17 E - 1 day 6,190 1,700 7,890 A-B-C-E-F-H
increase 100 A-B-D-E-F-H
A-B-C-E-G-H
A-B-D-E-G-H
16 C - 1 day 6,590 1,600 8,190 A-B-C-E-F-H
increase 200 A-B-D-E-F-H
D - 1 day A-B-C-E-G-H
 increase 200 A-B-D-E-G-H
=> the optimum time-cost point is 17 days with total cost $7,890.

Exercise 8 - 451

Duration Activity Direct cost Indirect cost Total cost Critical path
reduced
17 2,000 1,500 3,500 A-B-D-H-I
16 D – 1 day 2,040 1,450 3,490 A-B-D-H-I
Increase 40
15 H – 1 day 2,100 1,400 3,500 A-B-D-H-I
Increase 60
⟹ the optimum time-cost point is 16 days with total cost $3,490.