PMO Training Programs

Project management for Software Developers

A program for engineers, tech leads, and engineering managers who run delivery without a dedicated PM, or want to work better with the one they have.

Who this program is for

Built for engineering people who own delivery outcomes, not Gantt charts

Tech leads

Senior engineers running squads and accountable for team delivery commitments.

Engineering managers

EMs managing multiple teams who need predictable throughput without heavy ceremony.

Staff/principal engineers

ICs leading multi-team initiatives that span backend, frontend, data, and infra.

Learning outcomes

What participants will be able to do by the end of the program

Estimate honestly

Use range estimation, reference-class forecasting, and confidence intervals instead of single-point lies.

Map dependencies

Identify cross-team, vendor, and platform dependencies before they bite the critical path.

Measure delivery

Use throughput, lead time, and WIP. Skip story-point velocity theatre.

Communicate up

Translate engineering reality into delivery narratives execs and PMs can act on.

pm for software developers

Curriculum: six modules

Module 1: Scoping technical work and ruthless cuts

Module 2: Estimation, forecasting, and uncertainty

Module 3: Dependency mapping across teams and services

Module 4: Flow metrics and delivery health

Module 5: Risk, architecture trade-offs, and tech debt

Module 6: Reporting to PMs, EMs, and execs

Software engineers planning at a whiteboard

Format & duration

Engineer-friendly format. Short blocks, applied to real backlogs

6-week cohort

One 2-hour session per week with practice applied to participants’ real teams.

3-day intensive

Compressed format for whole engineering teams as an onboarding bootcamp.

Cohort size 8-20

Mix of squads and disciplines so dependency conversations are realistic.

Tooling-agnostic

Examples in Jira, Linear, GitHub Projects, and Shortcut. Pick what matches your stack.

PM for Software Developers: FAQs

Does this replace having a PM?

No. It makes you a better partner to PMs and gives engineering teams the muscle to run without one when needed.

Is this Scrum or Kanban?

Method-neutral. We focus on principles (flow, estimation, dependencies) that apply to either.

Do you cover OKRs and roadmapping?

Yes. We cover how to translate roadmap intent into deliverable plans without theatre.

Can entire engineering teams attend together?

Yes. Private cohorts work best with intact teams using their real backlog.

Make engineering delivery predictable, without ceremony

Tell us about your teams and we’ll design a program around their delivery shape.