“Project Management” summary — Erik W. Larson

Introduction

You face a constant flood of temporary endeavors designed to deliver unique products, services, or results under tight constraints. Traditional management routines fail when you must coordinate cross-functional teams, navigate shifting stakeholder demands, and deliver outcomes on fixed schedules and budgets.

Successful project management requires balancing formal technical scheduling tools with the sociocultural art of leadership and team dynamics.

Erik W. Larson presents a comprehensive framework spanning four distinct phases of the project lifecycle. You will learn how to align projects with corporate strategy, define rigorous scopes, build dependable schedules, manage uncertainty, lead diverse teams, and monitor performance.

You can answer critical questions as you build your projects:

How do you select the right projects and define an achievable scope?
What methods ensure accurate time and cost estimates?
How do you protect schedules from resource bottlenecks and risks?
Why do teams succeed or fail during execution?
How do you measure true progress using earned value?

1. Modern Project Management and Strategy

Projects bridge corporate strategy and operational execution, requiring structured portfolio selection models and socio-technical balance.

A project is a temporary endeavor undertaken to create a unique product, service, or result, bounded by specific time, cost, and performance requirements. Unlike routine repetitive work, projects have an established objective and a defined lifespan. In the United States alone, $2.5 trillion is spent on projects each year, accounting for 25 percent of the gross national product. You must navigate projects that pass sequentially through four predictable stages of a project life cycle:

Defining stage: Define specifications, establish objectives, form teams, assign major responsibilities.
Planning stage: Develop plans for scope, schedule, beneficiaries, quality levels, and budget.
Executing stage: Produce the physical product while using time, cost, and specification measures for control.
Closing stage: Deliver the product to the customer, redeploy resources, and conduct a post-project review.

What Is a Project?

Project management requires balancing two opposing dimensions: the formal technical science and the messy sociocultural art. The technical dimension covers logical planning and scheduling tools like work breakdown structures. The sociocultural dimension involves creating a temporary social system and managing interpersonal dynamics.

A project manager named Troi spends her day balancing formal schedules and progress meetings with handling disgruntled team members, client scope changes, and internal political gossip. Agile project management employs an iterative rolling wave approach for projects with high uncertainty and unstable scopes. In 1995, American firms and agencies spent $81 billion for canceled software projects due to traditional plan-driven methods failing under high uncertainty.

Organization Strategy and Project Selection

Project management sits at the apex of strategy and operations, moving beyond mere execution to achieving business results. Intel relies on projects to create specialty chips for autos, security, cell phones, and air controls to support its differentiation strategy. The strategic management process consists of four sequential activities:

Review and define the organizational mission.
Analyze and formulate strategies.
Set objectives to achieve strategies.
Implement strategies through projects.

Implementing projects without a strong priority system creates the implementation gap, organizational politics, and resource conflicts. Only 25 percent of Fortune 500 executives believe there is a strong linkage between formulated strategies and implementation. Multi-weighted scoring models use qualitative and quantitative criteria assigned with specific weights to objectively rank project proposals. At Frontier Airlines during bankruptcy, a steering committee used a weighted scheme prioritizing safety, revenue generation, cost reduction, and customer service to cut a backlog down to under 30 projects.

2. Project Organization and Scope Definition

Choosing the right organizational structure and establishing a rigid project scope prevent scope creep and align work packages with accountability.

Project Management Structures

A full-time project manager recruits a core group of specialists who work entirely on the project, often physically separated from the parent company. This dedicated project team eliminates bureaucratic delays but can create internal strife and a we-they syndrome with the rest of the organization.

Clarence L. Kelly Johnson created the Skunk Works at Lockheed Aerospace Corporation to build the Shooting Star jet fighter in just 43 days.

Matrix management overlays a horizontal project structure onto the normal functional hierarchy, balancing technical expertise and project requirements through dual chains of command categorized as weak, balanced, or strong matrices. Choosing the right project management structure requires balancing organizational considerations like core work volume and resource availability with project-level factors such as size, novelty, and strategic importance.

Assess how important project management is to the success of the firm based on core work percentage.
Evaluate resource availability for tying up critical personnel on individual projects.
Examine project-level factors including size, strategic importance, novelty, integration needs, environmental complexity, budget constraints, and resource stability.

