Project Manager (PM)
The on-time / on-budget / on-scope owner. Cares about the schedule, the budget, the risk register, and stakeholder communication. Strongest where the work is well-defined and the constraints are tight (construction, regulated rollouts, large physical projects). Cert ladder: CAPM → PMP → PgMP → PfMP.
Product Manager (PdM)
The why-and-what owner. Cares about the customer problem, the roadmap, the metric that proves the work mattered, and the launch. Strongest where the right thing to build isn't obvious (consumer software, B2B SaaS). The PdM doesn't typically own a ship date the way a PM does — they own whether the right thing shipped.
Scrum Master (SM)
A facilitator-coach. Cares about the team's health, the ceremonies (standup, planning, retro), and removing blockers. The Scrum Guide is explicit that the Scrum Master is a servant-leader — they don't direct the team's work, they protect the team's ability to direct its own work. Cert ladder: CSM / PSM I → A-CSM / PSM II → CSP-SM / PSM III.
Technical Program Manager (TPM)
A program manager with deep technical literacy — common at large tech companies (Google, Meta, Amazon). Coordinates initiatives that span multiple engineering teams, often deep in architecture conversations. TPMs read RFCs, push back on technical trade-offs, and translate between engineering reality and product/business asks.
↳ in the wild
| Role | Owns |
|---|