Information Technology Project Management

If you touch IT projects—as a manager, developer, analyst, or student—this is the standard textbook for a reason. It translates abstract PMBOK frameworks into software-specific practice, with real numbers on failure rates and step-by-step tools you can apply immediately. Read it to pass certification, to lead your first project, or to stop watching budgets and schedules slip.

1. 1Chapter 1

   A project is temporary, unique, and judged on three goals at once

   Schwalbe opens by pinning down what she is even teaching about. A project, she says, is 'a temporary endeavor undertaken to create a unique product, service, or result,' and project management is 'the application of knowledge, skills, tools and techniques to project activities to meet project requirements'—both straight from the PMBOK Guide. From there she introduces the triple constraint: every project balances scope, time, and cost, usually drawn as a triangle with quality at the center. Squeeze one side and the others move. That geometry frames every chapter that follows.

   The idea

   The triple constraint is deceptively simple. People treat scope, schedule, and budget as separate dials, then act surprised when tightening one loosens another. Quality sits at the center because it absorbs the pressure from all three sides. Once you see projects this way, every status meeting becomes a question about which corner of the triangle is giving way—and what that costs in quality.

   Try this: Draw the triangle for your current project and label which constraint is currently being squeezed hardest.

2. 2Chapter 1

   Ten knowledge areas, five process groups, one messy overlap

   Picture a new project manager with the PMBOK Guide open, staring at ten knowledge areas—scope, schedule, cost, resource, communications, risk, procurement, stakeholder, quality, and integration management—and wondering how they fit together. Then comes the second list: five process groups, initiating, planning, executing, monitoring and controlling, closing. The newcomer assumes a tidy assembly line: finish planning, then execute. Schwalbe stops them cold. The process groups overlap in practice. You are executing while still planning, monitoring while closing, circling back as conditions change. Real projects are not a pipeline; they are a juggling act, and the framework is honest about that.

   The idea

   The knowledge areas are a checklist of everything that can sink a project; the process groups are when you attend to each. Beginners expect a linear pipeline—plan, then do, then check. Schwalbe's point that the groups overlap matters because it licenses iteration: you keep planning while executing, keep monitoring while closing. Integration management ties the other nine together, which is why it exists at all.

   Try this: Map your current project's activities against the five process groups and mark where two are running at once.

3. 3Chapter 1

   The CHAOS numbers: why software projects keep failing

   A 'Media Snapshot' in the opening chapter delivers the wake-up call. The Standish Group's CHAOS studies track software project outcomes, and the 2015 report found only 29% of software projects were successful, with 19% failing outright and the rest challenged—late, over budget, or pared down. Schwalbe reaches further back too: the original 1994 CHAOS study found just 16% of software projects completed on time and within budget. She notes those grim 1994 statistics helped fuel interest in project management certification.

   The idea

   Two decades of measurement and the success rate roughly doubled—from 16% to 29%—which is progress and an indictment at once. Nearly one in five projects still fails outright. The numbers justify the entire discipline: if software projects succeeded naturally, nobody would need certification, process groups, or this book. Failure at this scale is a management problem, not just a coding one.

   Try this: Look up your organization's last five projects and classify each as successful, challenged, or failed—then count.

4. 4Chapter 2

   Your org chart decides how much authority you actually have

   Before any technique, Schwalbe makes you look at where you sit. She describes four organizational structures—functional, matrix (in weak, balanced, and strong flavors), and projectized—and explains how the project manager's authority differs in each. In a functional structure, project managers have little clout; in a projectized one, they hold real power over people and budgets. The matrix variants sit between, with authority depending on whether the matrix is weak, balanced, or strong.

   The idea

   Same project, same plan, wildly different odds of success depending on structure. A project manager in a functional organization is negotiating for resources; in a projectized one, they command them. Knowing your structure tells you which battles to pick and where your influence actually comes from—formal authority, persuasion, or the goodwill of functional managers who control your team.

   Try this: Identify which structure your organization uses and write down your three biggest sources of influence within it.

