Book summary “Information Technology Project Management”: summary

Introduction

Information technology projects fail at alarming rates, often exceeding budgets, missing deadlines, and delivering software that fails to meet business needs. You face immense pressure to deliver complex technical solutions while managing shifting requirements, limited resources, and stakeholder expectations. Without a structured methodology, you risk repeating common mistakes that lead to project cancellations and wasted investments.

Mastering project management requires balancing scope, time, cost, and risk through structured knowledge areas and interpersonal leadership.

Kathy Schwalbe provides a comprehensive framework for navigating the unique challenges of technology initiatives. The book explores organizational contexts, project process groups, and ten vital knowledge areas ranging from integration and scope to quality and communications. You will learn how to apply proven tools, techniques, and governance standards to ensure project success.

Consider how you can apply these principles to your daily work:

• How do you select the right projects for your organization?
• What methods keep your schedule and budget under control?
• How can you lead development teams effectively through conflict and change?

1. Project Management Fundamentals

What is a Project

A project is a temporary endeavor with a unique purpose, distinguishing it from ongoing routine operations. You use projects to drive change and enable value creation by moving from a current state to a desired future state.

Projects use progressive elaboration, require cross-area resources, involve uncertainty, and require a primary customer or sponsor.

Anne Roberts initiated an IT collaboration project to collect project ideas from across the company.

The Triple Constraint

Project success is bounded by competing limitations known as the triple constraint: scope, time, and cost.

You must balance scope, time, and cost targets, often managing these as ranges rather than rigid numbers due to uncertainty. Failing to balance them or ignoring quality can lead to project failure.

An IT collaboration project targeted a 40- to 50-page report on 30 potential projects within one month and a budget of $45,000 to $50,000.

Project management is structured around ten core knowledge areas that represent the key competencies you must master. These ten areas cover all functional aspects required to execute a project successfully, ranging from specific tactical controls like cost and schedule to overarching integrations.

2. The Organizational Context

Projects cannot run in isolation from the broader enterprise. You must understand the internal environment to deliver successful results.

Successful project execution demands a holistic systems approach and alignment with organizational culture and governance.

A Systems View

The systems approach emerged in the 1950s to describe a holistic and analytical way to solve complex problems. You apply a systems philosophy to think about things as systems. Systems analysis helps you define scope, divide components, evaluate constraints, and examine alternative solutions. You use systems management to address business, technological, and organizational spheres.

Tom Walters attempted to implement a mandatory tablet program at his college by involving only the IT department. He ignored business and organizational impacts, which led to fierce faculty opposition.

Organizations and Governance

Organizations must be understood through four distinct frames to navigate company politics and culture successfully. The structural frame focuses on roles and responsibilities. The human resources frame balances organizational and individual needs. The political frame addresses coalitions, power, and conflict over scarce resources. The symbolic frame deals with culture, language, and meaning.

Active commitment from top management remains crucial for securing resources and enforcing cross-functional cooperation. Microsoft paid the National Football League $400 million in a deal for Surface tablets. This partnership lasted for 6 years after being renewed in 2017.

You apply best practices by following core professional guidelines:

• Reach high. Stretch. Raise standards and aspirations. Find the best of the best and then use it as inspiration for reaching full potential.
• Help everyone in your organization become a professional. Empower people to manage themselves through benchmarks and standards based on best practice exchange.
• Look everywhere. Go far afield. Think of the whole world as your laboratory for learning.

3. Project Management Process Groups

All projects and project phases must incorporate five core process groups: initiating, planning, executing, monitoring and controlling, and closing. These process groups overlap and occur at varying levels of intensity throughout the project life cycle. Initiating and closing require the least time and resources, planning requires moderate effort, and executing normally demands the most resources and time.

Projects progress through five core process groups from initiation to closing, requiring disciplined planning to prevent failure.

