A project manager is accountable for bringing a project home: the agreed scope, at the agreed quality, within the time and budget the sponsor accepted — or renegotiating those constraints honestly when reality moves. The title spans industries, but the responsibility set is remarkably consistent.
By lifecycle phase
Initiation
- Shape the business case with the sponsor; test feasibility before money flows.
- Draft the charter — objectives, success criteria, high-level scope, named authority.
- Identify stakeholders and their stakes early, while goodwill is cheap.
Planning
- Decompose scope (WBS or backlog), sequence dependencies, build the schedule and budget.
- Run the first serious risk pass — identification, assessment, response owners.
- Agree the communication rhythm: who hears what, when, in what form.
Execution
- Coordinate the work without doing all of it — delegation is the phase's core skill.
- Clear blockers, manage vendors, keep decisions moving at the pace of the work.
- Lead the team: motivation, conflict, protection from organisational noise.
Monitoring & controlling
- Track actuals against plan — schedule, cost, scope, quality — and forecast, not just report.
- Run change control: assess impact, decide or escalate, document. Scope creep is death by a thousand undocumented yeses.
- Deliver bad news early — the discipline that separates trusted PMs from status-theatre PMs.
Closure
- Formal acceptance, handover to operations, contract closeout.
- Lessons learned that actually get written down and re-read.
- Release and recognise the team.
The daily reality
Between the phase diagrams, the average PM day is: one standup or status sync, two stakeholder conversations (one of them delicate), an hour of plan/risk/budget upkeep, unblocking two issues, and defending the team's focus from a meeting that could have been an email. Communication consumes the vast majority of the role — that's not overhead, that is the job.
Adjacent titles, real differences
- vs Program manager — programs coordinate multiple related projects toward a combined outcome; strategic altitude rather than task altitude.
- vs Product manager — products are permanent, projects temporary: the product manager owns what and why over a lifetime; the PM owns getting a defined change delivered.
- vs Scrum Master — the Scrum Master owns team effectiveness within a framework, holds no scope/budget accountability, and leads by influence alone.
Foundations for the role are covered in Project Management Fundamentals; the PMP certification is the standard credential once you have three years of experience — see the PMP guide for eligibility and exam detail.
Frequently asked questions
What makes a project manager fail?
The recurring patterns: absorbing scope changes silently, reporting optimistically against evidence, and mistaking activity tracking for stakeholder leadership.
Which industries hire the most PMs?
IT and software, construction and infrastructure, banking/financial services, healthcare, energy and consulting — the skill set transfers across all of them.
Is coding knowledge required for IT project management?
No, but technical literacy — enough to follow architecture discussions and smell risk — measurably improves credibility and decisions.