Defining the Project Scope

A clearly defined project scope is the foundation of project success and sets the stage for detailed planning by establishing the exact end deliverables. Research shows that 50 percent of planning problems relate to unclear definitions of scope and goals, according to a study of over 1,400 project managers in the US and Canada by Gobeli and Larson (1990). Scope creep refers to the gradual expansion of project scope over time, which frequently leads to cost overruns and delays unless managed with robust control processes.

Callaway Golf introduced the Big Bertha ERC II driver in 2000, which went beyond conventional limits and achieved a coefficient of restitution of 0.86, making it non-conforming to USGA standards and forcing engineers to redesign a conforming version.

You must define whether each criterion of cost, time, and performance is constrained, enhanced, or accepted in a priority matrix. The work breakdown structure (WBS) hierarchically subdivides project deliverables into smaller work elements, serving as the essential database for planning, scheduling, and control.

Break down the work until an accurate estimate can be made for your purposes.
Conform the WBS to how you will schedule work based on days or hours.
Avoid open-ended tasks and ensure final activities have clearly defined start/end events.
Break the work down so one individual is clearly responsible.

3. Estimating and Project Networks

Reliable bottom-up and top-down estimates combined with activity-on-node networks establish the baseline schedule and critical path.

Estimating Foundations

You must assign work package estimates to the person most familiar with the task. Use several people with relevant experience and knowledge of the task to arrive at a reasonable and realistic estimate. Base task time, cost, and resource estimates on normal conditions, efficient methods, and a normal level of resources. Select specific time units early and maintain consistent time units across all task estimates. Treat each task as independent of other tasks that might be integrated by the WBS. Work package estimates should not include allowances for contingencies. Add risk assessment to the estimate to identify time and cost risks.

Projects costing $1 billion or more frequently underdeliver on benefits and exceed maintenance costs. The new Denver airport that opened in 1995 had cost overruns of 200 percent, and the Chunnel connecting France with England was 80 percent over budget. Reference class forecasting uses outside empirical data from similar past projects to mitigate human bias and establish realistic forecasts.

Developing the Project Network

Activity-on-Node uses rectangular nodes to represent activities and arrows to indicate their logical relationships and sequence. Small project networks of 25 to 100 activities are frequently constructed collaboratively using physical 3 x 4 inches Post-it stickers on a whiteboard. Forward and backward pass calculations determine early, late, and slack activity times as well as the overall project duration. Total slack measures how much an activity can be delayed without delaying the project, whereas free slack measures delay without affecting any successor activity.

Keep the level of detail to a minimum while ensuring task durations do not exceed 5 workdays or at most 10 workdays.
Extend activity time beyond the 5- to 10-day rule only if control monitoring checkpoints for segments can establish clear percent-complete progress measures.

Controlled Demolition Inc. used meticulous risk assessment and planning to implode the 25,000-ton Seattle Kingdome while wrapping charges in chain-link fencing and geotextile fabric to protect nearby buildings. The preparations cost $9 million dollars and required drilling 1,000 holes packed with high-velocity gelatin explosives in the ribs.

4. Risk Management and Resource Scheduling

Proactive risk identification and critical-chain buffering protect project timelines from resource constraints and human behavioral traps.

Risk Management Process

A contingency plan provides a pre-selected alternative course of action to be implemented only if a foreseen risk event becomes a reality, preventing costly panic under pressure. You activate this plan only after a recognized risk occurs. It defines triggers, funding, and specific actions.

Mount Everest expeditions establish rigorous contingency plans, such as utilizing supplemental oxygen, relying on Sherpas, and setting a mandatory turnaround time of 2:00 p.m. to prevent climbers from dying during descent. At altitudes above 26,000 feet, the human mind and body quickly deteriorate in the death zone.

You must follow key practices for contingency planning:

Evaluate alternative remedies for possible foreseen events before the risk event occurs.
Determine and clearly document conditions and triggers for activating the contingency plan.
Include a cost estimate and identify the source of funding in the contingency plan.
Communicate contingency plans to all affected team members to minimize surprise and resistance.

Contingency funds and time buffers are independent reserves established to absorb unplanned costs and schedule delays caused by project uncertainties. You use contingency reserves for identified risks, while management reserves cover unidentified major unforeseen risks. Typical contingency ranges span 1 to 10 percent for similar projects and 20 to 60 percent for unique and high-technology projects.