JWD Consulting applied these five process groups to manage the development of its intranet site project from May 2 to November 4. Senior management should perform specific pre-initiation tasks to lay the groundwork and justify a project before formally assigning a project manager. Joe Fleming, CEO of JWD Consulting, drafted the high-level scope and asked Erica Bell to build a business case before proceeding with the intranet project.

Official project initiation centers on identifying stakeholders and developing a formal project charter to authorize the work. Erica Bell identified internal staff and external client representatives Kim Phuong and Page Miller, created a stakeholder register, and had CEO Joe Fleming sign the project charter.

The Five Process Groups

You apply core professional practices across each distinct stage:

• Initiating: Define and authorize the project or phase.
• Planning: Devise and maintain a workable scheme to ensure the project meets organizational needs.
• Executing: Coordinate people and resources to carry out plans.
• Monitoring and controlling: Measure progress regularly and take corrective action.
• Closing: Formalize acceptance of the work and bring the project to an orderly end.

Project Planning

Top-performing project managers, designated as alpha project managers, spend significantly more time on planning than their peers, which reduces execution problems. Andy Crowe studied 860 project managers and discovered that alpha project managers allocated 21 percent of their time to planning compared to just 11 percent for other project managers.

4. Project Integration Management

Project integration management involves coordinating all other project management knowledge areas throughout the project life cycle to ensure successful completion.

You must take responsibility for big picture coordination among people, plans, and work. According to the PMBOK Guide, this discipline consists of seven main processes ranging from charter development to project closure. Nick Carson managed hardware and software for a next-gen DNA-sequencing instrument but focused only on technical software integration while ignoring top management communication and project integration.

Strategic Planning

Organizations should follow a structured four-stage planning process to select IT projects that align with their business strategy. You can evaluate financial projections using net present value, return on investment, and payback analysis. A weighted scoring model provides a systematic, multi-criteria process for evaluating and selecting projects based on your organizational priorities.

• Tie information technology strategy to mission and vision of organization.
• Identify key business areas.
• Document key business processes that could benefit from information technology.
• Define potential projects, scope, benefits, and constraints.
• Select information technology projects and assign resources.

Change Control

Integrated change control involves identifying, evaluating, and managing changes throughout the project life cycle by balancing project constraints.

You must establish processes to detect changes against baselines and actively manage actual changes. The Salt Lake Organizing Committee for the 2002 Olympic Winter Games turned a $400 million deficit into a $100 million surplus by separating must-have items from nice-to-have items and using an Executive Roadmap.

• Establish a formal change control system including a change control board and IT steering committee.
• Implement effective configuration management to track product characteristics.
• Define procedures for making timely decisions about smaller changes.
• Use written and oral performance reports to identify and manage changes.

5. Project Scope Management

Project scope management includes six main processes to ensure that a project encompasses all the required work and nothing more. You must coordinate these steps to ensure the project team and stakeholders share a common understanding of deliverables and processes.

Rigorous scope management and requirements definition prevent costly rework and scope creep.

Collecting Requirements

A requirements traceability matrix links requirements from their source through implementation and validation. You maintain a table that lists requirements, their attributes, and their status to ensure every requirement is addressed.

• List requirements, categories, sources, and statuses in a structured table.
• Cross-reference each requirement with related items and tests.
• Maintain linkages from requirement sources through decomposition to implementation and validation.

FoxMeyer Drug spent nearly $10 million on state-of-the-art hardware and built an $18 million robotic warehouse in 1994, but erroneous orders and expanding scope cost over $15 million in unrecovered shipments, leading to bankruptcy in August 1996. McDonald's spent $170 million on consultants and planning before terminating its overly broad intranet project in 2001.

Creating the WBS

A work breakdown structure is a deliverable-oriented grouping of project work that defines total scope and forms the foundation for schedules and costs. You create this structure using decomposition to break major project deliverables into smaller pieces.

• Subdivide project deliverables into smaller pieces using decomposition.
• Organize items using guidelines, the analogy approach, top-down approach, bottom-up approach, or mind mapping.
• Ensure a unit of work appears in only one place and is the responsibility of only one person.

