Book summary “Fundamentals of project management”: summary

Introduction

You often face projects that exceed budgets, miss deadlines, and fail to deliver intended results because of a ready-fire-aim mentality. Reactive firefighting replaces discipline, leaving you stressed and your stakeholders disappointed.

Successful project management requires disciplined planning, stakeholder engagement, and structured control rather than reactive firefighting.

Joseph Heagney provides a systematic framework across seventeen chapters to guide you from initiation to closure. The book covers core methodologies including scope definition, network scheduling, risk mitigation, earned value analysis, and team leadership.

The following questions guide your journey through the text:

• How do you define project constraints and secure sponsor alignment?
• What tools help you build accurate schedules and manage risks?
• How do you measure progress and lead teams effectively?

1. Overview of Project Management

Many organizations skip adequate planning time, leading to wasted effort in fixing errors and soothing stakeholders. Data from TeamStage and Harvard Business Review indicate widespread budget overruns and project failures, though PMI Pulse of the Profession reports better outcomes for structured organizations.

A project is a unique, non-repetitive endeavor constrained by performance, cost, time, and scope targets, of which only three can be predetermined by the sponsor.

The Project Management Institute defines a project as a temporary endeavor to create a unique product, service, or result. J. M. Juran calls it a problem scheduled for solution. You must manage the four constraints known as PCTS targets. The sponsor can assign values to any three of these variables, but you must calculate and determine the remaining one.

A client company project manager realized during a conference call that his team did not agree on what the project was supposed to accomplish. After three hours of facilitated discussion, they finally finished writing a basic problem statement, proving the team originally had completely divergent views.

Project Failures and Success

TeamStage reports that 70 percent of all projects fail to deliver what was promised. Furthermore, 42 percent of organizations do not understand the importance of project management. Budget overruns remain a primary symptom of distress.

• 55 percent of project managers cite budget overruns as the reason for project failure.
• 27 percent is the average budget overrun for IT projects based on a survey published in HBR.
• 200 percent is the cost overrun for black swan IT projects.
• 70 percent is the schedule overrun for black swan IT projects.

The 2021 Pulse of the Profession report offers a different perspective on outcomes. It records a 55 percent on-time completion rate and a 62 percent within-budget rate. In total, 73 percent of projects meet their original goals and business intent.

What Is Project Management

The first rule of project management is that the people who must execute the work should actively participate in planning it. Inexperienced managers make the critical mistake of designing plans entirely by themselves. This habit results in flawed estimates and a total lack of team buy-in. Your true role is that of an enabler and leader who facilitates the process rather than a dictator.

Requiring project managers to simultaneously handle administrative management and execute technical project work inevitably causes management to fail. When torn between managerial duties and individual technical deliverables, you will always prioritize the tangible work task to prevent immediate schedule slips. Consequently, overall project management is neglected because the team cannot manage itself.

Every proper project progresses through concept, definition, planning, execution and control, and closeout phases. Before execution, your team must formalize the definition and establish a game plan. Strategy defines the overall high-level approach, tactics detail how steps are performed, and logistics ensure necessary supplies and provisions are available.

During World War II, Avondale Shipyard on the Mississippi River decided to build steel ships upside down to make welding in the keel area easier, turning them over later. This innovative strategy allowed them to build boats faster, cheaper, and with higher quality than competitors, and the upside-down construction strategy has continued to be used for seventy years.

2. Project Initiation and Planning

Proper planning is an absolute imperative because effective management and control are impossible without a pre-existing plan created with the people who execute the work.

Control is exercised by comparing current status against where you are supposed to be according to the plan so that corrective action can be taken. Believing you have no time to plan during tight deadlines is a counterintuitive trap. An engineer at a seminar was pulled out of a planning conference room by a boss who claimed they had no time for planning nonsense and needed to get the job done.

Initiation and Objectives