The Defense Department canceled the ARH-70 Arapaho helicopter development project after a $300 million investment due to budget cuts and a shift toward unmanned aircraft, illustrating severe funding risks. Opportunity management applies similar tools to positive events. You can exploit, share, enhance, escalate, or accept opportunities like favorable weather or lower fuel prices.

Resource Scheduling and Critical Chain

When manual resource allocation is too complex, heuristics such as the parallel method use specific priority rules to allocate resources and minimize project delay. You prioritize activities by minimum slack, smallest duration, and lowest activity identification number.

In the EMR electronic medical reference guide design phase, a shortage of design engineers reduced the available pool to eight engineers, extending project duration from 45 to 57 workdays. You can spot these bottlenecks using resource sheet and resource usage views.

Critical-Chain Project Management addresses project delays by utilizing true 50/50 activity time estimates and strategic time buffers to protect project completion dates from human behavioral traps and resource constraints. Traditional estimates pad task durations by 30 to 40 percent, triggering Parkinson's law and student syndrome.

Spirit Aero Systems applied critical-chain management to pylon assembly, cutting overtime by 50 percent and reducing assembly cycle time by 18 percent. You replace individual safety padding with project buffers, feeder buffers, and resource buffers as shock absorbers.

5. Project Duration Compression and Leadership

Crashing network schedules requires analyzing cost slopes, while exercising influence over diverse stakeholders depends on reciprocity and trust.

Reducing Project Duration

A project cost-duration graph plots total project costs as the sum of indirect and direct costs across various durations to identify the optimum cost-time point. Indirect costs vary directly with time, decreasing as project duration is reduced. Direct costs grow at an increasing rate as normal efficient methods are replaced by costly crash methods. The optimum point occurs where incremental indirect cost savings exceed incremental direct costs incurred.

The cost slope of an activity measures the constant cost increase per unit of time when compressing an activity from its normal time to its crash time. The slope is calculated as the rise in cost divided by the run in time duration between normal and crash limits. Comparing slopes of critical activities allows managers to identify the cheapest activities to shorten first.

An activity with a normal time of 10 units costing $400 and a crash time of 5 units costing $800 yields a slope of $80 for each time unit reduced.

Activity D can be reduced from a normal time of 11 time units to a crash time of 7 time units, representing a maximum reduction of 4 time units.

Managing versus Leading

Project success depends on managing a complex network of stakeholders who do not report directly to the project manager, requiring proactive dependency management. New project managers often fall into the trap of micromanagement out of frustration, but authority does not equal influence; they must navigate a web of stakeholders including top management, functional managers, customers, vendors, and contractors.

Ask whose cooperation will be needed.
Ask whose agreement or approval will be needed.
Ask whose opposition would keep us from accomplishing the project.
Draw a map of these dependencies.
Assess significance using the power/interest matrix.
Step into their shoes and analyze differences in goals, values, pressures, working styles, and risks.

Because project managers lack direct authority over many necessary allies, they must gain cooperation by trading various organizational currencies based on the law of reciprocity. Cohen and Bradford describe influence as currencies that must be balanced over the long run. Different stakeholders value different things, grouped into task-related, position-related, inspiration-related, relationship-related, and personal-related currencies.

Project managers use their own behavior as their most powerful leadership tool, influencing team norms by walking the talk across priorities, urgency, problem solving, cooperation, performance standards, and ethics. Subordinates look to respected leaders for cues on how to respond under uncertainty. Leaders convey priorities through how they spend time and convey urgency through their own pace of action.

In 1914, Ernest Shackleton embarked on the Endurance expedition that lasted two years, leading his stranded crew by example during the Antarctic expedition by heating hot milk for the crew and taking a three-hour watch himself after a grueling journey.

Ethical behavior and trust are foundational to exercising influence effectively, functioning as a lubricant for smooth interactions and depending on both character and competence. Character focuses on personal motives and values, while competence focuses on task, interpersonal, and organizational skills. Trust cannot be sustained by character or competence alone; both are required.