Northwest Airlines successfully managed enhancement requests on its ResNet project by giving reservation agents special function keys to submit requests and dedicating three full-time programmers to handle them.

6. Project Schedule Management

Project schedule management involves six specific processes designed to ensure the timely completion of a project. You can manage schedules effectively using activity sequencing, critical path analysis, and schedule compression techniques.

Accurate schedule management relies on activity sequencing, critical path analysis, and schedule compression techniques.

• Plan schedule management by determining policies, procedures, and documentation.
• Define activities by identifying specific actions needed to produce deliverables.
• Sequence activities by documenting relationships and dependencies.
• Estimate activity durations by calculating work periods needed for individual tasks.
• Develop the schedule by analyzing sequences, durations, and requirements to create the baseline.
• Control the schedule by monitoring performance and managing changes.

Critical Path Method

The critical path method predicts total project duration by identifying the longest sequence of dependent activities with the least amount of slack. Path B-E-H-J total duration of 16 days serves as the critical path for Project X.

• Develop a network diagram based on the work breakdown structure and activity list.
• Calculate path lengths by adding individual activity durations across every network path.
• Perform forward and backward passes to compute early start, early finish, late start, late finish dates, free slack, and total slack.

Schedule Compression

Project managers can shorten project schedules using duration compression techniques such as crashing and fast tracking. Experts suggest it is extremely difficult to shorten a reasonable project schedule by more than 25 percent.

• Analyze critical path activities to identify tasks where additional resources or scope adjustments can reduce duration without excessive cost increases.
• Execute dependent tasks in parallel through fast tracking when schedule compression is required, accounting for heightened project risk.

7. Project Cost Management

IT change initiatives frequently suffer from massive cost overruns, driven by a disproportionate number of unpredictable high-impact outliers known as black swans. A large study published in Harvard Business Review examined almost 1,500 IT projects and found an average cost overrun of 27 percent. The primary danger lies in IT black swan projects, which average a 200 percent cost overrun and a 70 percent schedule overrun.

Controlling project costs requires life-cycle costing, accurate estimation types, and earned value management performance tracking.

A Harvard Business Review study analyzed projects ranging from enterprise resource planning to customer relationship management systems with an average cost of $167 million and a maximum of $33 billion. Project cost management consists of four core processes designed to keep a project within its approved budget:

• Planning cost management involves determining the policies, procedures, and documentation that will be used for planning, executing, and controlling project cost.
• Estimating costs involves developing an approximation or estimate of the costs of the resources needed to complete a project.
• Determining the budget involves allocating the overall cost estimate to individual work items to establish a baseline for measuring performance.
• Controlling costs involves controlling changes to the project budget.

Cost Estimating

Project managers utilize three core types of cost estimates across different life-cycle stages with varying degrees of accuracy. Estimators can use analogous estimating based on past projects, bottom-up estimating by rolling up work package details, parametric estimating via mathematical models, or three-point estimating incorporating optimistic and pessimistic parameters.

• Prepare a rough order of magnitude estimate very early in the project life cycle, often 3 to 5 years before project completion, with an accuracy range of -50 percent to +100 percent.
• Prepare a budgetary estimate early, 1 to 2 years out, with an accuracy range of -10 percent to +25 percent.
• Prepare a definitive estimate later in the project, less than 1 year out, with an accuracy range of -5 percent to +10 percent.
• Use analogous estimates by taking the actual cost of a previous, similar project as the basis for estimating the current project.
• Use bottom-up estimates by estimating the costs of individual work items or activities and summing them to get a project total.
• Use parametric estimating by applying project characteristics in a mathematical model to estimate costs.

Earned Value Management

Earned value management integrates scope, time, and cost data to evaluate project performance against an approved baseline. By tracking planned value, actual cost, and earned value, project managers calculate variances and performance indices to forecast final project cost and schedule outcomes.

