liveBook · Manning

Project manager

As explained in Think Like a CTO

A professional responsible for planning, coordinating, and controlling the work and delivery of a project.

A project manager helps an engineering group execute its plans by tracking resources, reporting progress, and continually revising timelines as daily events change them. Once a group grows beyond roughly five people, a dedicated project manager becomes important; smaller groups can often coordinate among themselves. section 9.1.1

The role works best when responsibilities are clear:

  • Project managers watch ticketing systems, run periodic meetings, and surface deadline risks early, including the reasons for a likely delay. section 9.1.1
  • Leads hold people accountable. Project managers encourage an open flow of good and bad news so timelines remain useful. section 9.1.1

Plan for actual availability

A schedule should allow for an ordinary working day with interruptions and for the time someone needs to regain context after vacation—not assume every nominal work hour is productive. section 9.1.1

How Think Like a CTO covers it

How deep it goes
Defines responsibilities and offers practical capacity assumptions, but does not provide a detailed scheduling procedure.
Examples
Uses a roughly five-person team threshold, a realistic working day, and recovery time after vacation.
What you can do after
Practice/perform it by monitoring progress, revising timelines, and flagging likely delays early enough to consider corrective action.
How it connects
Connects project management to scrum masters, engineering leads, ticketing systems, and deadline risk.

Also explained in

Compare how 2 books explain project manager →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a CTO. The section links point to the parts of the book it draws on.