A project problem must be defined as a gap between the current state and the goal complicated by obstacles, rather than in terms of a solution or a person. If a problem is incorrectly defined as a solution or as people's failings, the project will implement the right solution to the wrong problem.

A sales manager incorrectly defined a sales problem as having bad salespeople who could not sell a new product, failing to realize the product or market had underlying issues. Project objectives must be specific, measurable, attainable, realistic, and time limited to clearly define the desired end results.

An objective to raise funds states: Our objective is to raise $600,000 in funds from local viewers by September 18, 2023. You can apply the SMART framework by checking if your targets meet these criteria:

• Specific
• Measurable
• Attainable
• Realistic
• Time limited

Stakeholder Management

Managing stakeholders begins early in the planning process by identifying who benefits, contributes, and is impacted by the project. Failing to include important groups results in project delays, unforced errors, and needless conflict.

Early in his career at Grumman Aerospace, the author's procurement team forgot to include Grumman's Texas office when creating a supplier performance rating system, causing a painful project delay. You must identify these groups using simple questions:

• Ask who benefits from the project deliverable.
• Ask who contributes to the project work.
• Ask who is impacted by the project deliverable.

Project managers must also actively engage key stakeholders and align their own communication level with the stakeholders' technical understanding. Geert Hofstede's 1974 study of IBM employees identified five cultural dimensions that determine behavioral indicators within a working culture.

Work Breakdown Structure

The work breakdown structure subdivides complicated tasks into smaller elements to accurately estimate time, costs, and resources without indicating sequence. A WBS portrays the scope of a project graphically and allows managers to assign responsibilities.

A WBS diagram to clean a room breaks tasks down into picking up clothes, vacuuming, washing windows, wiping walls, and dusting furniture. You should follow specific guidelines when building this structure:

• Subdivide a complicated task into smaller tasks until reaching a level that cannot be further subdivided.
• Stop breaking down work when reaching a low enough level to do an estimate of desired accuracy.
• Develop the WBS before working out the schedule without trying to identify task sequence.

Project estimates must account for human productivity realities and historical data, avoiding the trap where ballpark estimates become rigid targets. Parkinson's Law states that work expands to fill the time allowed. Furthermore, humans are not 100 percent productive, requiring adjustments for project loss, reworks, and labor overhead.

Karen gave her boss a quick ballpark estimate for a job, which was later treated as a firm target despite major specification changes, leading to project failure and stress. Standard calculations compare a 56-hour estimated total required hours against a standard 40-hour week.

Three-point estimates and PERT handle high uncertainty by using optimistic, pessimistic, and most likely estimates with weighted averages. When historical data are missing, PERT applies a weighting factor to the most likely estimate to account for project uncertainty and potential extreme pessimistic values.

PERT was developed in 1957 to support the Polaris missile submarine program by an operations research team from Booz Allen Hamilton, Lockheed Missile Systems Division, and the Department of the Navy. You apply this technique using these calculations:

• Produce three sets of estimates: optimistic, pessimistic, and most likely.
• Calculate the standard average by adding the three points and dividing by three.
• Calculate the PERT weighted average by multiplying the most likely estimate by 4, adding optimistic and pessimistic estimates once each, and dividing by six.

3. Risk Management and Scheduling

Scheduling requires network diagrams and Critical Path Method computations to identify interdependencies, while proactive risk management uses a structured six-step process.

You must avoid reactive management by using a formal, proactive risk plan. A photography project risk analysis utilizes a flip chart divided in half to brainstorm risks on the left and list contingencies on the right.

Follow these steps to manage risk:

• Step 1: Make a list
• Step 2: Determine the probability of risk occurrence
• Step 3: Determine the negative impact
• Step 4: Prevent or mitigate the risk
• Step 5: Consider contingencies
• Step 6: Establish the trigger point

Establishing a formal email protocol prevents communication chaos and ensures efficient information sharing among stakeholders. A project manager returning from vacation faces 500 cc emails, most of which have nothing to do with the project.

