Best books for Technical Program Managers (TPMs)

Making Things Happen: Mastering Project Management

by Scott Berkun · 2008

~400 pages~10 hrs to read

A practical guide to running software projects: scoping, specs, schedules, decisions and keeping a team moving, written by a former Microsoft program manager. A good first read when you take over your first cross-team project.

The Mythical Man-Month: Essays on Software Engineering

by Frederick P. Brooks · 1975

~320 pages~8 hrs to read

Essays on why large software projects run late, including the cost of adding people and the communication overhead of big teams. Read it early to understand the schedule pressure you will be asked to manage.

Software Estimation: Demystifying the Black Art

by Steve McConnell · 2006

~310 pages~8 hrs to read

Explains how to estimate software work, express uncertainty as ranges and tell an estimate from a target. Useful when engineers and executives give you numbers that do not agree.

The Phoenix Project

by Gene Kim, Kevin Behr, George Spafford · 2013

~430 pages~11 hrs to read

A novel about an IT organization in crisis that introduces flow, work in progress and handoffs between teams. An easy way to see where delivery work gets stuck before you have a framework for it.

Influence Without Authority

by Allan R. Cohen, David L. Bradford · 1990

~320 pages~8 hrs to read

A method for getting help from people who do not report to you: work out what each side values and trade accordingly. Central to a TPM job, where every dependency sits with a team you do not manage.

Thinking in Systems: A Primer

by Donella H. Meadows · 2008

~220 pages~6 hrs to read

An introduction to feedback loops, delays and leverage points in complex systems. Helps you see why a program keeps slipping in the same place and where changing the process matters more than pushing harder.

Crucial Conversations: Tools for Talking When Stakes Are High

by Kerry Patterson, Joseph Grenny, Ron McMillan, Al Switzler · 2001

~300 pages~8 hrs to read

Techniques for raising hard issues when opinions differ and emotions run high. Useful for the conversations a TPM has to start: a slipping date, a missed commitment, a disagreement between two leads.

Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency

by Tom DeMarco · 2001

~260 pages~7 hrs to read

Argues that an organization with no spare capacity cannot change or respond to surprises. Worth reading before you commit a team to a plan that has no buffer.

Docs for Developers: An Engineer's Field Guide to Technical Writing

by Jared Bhatti, Heidi Waterhouse · 2021

Covers planning, writing and maintaining technical documents, including design docs, release notes and process documentation. Helps when your main output is the written plan, status update or decision record others rely on.

How Big Things Get Done

by Bent Flyvbjerg, Dan Gardner · 2023

~360 pages~9 hrs to read

Draws on a large database of projects, from buildings to IT, to explain why big projects overrun and how planning and reference-class forecasting reduce that risk. For TPMs who run large, multi-year programs.

An Elegant Puzzle: Systems of Engineering Management

by Will Larson · 2019

~290 pages~7 hrs to read

Essays on team sizing, org design, migrations and engineering strategy. Gives senior TPMs a view of how engineering leaders think about the same constraints you plan around.

Team Topologies: Organizing Business and Technology Teams for Fast Flow

by Matthew Skelton, Manuel Pais · 2019

~240 pages~6 hrs to read

Describes four team types and three interaction modes for organizing teams around fast flow of change. Useful when dependency pain comes from how teams are structured rather than from any one project.