Technical project manager: how to train and review the role
Plans and delivers software projects: scope, schedule, team, risks and client communication. Runs sprints or milestones, tracks progress and shields the team from churn. Reports to the delivery head and is the main contact for the client.
Not sure what you need? Tell us about your business in six short steps and we will come to the first meeting prepared.
Share your requirementsWho usually fills this role
Typically senior developers, testers or business analysts moved into management, plus MBA or PMP-trained people. At hiring, test planning, estimation, honesty about status, handling a client who changes scope and understanding enough tech to question the team. Take references, and ask for a short practical demonstration before making the offer.
Skills ladder
Stage 1
New joiner
- Maintains task boards and meeting notes
- Tracks status and flags slips
- Supports a senior manager
Stage 2
Independent
- Plans sprints or milestones
- Manages risks and client updates
- Handles scope change
Stage 3
Senior or lead
- Runs multiple projects
- Manages large client relationships
- Mentors project managers
Training path
First weeks
- 1
Project and client overview
The delivery head explains active projects, contracts and client styles. The joiner writes a summary of one project that the head reviews.
- 2
Tools and routines
Teach the planning tool, status reports and review rhythm. The joiner prepares a report that the head checks.
- 3
Shadowing
The joiner attends planning, review and client calls and notes decisions. The head debriefs.
First year
- 1
Planning and estimation
Teach breaking work into tasks, estimation and buffers using past projects. The manager plans a sprint and the head reviews.
- 2
Risk and scope
Teach risk registers and change control. The manager handles a change request with the head's feedback.
- 3
Client communication
Teach honest status updates and bad news delivery. The head reviews drafts and joins difficult calls.
Towards senior
- 1
Multi-project planning
The manager balances people across projects. The head reviews allocation.
- 2
Commercial awareness
Teach margin, billing and renewals. Finance helps review project profitability.
- 3
Mentoring
The senior manager coaches juniors with reviews. The head checks progress.
Performance review
A weekly talk with the delivery head, a post-milestone review and a written half-yearly review. Keep each conversation short and based on records, not memory.
What to measure
| Measure | How it is seen |
|---|---|
| Delivery against plan | Milestone dates and reasons for slips |
| Quality at handover | Defects and client acceptance |
| Risk handling | Risk register actions |
| Client confidence | Client feedback and escalations |
| Team health | Attrition, workload and feedback |
| Commercial control | Scope change and billing records |
Evidence to bring
- Project plans
- Status reports
- Risk register
- Client feedback
- Change requests
Questions to ask in the review
- Which risks did you spot early?
- Where did the plan slip?
- How did you handle scope change?
- What does the client say about us?
- How is the team coping?
- What did you learn from the last milestone?
- What support do you need from me?
Pitfalls
- Promoting the best developer without management training
- Rewarding only on-time delivery
- No honest status culture
- Ignoring team overload
Questions about this role
Not necessarily, but enough understanding to challenge estimates.
Look at scope control, margin and quality as well as dates.
Plan to avoid it and confirm overtime rules with your adviser.