Adopt these rules for your messages:

• Send the email only to those who need to know.
• Proofread the email before sending it; use spellcheck.
• Use the subject line to set the tone of the message.
• Create an email protocol and use it.
• If you are angry . . . wait a while before sending it.
• Do not write a novel; be succinct.
• Be succinct, but include all necessary information.
• Do not use email to avoid people.
• If the information is sensitive, consider a face-to-face meeting.

Project Risk Management

Acquiring scheduling software does not make someone an instant project manager, and professional training is necessary to use complex tools effectively. You should expect to spend 2 to 3 days of classroom time to become truly proficient. Verify that your instructor possesses practical project management knowledge rather than just software skills.

Bar charts developed by Henry Gantt were the only tool for scheduling projects until 1958. While Gantt bar charts are ideal for communicating timelines to teams, network diagrams using the Critical Path Method (CPM) or Program Evaluation and Review Technique (PERT) are necessary to identify task interdependencies and schedule impacts.

Scheduling and Network Computation

To prevent back-end loading and maintain schedule integrity, no project task should be scheduled with a duration much greater than 4 to 6 weeks. A work breakdown structure can contain 2 to 20 levels.

Manual forward-pass and backward-pass network computations allow you to understand early and late start/finish dates, float, and the critical path. The sample yard project network calculation results in 165 minutes of total calculated working time.

Develop schedules according to what is logically possible before dealing with resource limitations. Examine float availability to see if tasks can be delayed until resources become available. Inspect functional variables of cost, time, and scope if float is insufficient. Determine whether to apply time-critical or resource-critical leveling in scheduling software.

Workers are never available for productive project work 100 percent of the time due to personal needs, fatigue, and delays, and multi-project assignments severely degrade productivity. Routine workstation-bound jobs have an 80 percent maximum availability percentage. This yields 6.4 hours of available work time in an 8-hour day using an 80 percent factor, while prudence recommends 6 conservative daily working hours.

Lost availability attributed to PFD (personal, fatigue, and delays) accounts for 20 percent. Knowledge workers spend 50 percent or lower on productive work, and a company time study found only 25 percent of time spent on project work. One company doubled employee productivity when it stopped having people work on multiple projects.

4. Project Control and Change Management

Project control relies on timely status data and earned value analysis to compare progress against the baseline, supported by a formal change control process.

Project managers often carry 35 million dollars in project budgets while lacking unilateral spending approval. This sends mixed messages of distrust to the team. True control means using status data to initiate corrective actions. Macro-level control is only achieved when every individual team member maintains self-control over their specific work.

You need to provide certain elements for team member self-control:

• a clear definition of what they are supposed to be doing, with the purpose stated;
• a personal plan for how to do the required work;
• skills and resources adequate to the task;
• feedback on progress that comes directly from the work itself;
• a clear definition of their authority to take corrective action when there is a deviation from the plan and it cannot be zero.

Collecting time reports weekly from memory results in fictitious data that ruins future estimating. Status data delayed by four to six weeks becomes completely useless for corrective action. Periodic process reviews conducted at milestones or every three months help teams identify performance improvements without fear of punishment.

Change Control and Earned Value

Without a method to control changes, the baseline plan becomes invalid. You must act as a gatekeeper, evaluating changes against the triple constraints triangle and revising the baseline accordingly. Sources of change typically originate from scope, schedule, or budget. Management pulling funds represents a typical budget source of change, often pulling 20 percent of the project budget.

A colleague and group program manager at American Management Association International used an approved change request form to justify a $10,000 budget increase to a steering committee without needing an aspirin. The request asked for 25 percent of a Train the Trainer course book for colorization.

You must follow a structured procedure for every request:

• enter the initial change control information into your change control log;
• determine whether the change should be processed;
• submit recommendations to management and or the customer for review and approval;
• update the project plan;
• distribute the updated plan;
• monitor the change and track progress against the revised plan.