For a web server installation planned at $10,000 for Week 1 that actually incurred $15,000 and achieved $5,000 in earned value, the cost variance is -$10,000 and the schedule variance is -$5,000.

• Calculate cost variance using the formula CV = EV - AC.
• Calculate schedule variance using the formula SV = EV - PV.
• Calculate the cost performance index using the formula CPI = EV / AC.
• Calculate the schedule performance index using the formula SPI = EV / PV.
• Calculate the estimate at completion using the formula EAC = BAC / CPI.

8. Project Quality Management

Project quality management must ensure that the project satisfies both stated specifications and unstated customer expectations. Quality is defined as conformance to requirements and fitness for use. Conformance means meeting written specifications, while fitness for use means the product can actually be used as intended. You must balance quality equally with scope, time, and cost.

A company delivered 100 computers with correct processors and memory, but left them in boxes on the dock without monitors or keyboards, rendering them unfit for use.

Quality control utilizes seven basic industrial tools to trace root causes, track performance over time, and prioritize problems.

The Seven Basic Tools of Quality include cause-and-effect diagrams, control charts, checksheets, scatter diagrams, histograms, Pareto charts, and flowcharts. These tools help identify whether a process is in control and find the vital few contributors to defects.

• Cause-and-effect diagrams: Trace complaints to root causes using brainstorming categories
• Control charts: Display process data over time to check for control limits and run rules
• Checksheets: Manually collect and tally data occurrences
• Scatter diagrams: Show relationships between two variables
• Histograms: Show frequency distributions using bar graphs
• Pareto charts: Order variables by frequency to identify vital few problems
• Flowcharts: Display the logic and flow of processes

Tools for Quality Control

Scott Daniels used a fishbone diagram and the 5 whys technique to investigate why users of an Executive Information System could not log in.

Modern quality management is built upon the philosophies of pioneers who emphasized prevention, top management commitment, and worker responsibility. Key quality leaders like Deming, Juran, Crosby, Ishikawa, Taguchi, and Feigenbaum shifted manufacturing and IT cultures away from inspection toward continuous process improvement and robust design.

Ford Motor Company and Japanese manufacturers adopted W. Edwards Deming’s 14 Points and the Plan-Do-Check-Act cycle to achieve dramatic quality improvements.

Six Sigma and Testing

Six Sigma is an operating philosophy targeting no more than 3.4 defects per million opportunities using the DMAIC improvement cycle.

Six Sigma aims to eliminate defects by driving out waste and reducing data variation through the systematic DMAIC phases. Training follows a belt system from Yellow to Master Black Belt.

• Define: Define the problem, process, and customer requirements using VOC data
• Measure: Define measures, collect data, and compute defects per opportunity
• Analyze: Scrutinize process details and verify root causes
• Improve: Generate, pilot test, and implement solutions
• Control: Track and verify stability using control charts

Motorola saved billions and achieved high quality by applying Six Sigma principles company-wide with strong executive leadership.

Software testing must occur across multiple phases of the development life cycle rather than relying solely on a final inspection. Comprehensive testing methodologies include unit testing individual components, integration testing combined modules, system testing the entire entity, and user acceptance testing for business fit. Watts S. Humphrey notes that programmers introduce about one defect for every nine or ten lines of code.

• Unit test: Test each individual component or program to ensure it is defect-free
• Integration test: Test functionally grouped components to ensure a subset works together
• System test: Test the entire system as one entity
• User acceptance test: Perform independent tests by end users for business fit

Companies like Amazon and Target suffered website crashes during peak demand due to inadequate scalability testing.

The cost of quality encompasses the expenses of conformance combined with the severe costs of nonconformance and failures. Conformance costs include prevention and appraisal, while nonconformance costs cover internal and external failures. In IT projects, failing to find defects early leads to exponentially higher costs during later phases.