81 percent of project managers report that they encounter ethical issues in their work. On October 23, 2001, David Duncan told his Enron project team to comply with new document policies, leading staff to shred over one ton of audit documents. On November 9, 2001, the day after the SEC issued a subpoena, shredding stopped after 30,000 e-mails and Enron-related computer files were erased, ultimately destroying Arthur Andersen.

6. Managing Teams and Outsourcing Work

High-performance teams achieve positive synergy through structured development, while outsourced projects require principled negotiation and partnering models.

Project groups evolve through five predictable developmental stages: forming, storming, norming, performing, and adjourning. You build high-performance teams by carefully recruiting members, running effective kick-off meetings, setting operational ground rules, and establishing team norms.

Chief diesel engineer Adam Gryglak led Project Scorpion at Ford to deliver an all-new diesel engine in under 36 months by moving off-site, encouraging a fun culture with desk snowmen and Pinewood Derby races, and beating the deadline.

To run effective project meetings, you should apply specific practices:

Start meetings on time regardless of whether everyone is present.
Prepare and distribute an agenda prior to the meeting.
Identify an adjournment time.
Periodically take time to review how effective previous meetings have been.
Solicit recommendations and implement changes.
Assign good recordkeeping.
Review the agenda before beginning, and tentatively allocate time for each item.
Prioritize issues so that adjustments can be made, given time constraints.
Encourage active participation of all members by asking questions instead of making statements.
Summarize decisions, and review assignments for the next meeting.
Prepare and distribute a summary of the meeting to appropriate people.
Recognize accomplishments and positive behavior.

Managing Project Teams

Managing virtual project teams requires deliberate strategies to establish trust and maintain effective electronic communication across distance and time zones. At IBM Global Services, Carl A. Singer utilized global time zones between Australia, Scotland, and the U.S. to create a virtual 24-hour workday, accelerating reviews using a dry-cleaning approach. High-performance teams can suffer from pathologies such as groupthink, bureaucratic bypass syndrome, and team infatuation.

Outsourcing Project Work

A comprehensive Request for Proposal is essential for soliciting qualified bids and preventing misunderstandings or legal claims between the owner and contractor. Successful firms approach outsourced project work through a partnering model built on shared goals, joint teams, and trust rather than a traditional master-slave dynamic. Ohio school construction projects used a preconstruction partnering dress rehearsal led by Project Management Consultants to align expectations and avoid disputes across $3 billion in construction. Principled negotiation replaces competitive contests with collaborative problem-solving to protect working relationships and reach win/win agreements.

7. Progress Monitoring and Earned Value Management

Controlling a project requires a four-step cycle of setting a baseline, measuring progress, comparing plan against actual, and taking corrective action.

You must manage performance periodically every one to four weeks to catch deviations early. You practice this control process through specific steps:

Setting a baseline plan.
Measuring progress and performance.
Comparing plan against actual.
Taking action.

A tracking Gantt chart combines original schedules with actual start and finish times and expected remaining durations to provide a quick overview of schedule status. You should use milestones as concrete, specific, and measurable events rather than tasks, spaced at intervals no longer than every two weeks for projects lasting several months.

Earned Value Management

Earned Value Management combines scope, schedule, and resource measurements by using the budgeted cost of work actually accomplished rather than just actual costs.

Traditional cost variance alone is inadequate because it does not measure how much work was accomplished for the money spent. You implement EVM by following strict procedural steps:

Define the work using a WBS.
Develop work and resource schedule.
Develop a time-phase budget (PV).
Collect actual costs (AC) and calculate earned value (EV) using percent complete.
Compute schedule variance (SV) and cost variance (CV) and prepare hierarchical status reports.

The percent complete rule is the heart of earned value systems, supplemented by alternative rules like 0/100 and 50/50 to reduce data collection overhead. For example, an author used expertise in EVM to help the College of Oceanography at Oregon State University secure a National Science Foundation grant to design and build research vessels.

Forecasting and Control

Performance indexes like the Cost Performance Index and Schedule Performance Index provide efficiency ratios where values below 1.00 signal poor progress.

A 1.00 index value indicates progress is exactly as planned, whereas a CPI of 0.696 showed that only 70 cents worth of work was completed for each dollar spent. Final project costs can be forecasted using expert revisions or by dividing the total baseline budget by the cumulative cost performance index. Using the digital camera project data with a baseline budget of $320,000, earned value of $160,000, and actual cost of $230,000, the projected final cost forecast reached $459,000.