Developed in the 1960s decade for government contractors, earned value analysis integrates cost and schedule reporting. The method compares budgeted and actual costs of scheduled and performed work. You calculate cost variance by subtracting actual cost of work performed from budgeted cost of work performed. You calculate schedule variance by subtracting budgeted cost of work scheduled from budgeted cost of work performed.

When a deviation or variance occurs, you can take only four specific actions:

• cancel the project;
• ignore the deviation;
• take corrective action to get back onto the planned progress;
• revise the plan to reflect a change in status that cannot be corrected.

5. Team Leadership and Organizational Implementation

Turning a project group into a committed team requires adapting leadership styles across development stages, resolving conflicts flexibly, and ensuring top management involvement.

Teams do not form automatically. Members must participate in planning and share a clear mission to overcome the lack of commitment often found in matrix organizations.

You must follow specific steps to organize project teams:

• Decide what must be done, using work breakdown structures, problem definitions, and other planning tools.
• Determine staffing requirements to accomplish the tasks identified in the first step.
• Recruit members for the project team.
• Complete your project plan with the participation of team members.

Every project team must address four general issues in a specific order: goals, roles and responsibilities, procedures, and relationships. Clarifying the mission and goals is always the first step. Once established, team members must understand their distinct roles, optimize their work processes, and manage interpersonal relationships.

You can guide your team through four distinct stages of team development:

• Adopt a directive style of leadership in the forming stage.
• Use an influencing or selling style of leadership at the storming stage.
• Adopt a participative style of leadership in the norming stage.
• Apply a delegative style of leadership in the performing stage.

Project Leadership

Project managers must act as agile leaders who adapt their communication and leadership styles to different stakeholders and situations rather than forcing others to adapt to them. The people factor is often the most challenging part of project management. You must perform a practical self-inventory of your behavior and drivers.

Establishing a positive culture of dissent where all titles are left at the door prevents team stagnation and ensures a healthy exchange of ideas. Overly cordial and agreeable meetings during the storming phase indicate a dysfunctional team operating in a constricted environment. You must create an environment that encourages the open exchange of ideas and opinions without the threat of reprisals.

Project leaders must choose the appropriate conflict-resolution approach based on the specific scenario rather than relying solely on their personal comfort zone. Susan Junda outlines five distinct conflict resolution approaches that you must apply flexibly:

• Avoidance: Delay the issue, withdraw from the situation, or avoid the conflict altogether.
• Accommodating: Focus on meeting the needs of the other person to the exclusion of everything else.
• Compromising: Attempt to find the middle ground where neither party gets all that it is seeking.
• Collaborating: Have both parties work together to come to a mutually beneficial win-win solution.
• Forcing/Competing: Use the my-way-or-the-highway approach when one individual forges ahead with their idea.

Project Recovery and Closure

Project closure requires strict discipline and must encompass both contractual closure and comprehensive administrative closure activities. Project managers often experience a letdown near the finish line and rush through closure. You must complete specific administrative and contractual closure activities:

• Turn over the deliverable and ensure customer sign-off.
• Create team member performance documentation and reward top performers.
• Gather and archive project records in a document repository with redundant backups.
• Release the project team and ensure proper charge-back to functional departments.
• Summarize post-completion variance data for scope, schedule, and budget.
• Close all reports including financials and forward regulatory reports to appropriate agencies.
• Thank stakeholders and identify and chart lessons learned.

Troubled projects can be saved by avoiding symptom treatments and applying the structured FADE process to focus, analyze, develop, and execute a recovery plan. When projects fail, managers often act as firefighters treating superficial symptoms rather than root causes. The FADE quality improvement model provides a disciplined structure to calculate variances, analyze data using tools like fishbone diagrams, develop solutions, and execute recovery:

