Tech Project Lead A -> Z

Introduction to a 26-chapter project management series for engineers becoming tech leads. Covers the chapter shape, the artifact-first stack, and how to read it.

The hub checklist that ties every artifact in this series together. Use it to start a project, audit a project mid-flight, or prepare for a handover.

Wrap-up of the Tech Project Lead A -> Z series: five lessons that outlast specific projects, the recommended reading list, and what to do tomorrow.

What PM, EM, and TPM actually do in software shops, and which mix of the three you are currently doing without realising it.

How to estimate software work without lying to yourself: three-point estimation, reference class forecasting, T-shirt sizing, and when planning poker is worth the time.

How to track risks before they happen and issues after, with the RAID log format and weekly cadence that keep the log honest.

How to map stakeholders to a RACI matrix, decide who hears what at which cadence, and write the comms plan that prevents 'I didn't know' meetings.

How to defend scope when stakeholders ask for more: the iron triangle, MoSCoW prioritisation, and the scope-cut conversation that ships on time.

What Scrum actually requires - sprints, ceremonies, roles - stripped of consultant theatre. The minimum that works for a 5-engineer team.

How Kanban actually works for software teams: WIP limits, cycle time, throughput. The board template and the metrics that matter, without inventing sprints.

How to pick the right methodology for the work in front of you. The decision tree, when each wins, and how to run a hybrid without it becoming process soup.

How to run project discovery without months of meetings, and the kickoff document that captures the result. Templates plus the meeting agenda for a 90-minute kickoff.

How to plan a software project: Now/Next/Later roadmap, dependency Gantt, confidence levels by phase, and honest communication.

How to keep a sprint moving day to day: a useful standup format, blocker management that actually unblocks, and mid-sprint scope adjustments without panic.

How to launch software safely: go-live checklist, rollback plan, ops handover doc, and the day-zero communication plan that keeps stakeholders informed.

How to run an incident from page to all-clear: severity levels, incident commander role, comms cadence during the incident, and the rollback decision tree.

How to run team retrospectives that change behaviour and post-mortems that reduce repeat incidents. Templates plus the action-tracking discipline that makes them stick.

How to run useful one-on-ones with engineers: cadence, agenda template, what to avoid, and the topic rotation that catches problems before they hit retros.

How to hire engineers without burning the team and how to onboard them so they ramp in weeks, not quarters. JD template, interview loop, and 30-60-90 plan.

How to give feedback that lands and write performance reviews that grow people. SBI model, growth plan template, and the conversation structure for hard feedback.

How to write a weekly status report stakeholders actually read: RAG status, top 3 risks, and the one-page format that fits in a Slack message.

How to write Architecture Decision Records (ADRs) and lighter decision logs that future team members and your future self will actually find useful.

How to take over a software project that is missing dates, losing trust, and running on heroics. The 30-day rescue playbook with artifacts and conversations.

How to ship a brand-new product from kickoff to launch in one quarter. The week-by-week plan, decisions to make early, and traps that delay greenfield projects.

How to modernise a legacy system without a big-bang rewrite. Strangler Fig pattern, route-by-route migration, and the ladder from old to new across 6-12 months.

How to manage a software project where most work is done by an external vendor. Contract structure, weekly cadence, acceptance criteria, and the in-house thin team.