5. 5Chapter 2

   The SDLC: four stages from idea to running system

   Schwalbe grounds IT projects in the systems development life cycle, describing its four stages: systems planning, systems analysis, systems design, and systems implementation. Planning asks whether the system is worth building; analysis captures what it must do; design determines how; implementation builds and delivers it. The framework gives IT projects a shared vocabulary that generic project management texts lack.

   The idea

   The SDLC matters to project managers because each stage carries different risks and different deliverables. Problems caught in planning cost far less than problems caught in implementation. Knowing the stages lets you match your project management intensity to where the project actually is—heavy on feasibility early, heavy on control late.

   Try this: Label your current project's stage in the SDLC and list the deliverables due before it can move to the next.

6. 6Chapter 7

   Three estimates for three moments in a project's life

   Schwalbe describes three types of cost estimates and when each belongs in the project life cycle. The rough order of magnitude (ROM) estimate comes early, when little is known and wide ranges are acceptable. The budget estimate follows as planning firms up. The definitive estimate arrives late, precise enough to commit real money. Each type matches the amount of information available at its stage.

   The idea

   The mistake is demanding definitive numbers at ROM moments or accepting ROM guesses at definitive moments. Estimate accuracy should improve as the project learns. Executives who freeze budgets from early rough numbers lock in error; project managers who keep re-estimating forever never commit. Matching estimate type to life-cycle stage is the discipline.

   Try this: Check what estimate type your current budget is based on and whether that matches how far along the project is.

7. 7Chapter 7

   Earned value: the math that tells you if you're bleeding money

   Schwalbe explains earned value management, the cost chapter's technical core. You track planned value (PV), earned value (EV), and actual cost (AC), then compute cost variance as CV = EV − AC, schedule variance as SV = EV − PV, and the cost performance index as CPI = EV/AC. These formulas compare what you planned to spend, what you accomplished, and what you actually spent—at the same point in time.

   The idea

   Traditional tracking compares spending against budget, which tells you nothing about progress. A project can be under budget and badly behind, or on schedule and hemorrhaging cash. Earned value forces the three numbers into one picture: CPI below 1 means each dollar buys less than a dollar's worth of work. It is the closest thing project management has to a dashboard warning light.

   Try this: Compute CPI for your project this week: earned value divided by actual cost. Below 1 means trouble.

8. 8Chapter 6

   PERT: three guesses beat one

   In the schedule chapter, Schwalbe describes the Program Evaluation and Review Technique. PERT takes three duration estimates—optimistic, most likely, and pessimistic—and blends them with a weighted average: (optimistic + 4 × most likely + pessimistic) / 6. The formula weights the most likely estimate heavily while letting best-case and worst-case pull the result toward realism.

   The idea

   Single-point estimates hide uncertainty; PERT surfaces it by forcing you to name the best and worst cases. The weighting toward the most likely value keeps the average grounded, while the tails capture the risk that optimistic planners ignore. Asking for three numbers also changes the conversation—people think harder about what could go wrong when they must state a pessimistic case.

   Try this: Take your next task estimate and produce all three PERT numbers instead of one.

9. 9Chapter 8

   RACI: ending the 'I thought you had it' problem

   Schwalbe describes the responsibility assignment matrix and its best-known form, the RACI chart. For each task, RACI shows who is Responsible, Accountable, Consulted, and Informed. The matrix makes explicit what teams usually leave to assumption—exactly who does the work, who owns the outcome, who must be asked, and who just needs to know.

   The idea

   Most coordination failures are ownership failures. Two people each assumed the other was handling the task; nobody was Accountable. The RACI chart's power is its bluntness: one Accountable person per task, named in writing. Filling one out for a troubled project usually surfaces the gaps within an hour—tasks with no owner, or three people all convinced they were merely informed.

   Try this: Build a RACI chart for your next deliverable and verify each task has exactly one Accountable person.