• Identify prevention costs: Planning and executing error-free processes via training and quality surveys
• Identify appraisal costs: Evaluating processes and outputs through inspection and testing
• Identify internal failure costs: Correcting defects before delivery via scrap, rework, and engineering changes
• Identify external failure costs: Handling warranty claims, field service, liability suits, and lost business
• Identify measurement and test equipment costs: Capital costs of equipment used for prevention and appraisal

Tom DeMarco’s studies found that average large companies spent over 60 percent of software development efforts on maintenance and about 50 percent on testing and debugging.

9. Project Resource Management

Effective resource management involves understanding human motivation theories, managing team development, and leveling resource loads.

Project resource management involves six distinct processes covering both human and physical resources. You must execute these processes systematically throughout the project life cycle:

• Plan resource management
• Estimate activity resources
• Acquire resources
• Develop the project team
• Manage the project team
• Control resources

Motivation Theories

Project managers are more likely to succeed when they influence workers through work challenge and expertise rather than relying on authority, money, or penalties. Thamhain and Wilemon investigated 72 global project teams in 2013 and found that over-reliance on hierarchical authority, money, or punitive measures correlates with project failure.

Resource Loading and Leveling

Resource loading tracks individual resource demands over time, while resource leveling resolves overallocation conflicts by shifting tasks within their slack allowances.

Joe Franklin experienced a 300 percent work allocation in the Microsoft Project example. You should maintain a 70 to 80 percent productive work rule of thumb when planning workloads.

10. Project Communications Management

Failure to communicate is widely considered the greatest threat to the success of any project, particularly IT projects. Technical jargon further widens the gap between technical developers and business professionals.

Communications management prevents project failure through structured plans, interactive methods, and effective meeting practices.

As the number of people involved in a project increases, the complexity of communication grows exponentially through a mathematically defined number of channels. Two people create 1 communication channel, three people create 3 communication channels, and four people create 6 communication channels.

Communication Channels

Every project must include a written communications management plan to guide how project information is gathered, distributed, and controlled. You should follow specific steps to design this plan effectively:

• Identify stakeholder communications requirements.
• Define information to be communicated including format, content, and detail level.
• Specify who will receive the information and who will produce it.
• List suggested methods or technologies for conveying the information.
• Establish the frequency of communication.
• Define escalation procedures for resolving issues.
• Outline revision procedures for updating the plan.
• Provide a glossary of common terminology.

Managing Communications

Project communications rely on three broad method classifications: interactive, push, and pull communication.

• Use interactive communication via meetings, phone calls, or video conferencing for mutual understanding.
• Use push communication via reports, e-mails, faxes, and voice mails to distribute info without recipient requests.
• Use pull communication via websites, bulletin boards, e-learning, and knowledge repositories for information retrieval on demand.

Performance reporting utilizes progress reports, status reports, and forecasts to keep stakeholders informed and motivated. You can execute these reporting techniques using distinct practices:

• Prepare progress reports describing accomplishments during a set period.
• Prepare status reports describing project standing against scope, time, and cost goals at a specific point in time.
• Develop forecasts using earned value management to predict final budgets and completion dates.

10 Key Ideas

1. Project success is fundamentally bounded by the competing limitations of the triple constraint involving scope, time, and cost.
2. Successful project execution demands a holistic systems approach and alignment with organizational culture and governance.
3. Projects progress through five core process groups from initiation to closing, requiring disciplined planning to prevent failure.
4. Project integration management involves coordinating all other project management knowledge areas throughout the project life cycle to ensure successful completion.
5. Rigorous scope management and requirements definition prevent costly rework and scope creep.
6. Accurate schedule management relies on activity sequencing, critical path analysis, and schedule compression techniques.
7. Controlling project costs requires life-cycle costing, accurate estimation types, and earned value management performance tracking.
8. Quality control utilizes seven basic industrial tools to trace root causes, track performance over time, and prioritize problems, alongside Six Sigma operating philosophies targeting minimal defects.
9. Effective resource management involves understanding human motivation theories, managing team development, and leveling resource loads.
10. Communications management prevents project failure through structured plans, interactive methods, and effective management of exponential communication channels.