Scope creep refers to minor refinements that accumulate into major scope changes, requiring a well-defined scope statement and strict change management as a defense. For example, Denver International Airport experienced $2 billion in cost overruns and 16 months of delay in its baggage handling system due to late scope changes.

You defend project baselines by applying strict management practices:

Establish a well-defined scope statement that explicitly states what the project is not.
Put clear procedures in place before the project begins for authorizing and documenting scope changes.
Document the impact of necessary scope changes on cost, time, dependencies, and responsibilities.
Quickly add scope changes to the original baseline and communicate them to all stakeholders.

8. Project Closure, Agile Methods, and International Projects

Modern project execution incorporates agile iterative frameworks, rigorous post-project audits, and cross-cultural awareness.

Project Closure and Audits

Complete project closure requires three major deliverables: operational wrap-up, a project audit, and performance evaluations. Organizations must ensure proper customer sign-off, financial settlement, resource reassignment, causal analysis retrospectives, and individual and team performance reviews.

Getting delivery acceptance from the customer
Shutting down resources and releasing to new uses
Reassigning project team members
Closing accounts and seeing that all bills are paid
Delivering the project to the customer
Creating a final report

Project audits examine broader organizational success and lessons learned, differing from routine performance status reports. Audits are conducted during or after projects by independent teams using verifiable data, focusing on constructive learning rather than prosecution.

On November 4, 1979, the U.S. Embassy in Iran was stormed and 52 Americans were taken hostage. Operation Eagle Claw in 1979 failed due to factors like improper air crew selection and lack of joint mission rehearsals, which a post-project review committee subsequently analyzed. Helicopters flew a distance of 600 miles to Desert One during the aborted mission in 1979, where 8 soldiers died.

Project maturity models measure an organization's progression in implementing industry best practices across five distinct growth levels. Organizations advance slowly through maturity stages due to organizational inertia and the necessity of mastering challenges at each sequential level.

There are 2,400 organizations reporting maturity progress to the Software Engineering Institute. The median time from Level 1 to 2 is 22 months, from Level 2 to 3 is 19 months, from Level 3 to 4 is 25 months, and from Level 4 to 5 is 13 months. The Navy Federal Credit Union established a project management office in 2014 and increased its projects closed according to plan from 55 percent in 2014 to 88 percent in 2015.

Agile PM and International Projects

The Agile Manifesto prioritizes individuals, working software, customer collaboration, and responding to change over rigid processes, comprehensive documentation, contract negotiation, and following a plan.

Published in 2001 by the Agile Alliance, the manifesto reflects a socio-technical mindset that values culture, trust, and collaboration, responding to the overly controlling nature of traditional software engineering management. You apply agile values through specific operational choices:

Individuals and interactions over processes and tools.
Working software over comprehensive documentation.
Customer collaboration over contract negotiation.
Responding to change over following a plan.

The Scrum methodology operates through three distinct roles: the product owner representing customer interests, a self-organizing cross-functional development team consisting typically of 5 to 9 people, and a Scrum master serving as a process facilitator. The product owner maintains the product backlog and prioritizes features. The development team decides how to accomplish the work collaboratively. The Scrum master acts as a coach and servant leadership figure rather than a traditional boss, protecting the team from outside interference.

American project managers often struggle abroad due to parochialism, ethnocentrism, and prioritizing technical problem-solving over relationship building and trust. Larson notes that Americans tend to view the world solely through their own perspective and want to get down to work immediately. In contrast, many foreign cultures rely on long-term personal relationships, courtship rituals, and trust derived from personal interaction before discussing business details. Arab managers may require five to eight meetings before they are even willing to discuss business details.

Culture shock is a natural psychological disorientation resulting from sensory overload and the breakdown of familiar interpretive assumptions in a foreign environment. The author outlines a four-stage culture shock cycle consisting of honeymoon, irritability and hostility, gradual adjustment, and adaptation. You typically require 3 to 6 months to overcome a culture shock low. An engineer building a waste treatment plant in Chiang Mai experienced insomnia, fatigue, and irritability before adapting to the local environment.

Conclusion