• Focus: Answer baseline questions, calculate schedule variance (SV), personnel and expense cost variance (CV), and scope variance (ScV).
• Analyze: Research data using the original project plan, charter, and fishbone diagrams to identify underlying root causes.
• Develop: Convene a formal recovery meeting with stakeholders, evaluate cost-benefits, and build a recovery work breakdown structure (WBS).
• Execute: Acquire executive buy-in, implement the recovery plan using existing resources or a tiger team, and continuously monitor performance.

Project managers must be willing to make the difficult decision to terminate or punt on a troubled project that has no chance of success. You may become emotionally attached to projects, viewing cancellation as personal failure. Continuing to invest time, people, and money into an unviable project harms the organization. Terminating early functions like punting in football, limiting damage and allowing resources to be redirected toward new initiatives.

Making Project Management Work

Project management programs will be short-lived if top executives do not actively show sustained interest and involvement. Executives must change their calendars to talk about project management, sit in on planning or review meetings, ask to see project notebooks, and build the use of management tools into performance appraisals. Dr. W. Edwards Deming learned this over fifty years ago, and Tom Peters recommended in Thriving on Chaos that executives must actively demonstrate interest.

Teams and executives need appropriate project management training, and teams should begin with projects that have a high probability of success rather than tackling the most difficult job first. Project managers need a minimum of three or four days' training, team members need about two days' training, and senior managers need a brief overview. Senior managers are so busy they can usually only spare about three hours, prompting some to create a videotaped briefing cut down to one hour and fifteen minutes.

You should follow specific implementation practices:

• Pick a project that already has a pretty high probability of success for your first project after training.
• Have your trainer or consultant walk the team through the steps during the hand-holding phase.

Conclusion

Project management succeeds when you integrate planning, scheduling, risk management, and team leadership into a cohesive system. You cannot treat these elements as isolated tasks because decisions in one area immediately impact all others. Careful initiation defines your boundaries, structured planning builds the baseline, network scheduling reveals critical dependencies, and earned value tracking maintains control. Meanwhile, active risk management protects your timeline, and adaptive leadership ensures your team remains committed through every phase.

To apply these principles effectively in your daily work, follow these rules:

1. Define clear project objectives and secure stakeholder agreement on performance, cost, time, and scope before starting any work.
2. Involve the people who will execute the work in the planning process to ensure realistic estimates and genuine commitment.
3. Build a detailed Work Breakdown Structure and network diagram to identify interdependencies and the critical path.
4. Establish a formal baseline plan and use earned value analysis regularly to monitor schedule and cost variances.
5. Anticipate risks continuously, assess their impact, and maintain response plans for critical threats.
6. Adapt your leadership style to the developmental stage of your team and manage conflicts constructively to maintain high performance.

10 Key Ideas

1. A project is a unique, non-repetitive endeavor constrained by performance, cost, time, and scope targets, of which only three can be predetermined by the sponsor.
2. Proper planning is an absolute imperative because effective management and control are impossible without a pre-existing plan created with the people who execute the work.
3. The work breakdown structure subdivides complicated tasks into smaller elements to accurately estimate time, costs, and resources without indicating sequence.
4. Scheduling requires network diagrams and Critical Path Method computations to identify interdependencies, while proactive risk management uses a structured six-step process.
5. Project control relies on timely status data and earned value analysis to compare progress against the baseline, supported by a formal change control process.
6. You can guide your team through four distinct stages of team development by adopting directive, influencing, participative, and delegative styles of leadership.
7. Project leaders must choose the appropriate conflict-resolution approach based on the specific scenario rather than relying solely on their personal comfort zone.
8. Troubled projects can be saved by avoiding symptom treatments and applying the structured FADE process to focus, analyze, develop, and execute a recovery plan.
9. Project managers must be willing to make the difficult decision to terminate or punt on a troubled project that has no chance of success.
10. Project management programs will be short-lived if top executives do not actively show sustained interest and involvement.