10. 10Chapter 8

    Teams storm before they perform—and conflict has five resolutions

    Schwalbe describes the Tuckman model of team development: forming, storming, norming, performing, and adjourning. Teams do not gel immediately; they clash before they click. She pairs this with five conflict resolution modes—confrontation solving, compromise, smoothing, forcing, and withdrawal—and notes that confrontation is generally the best approach. Not confrontation as shouting, but as directly working the problem together.

    The idea

    Storming is a stage, not a crisis. Managers who panic at early friction and force harmony often freeze teams in forming. Likewise, smoothing and withdrawal feel kind but leave problems intact; confrontation—naming the issue and solving it—actually resolves conflict. Knowing the stages lets you treat friction as progress and choose your response deliberately instead of reflexively.

    Try this: Name your default conflict mode from the five, then pick confrontation deliberately for your next disagreement.

11. 11Chapter 8

    What actually motivates people: Maslow, Herzberg, and Theory X vs Y

    Schwalbe brings in three classic motivation frameworks. Maslow's hierarchy of needs arranges human drives from basic physiological needs up through safety, belonging, esteem, and self-actualization. Herzberg's motivation-hygiene theory separates factors that prevent dissatisfaction—like working conditions—from factors that genuinely motivate, like achievement and recognition. McGregor's Theory X and Theory Y contrasts managers who assume people avoid work with those who assume people seek responsibility.

    The idea

    The frameworks converge on one point: you cannot motivate people with hygiene factors alone, and your assumptions about people become self-fulfilling. A Theory X manager who watches every hour gets workers who work only when watched. Herzberg explains why fixing salaries and offices stops complaints without creating engagement—motivation comes from the work itself, recognition, and growth.

    Try this: Audit your team's last month: how much effort went to hygiene factors versus genuine motivators like recognition?

12. 12Chapter 10

    Score your risks before they score you

    Schwalbe describes using a probability-impact matrix to prioritize risks, calculating a risk factor or risk score for each identified threat. The matrix forces two questions per risk: how likely, and how bad? Scores let you rank risks instead of treating them all as equally terrifying. She then lays out four response strategies—risk avoidance, risk acceptance, risk transfer, and risk mitigation—and explains when each is appropriate.

    The idea

    Unranked risk lists are anxiety documents; scored ones are decision documents. The four responses map to different situations: avoid when the risk is intolerable, mitigate when you can shrink it, transfer when someone else absorbs it better, accept when the cost of responding exceeds the exposure. Choosing deliberately beats defaulting to worry—or to ignoring risks entirely.

    Try this: List your top five project risks and assign each one of the four response strategies by name.

13. 13Chapter 11

    Contracts: who carries the cost risk?

    Schwalbe describes three types of contracts and when each fits. Fixed price or lump sum contracts put cost risk on the seller, who agrees to deliver for a set amount. Cost reimbursable contracts put risk on the buyer, who pays actual costs plus something extra. Time and material contracts sit between, paying for effort and supplies as consumed. The choice determines who loses money when estimates go wrong.

    The idea

    Contract type is risk allocation in disguise. Buyers love fixed price until scope shifts and sellers pad every quote to cover the uncertainty they now carry. Cost reimbursable fits genuinely uncertain work but removes the seller's incentive to economize. Matching contract type to how well the work can be specified is the entire decision.

    Try this: Check your current vendor contracts and identify who absorbs the cost risk if estimates run over.

14. 14Chapter 12

    The power grid: manage stakeholders by quadrant

    Schwalbe describes the power grid, which classifies stakeholders by their power over the project and their interest in it. Each quadrant calls for a different engagement strategy—high-power, high-interest stakeholders get close management; low-power, low-interest ones get minimal effort. The grid turns a sprawling stakeholder list into a manageable map of where attention pays off.

    The idea

    Stakeholder management fails when effort is spread evenly across everyone. The grid's insight is that engagement should be tailored: a powerful, uninterested executive needs different treatment than an interested, powerless end user. Plotting your stakeholders exposes where you are over-investing in the uninvolved and under-investing in the people who can sink or save the project.

    Try this: Plot your project's stakeholders on a power grid and identify one quadrant you are neglecting.

IT professionals, aspiring project managers, and students preparing for certification who need the PMBOK frameworks translated into software-specific practice. Also valuable for technical leads who keep watching budgets and schedules slip and want named tools to stop the bleeding.

FAQ