Lead mid-size IT projects: hybrid delivery, governance, earned value, vendors, business cases, technical and security risk, recovery and your path to PMP and program management.

IT Project Leadership

Open the PMI certifications page (https://www.pmi.org/certifications) and download or open the current handbooks for CAPM and PMP.

From the handbook, write down the current eligibility requirements for each (experience and education) in your own words, and the date you checked.

Decide which one you are eligible for now, and which you could be eligible for next.

Read 15 job adverts for IT project manager or project coordinator roles in your area and tally which certifications they mention.

Start an experience log with the columns from the lesson, and add every project or project-like piece of work you have done so far.

Write a study plan for your chosen certification: education hours, weekly study time, practice question goals and a target month.

## Why it matters

IT project manager job adverts often list a certification, and the two you will see most are from the **Project Management Institute (PMI)**: the **Certified Associate in Project Management (CAPM)** and the **Project Management Professional (PMP)**. They do not replace experience, and many good project managers have neither. But they give employers a shared signal that you know the vocabulary and practices, and the PMP in particular is widely requested for mid-level and senior roles. This lesson explains what each is for, how to check the real requirements, and how to plan towards them without wasting time or money.

**Requirements, exam content and fees change.** This lesson deliberately does not copy them. Always read the current certification handbook on the [PMI certifications page](https://www.pmi.org/certifications). Checked on 2026-10-23.

## CAPM: the entry-level credential

The CAPM is aimed at people early in their project career, or moving into project work from another role. It tests knowledge of project management fundamentals, including predictive, agile and business analysis concepts.

- **Experience:** none required.
- **Education:** PMI requires a set number of hours of project management education before you apply. Courses from PMI and many other providers count; check the handbook for what qualifies.
- **Who it suits:** coordinators, analysts, junior project managers and career changers who want to show commitment before they have years of leadership experience.

## PMP: the experienced practitioner credential

The PMP is for people who have *led* projects. Eligibility combines experience leading projects with project management education. In broad terms, PMI asks for around three years of experience leading projects if you have a four-year degree, more if you do not, plus a set number of hours of project management education (the CAPM can count towards that education). Check the exact rules in the handbook.

The exam covers people skills, process and the business environment, across predictive, agile and hybrid approaches. That is why this course and your agile course matter: much of the exam is about judgement in realistic situations, not memorising formulas.

Important details:

- **Leading** means directing the project work, not only being a team member on a project. Roles such as project coordinator or Scrum Master can count when you led and directed work; describe what you actually did.
- Applications may be **audited**: PMI can ask you to provide evidence such as signed confirmation from a manager. Write your experience descriptions honestly so they would stand up to an audit.
- Both certifications must be **maintained** by earning professional development units (PDUs) over a renewal cycle.

## Other credentials worth knowing

- **Agile:** PMI-ACP (PMI), Professional Scrum Master (Scrum.org), Certified ScrumMaster (Scrum Alliance).
- **PRINCE2**, common in the UK, Europe and Australia, especially in government.
- **ITIL** for IT service management, useful if your projects hand over to operations.
- Later in your career: PMI's program (PgMP) and portfolio (PfMP) credentials.

Pick credentials that match the jobs you are applying for. Read 15 to 20 job adverts in your target area and count which certifications are asked for.

## Planning your hours

Most people aiming for the PMP keep an **experience log** from day one, long before they apply. For each project:

| Field | Example |
|---|---|
| Project and organisation | Northside Clinics booking portal, Northside Clinics |
| Dates | March 2026 to November 2026 |
| Your role | Project lead for portal and rollout workstreams |
| Hours or months leading | 9 months |
| What you did (in your own words) | Built the integrated schedule; ran steering committees; managed the integration vendor's SOW; led recovery of the records integration; managed a $480,000 budget with earned value reporting |
| Who can confirm it | Operations director (sponsor) |

If you log this as you go, the application takes an evening instead of weeks of trying to remember.

## A study plan that works

1. **Confirm eligibility** in the current handbook.
2. **Complete the required education hours**, ideally with a course that includes practice questions.
3. **Study the official material** referenced in the handbook. PMI publishes an exam content outline for each certification: read the current one rather than relying on someone's summary.
4. **Practise with situational questions.** Time yourself. Review every wrong answer and write down why the right one is right.
5. **Schedule the exam** when your practice scores are consistently comfortable, not on hope.
6. A typical plan is a few hours a week over two to three months, but it varies a lot by experience.

## Common mistakes

- Paying for an expensive course before checking eligibility.
- Trusting old blog posts about exam content: the exam changes.
- Describing experience as "led the project" when you were a team member. If audited, this fails.
- Treating the certificate as the goal. Employers still ask "tell me about a project you recovered".

## Quick recap

- CAPM: entry level, education hours but no experience required.
- PMP: for people who have led projects; requires leadership experience plus education.
- Always check current requirements, content and fees on PMI's site.
- Keep an honest experience log from your first project.

## Try it

Open the **Do** tab and build your own certification plan.


Understand what PMI's CAPM and PMP certifications are for, check your eligibility at the source, and plan your hours and study.

CAPM and PMP

CAPM versus PMP - What Are They and Which Should You Choose?

## Why it matters

As you move up, the questions you are asked change. A project lead asks "how do we deliver this project well?". A program manager asks "how do these related projects together deliver the benefit we want?". A portfolio manager asks "out of everything we could do, which projects and programs should we fund at all?". Understanding these levels helps you see why decisions above you are made, talk to senior leaders in their terms, and plan your own career. You will also almost certainly work with a **project management office (PMO)**, so it helps to know what kinds exist.

## Three levels

**Project.** A temporary effort to create a specific product, service or result. It has a defined scope, schedule and budget. Success = delivering the outputs to agreed quality, on time and on budget.

**Program.** A group of related projects (and sometimes ongoing activities) managed together because coordinating them delivers **benefits that would not be achieved by managing them separately**. A program usually lasts longer than any one project, and success is measured in benefits and outcomes, not just outputs.

**Portfolio.** A collection of projects, programs and operational work managed together to achieve **strategic objectives**. The items do not have to be related. Portfolio management is about selection and balance: choosing what to fund, setting priorities, and stopping work that no longer fits the strategy.

| | Project | Program | Portfolio |
|---|---|---|---|
| Focus | Outputs | Benefits from related work | Strategic objectives |
| Time | Defined start and end | Longer, may change shape | Ongoing |
| Key question | Are we doing it right? | Are the pieces adding up? | Are we doing the right things? |
| Success measure | Scope, time, cost, quality | Benefits realised | Return on the whole investment, strategic fit |

## Worked example: Northside Clinics

Suppose Northside's leadership has a strategy goal: "Make it easy for patients to reach us digitally."

- The **booking portal** is one project.
- Northside also runs a **patient messaging** project, a **telehealth video** project and a **website redesign**. All share the same patient sign-in, the same records integration and the same clinic staff for training. Managed separately, they would each build their own sign-in, train staff four times and compete for the integration team. Managed together as a **Digital Access program**, they share components, sequence training once and measure combined benefits (for example the share of patient contacts that happen online).
- Northside's **portfolio** includes the Digital Access program, but also a finance system upgrade, a building refurbishment and the day-to-day running of IT. The portfolio board decides how to split this year's budget between them. When money is tight, it might delay the website redesign to fund a mandatory security upgrade.

## Program management in practice

Program managers spend their time on:

- **Benefits management**: defining the benefits, who owns them, and how they will be measured after projects close.
- **Dependencies and shared resources** between projects.
- **Roadmaps** that sequence projects so that early ones enable later ones.
- **Program-level governance and risk**, including risks no single project owns.
- **Stakeholders and change** at an organisational level, for example changing how clinic staff work across all the projects.

## Portfolio management in practice

Portfolio managers and boards:

- Score proposals against strategy, value, risk and capacity.
- Balance the portfolio: quick wins and long-term bets, mandatory compliance work and growth.
- Review performance and **reallocate** money and people, including stopping projects.
- Make capacity visible: there are only so many people who can work on integration at once.

## What a PMO does

A **project management office** is a group that supports or oversees project work. PMI's material describes three broad types:

- **Supportive**: provides templates, training and advice. Low control.
- **Controlling**: requires the use of certain methods, templates and reporting, and checks compliance. Moderate control.
- **Directive**: directly manages projects; project managers report to it. High control.

Some organisations have an **enterprise PMO** or a portfolio office supporting the portfolio board. As a project lead, the PMO is often where your status reports go, where your business case is reviewed, and a good source of templates and lessons from past projects.

## Common mistakes

- Calling any big project a "program". If there is no shared benefit to coordinate, it is a large project.
- Program managers acting as "super project managers" and micromanaging each project instead of managing benefits and dependencies.
- Portfolios that only ever add work and never stop anything.
- Treating the PMO as a reporting bureaucracy rather than a source of support.

## Quick recap

- Project: delivers outputs. Program: coordinates related projects for combined benefits. Portfolio: selects and balances work to meet strategy.
- Programs are judged on benefits; portfolios on strategic return and fit.
- PMOs range from supportive to controlling to directive.

## Try it

Open the **Do** tab and test yourself on projects, programs, portfolios and PMOs.


Tell projects, programs and portfolios apart, and explain what a PMO does and how it affects your work as a project lead.

Portfolios and programs

PPP - Project - Program - Portfolio: What's the Difference?

Project vs. Program vs. Portfolio Management: Simple Explanation

Choose one target role from the lesson's table and write two sentences on why its daily work suits you.

Read three to five real job adverts for that role and list the skills and experience they ask for most often.

Rate yourself on each skill from 1 (no experience) to 5 (could teach it), with a short note of evidence.

Pick the three biggest gaps. For each, write one action you can take within your current work or study in the next six months.

Add a way to measure each action (a deliverable, feedback, a result).

Write the name of one person who could mentor you and draft a short message asking for 30 minutes of their time.

Set a date three months from now to review the plan.

## Why it matters

You have now covered the full range of an IT project manager's job, from choosing a delivery approach to recovering a failing project. This last lesson looks forward. IT project managers grow in several directions, and the skills that got you here are not all the skills the next role needs. A deliberate plan beats waiting to be noticed. This lesson maps the common paths, the skills each one needs, and how to build them while you are still doing your current job.

## Common next steps

| Path | What changes | Skills to build |
|---|---|---|
| **Senior project manager** | Bigger, riskier, more political projects; often vendor-heavy | Contract and commercial skills, executive communication, recovery experience |
| **Program manager** | Coordinates several projects for shared benefits | Benefits management, roadmaps, dependency management, organisational change |
| **Technical program manager (TPM)** | Common in tech companies; leads cross-team engineering programs | Deeper technical understanding (systems design, APIs, cloud), engineering metrics |
| **PMO lead or portfolio manager** | Runs governance, methods and portfolio decisions | Portfolio prioritisation, financial analysis, capacity planning, coaching |
| **Delivery manager or agile coach** | Focus on team flow and agile practice | Coaching, facilitation, flow metrics, agile at scale |
| **Product manager** | Owns what to build and why, rather than how to deliver it | Customer research, product strategy, data analysis |

None is "higher" than the others; they are different jobs. Choose the one whose daily work you would enjoy.

## What changes when you move to program management

Program management is the most common next step, and it changes how you spend your time:

- **From outputs to outcomes.** A project delivers a portal. A program is judged on whether patients actually book online and whether call volumes fall. You spend time on benefits, measures and adoption, often after projects close.
- **From one plan to a roadmap.** You sequence several projects, decide what each must deliver for the next, and change the roadmap as you learn.
- **From managing tasks to leading leaders.** Your direct counterparts are project managers, engineering managers and directors. Influence without authority matters even more.
- **From one budget to trade-offs between budgets.** You move money and people between projects to protect the overall benefit.
- **From team change to organisational change.** You plan communications, training and new ways of working across departments.

## How to build the skills now

You do not need the title to start practising the work:

- **Volunteer for cross-project work**: shared environments, a joint release, a dependency map for your department.
- **Own the benefits** on your current project: define them, measure the baseline, and track them after go-live.
- **Ask to attend** (or take notes at) portfolio or investment board meetings to see how decisions are made.
- **Lead a recovery.** Few experiences teach more, and they make strong interview stories.
- **Build technical depth** if you are aiming for a TPM role: system design basics, cloud fundamentals and how your company's software is built and deployed.
- **Find a mentor** one level above where you want to be, and a peer group of other project managers to swap lessons with.
- **Keep your experience log and stories**: for each project, note one example each of influence, a hard decision, a recovery and a measurable result.

## Worked example: a development plan

Sam has led the Northside portal project and wants to become a program manager within two years.

| Skill gap | Evidence of the gap | Action in the next 6 months | Measure |
|---|---|---|---|
| Benefits management | Has never tracked benefits after go-live | Own the portal's benefit tracking for 6 months after rollout; report to the steering committee monthly | Benefit report delivered; call abandonment trend shown |
| Roadmapping several projects | Has only planned single projects | Draft a combined roadmap for the Digital Access projects with the PMO | Roadmap reviewed by the program sponsor |
| Executive communication | Steering packs are long | Ask the sponsor for feedback on each pack; cut to one-page summaries | Sponsor feedback; meetings finish early |
| Credential | Has the experience but not the certificate | Apply for the PMP using the experience log | Exam booked |

The plan is specific, tied to real work, and measurable. Sam reviews it with a mentor every quarter.

## Common mistakes

- Waiting for a promotion before practising the next role's work.
- Collecting certificates instead of experience.
- Choosing a path because of the title rather than the daily work.
- Not telling your manager what you want. They cannot support a plan they do not know about.

## Quick recap

- IT project managers can grow into senior PM, program, TPM, PMO, delivery or product roles.
- Program management shifts the focus from outputs to outcomes, from one plan to a roadmap, and from tasks to leading leaders.
- Practise the next role's work now through benefits tracking, cross-project work, recoveries and mentoring.
- Write a specific, measurable development plan and review it regularly.

## Try it

Open the **Do** tab and write your own development plan.


Map the career paths open to an IT project manager and write a development plan for the skills your next role needs.

Growing into program management

Program Manager vs Project Manager: Key Differences

Program Manager Responsibilities - Project Management Training

Plan for PMI's CAPM and PMP, understand programs, portfolios and PMOs, and map your path into program management.