Project careers: coordinator to lead

The Project Management Institute (PMI) estimates that India has about 3.9 million project professionals today and projects that organisations there will need about 6.5 million by 2035, a gap of about 2.9 million once retirements and other departures are counted. Those are projections of people needed, not a count of jobs open this month. Job sites list many titles for what sounds like one job: project coordinator, project manager, programme manager, PMO analyst, Scrum Master, Product Owner, delivery manager and technical programme manager. The work behind a title differs by company, and senior roles count experience in months, not projects.

Below you walk one invented progression from fresher to programme lead, count eligible months from overlapping project dates with the rule PMI uses, build a portfolio of artefacts that shows judgement without leaking anyone’s data, and read a job description critically. Nothing here promises a job, a placement or a salary; the aim is to make the words on a resume and in a posting mean something.

Titles differ, but the work falls into four kinds

These titles cluster into four kinds of work. The first is coordinating a project someone else leads: the schedule, the risk register, the minutes and the status report belong to a project coordinatorproject coordinator: A support role on a project someone else leads, owning the schedule, the minutes, the risk register and the status report, but not the trade-off calls. or a PMO analyst, but the trade-off calls still sit above them. The second is leading one project end to end: a project manager owns the plan, the people the sponsor releases, the risks and the hand-over. The third is running related projects together as a programme managerprogramme manager: The person accountable for running related projects together to deliver a benefit none of them would deliver alone, coordinating plans and dependencies across the projects' leads., or a steady flow of work as a delivery managerdelivery manager: A project-leadership role in product or services teams that scales what a project manager does across a steady flow of work, often with less planning overhead and more stakeholder work.; in many companies both widen what a project manager does, across more teams or more time. The fourth is Scrum’s team-level accountabilities: the Product OwnerProduct Owner: The Scrum accountability for maximising the product's value and for ordering the Product Backlog, including the Product Goal; it is one person, not a committee. More in “Scrum theory, values and accountabilities” and the Scrum Master, which the 2020 Scrum Guide defines, with the Developers, as the three accountabilities of a Scrum Team.

The same person usually passes through several of these in a career. Walk the five phases of one invented progression and notice what each phase asks for:

Three invented people in Pune and Bengaluru show how different the paths can look while the skills still match. Priya joined a mid-size insurance company as an analyst, moved to project coordinator at year three and to project manager at year six on a mandatory DPDP compliance project. Rahul started as a backend engineer in a product company and moved into the Scrum Master accountability for his own team at year four. Neha joined a bank’s PMO as an analyst, built a benefits-tracking dashboard that the portfolio office actually used and became portfolio lead by year ten.

What experience counts: PMI counts months, not projects

A fresher’s resume often lists six projects over two years and claims three years of experience. PMI’s PMP examination content outline, the public rulebook of its best-known certification, asks for months of non-overlapping experience leading projects in the past 10 years: 36 months for a bachelor’s degree holder, more months for lower qualification levels and fewer for degrees from programs that PMI’s own Global Accreditation Center reviews. It says tenure is tracked in months, not in the number of projects, and its own example makes the point: a project led through January to March and another led through February to May together count five months, because February and March, which both projects share, cannot be counted twice. A lead who ran two projects together for six months counts those six months as six, not twelve.

The same outline says that only professional work counts. School projects, planning personal events and routine operational or administrative tasks do not qualify. A dated log of the projects you lead, kept as they run, is therefore the honest input: it shows which months were professional and which of them were leading.

The program takes five invented workplace projects, sums the months the naive way (each project in full) and then merges overlapping or adjacent months to count each calendar month once:

"""Count eligible leadership months from overlapping project dates with PMI's counting rule.

The PMP Examination Content Outline (2026) counts months spent leading projects, and counts
months that overlap once. A fresher who put every project's months on a resume would overstate
their experience. The script sums each project's months the naive way (overlap counted twice),
then merges overlapping intervals to count each calendar month once, and shows the two totals
side by side so the rule is visible.

Only professional project leadership counts: PMI's outline says school projects, personal events and routine
operational work do not qualify, so the five projects below are invented workplace projects.

Dates are invented. Months are counted inclusively: a project running 2022-07 to 2022-10 is 4
months. Two intervals that touch across the month boundary (2024-02 and 2024-03) belong to one
run of leadership and merge into a single interval.
"""

from datetime import date

# Five invented workplace projects a project lead in Pune led across four calendar years.
PROJECTS = [
    ("Payroll data clean-up",    date(2022, 7, 1),  date(2022, 10, 31)),
    ("Vendor portal pilot",      date(2023, 7, 1),  date(2023, 11, 30)),
    ("Branch Wi-Fi upgrade",     date(2023, 10, 1), date(2024, 2, 29)),
    ("Admissions portal rebuild", date(2024, 3, 1),  date(2024, 12, 31)),
    ("Warehouse automation",     date(2024, 9, 1),  date(2025, 6, 30)),
]


def months_in(d_from, d_to):
    """Whole calendar months from d_from to d_to, both ends included."""
    return (d_to.year - d_from.year) * 12 + (d_to.month - d_from.month) + 1


def to_month_index(d):
    """Absolute month index: 2022-07 and 2022-08 are consecutive integers."""
    return d.year * 12 + d.month - 1


def union_months(projects):
    """Merge overlapping or adjacent month intervals and count unique months."""
    intervals = sorted((to_month_index(f), to_month_index(t)) for _, f, t in projects)
    merged = []
    for start, end in intervals:
        if merged and start <= merged[-1][1] + 1:
            merged[-1] = (merged[-1][0], max(merged[-1][1], end))
        else:
            merged.append((start, end))
    total = sum(end - start + 1 for start, end in merged)
    return total, merged


def index_to_ym(i):
    y, m = divmod(i, 12)
    return y, m + 1


print("Project                       | From       | To         | Months")
print("------------------------------+------------+------------+-------")
naive_sum = 0
for name, f, t in PROJECTS:
    m = months_in(f, t)
    naive_sum += m
    print(f"{name:<30}| {f.isoformat()} | {t.isoformat()} |   {m:>3}")

union_total, merged = union_months(PROJECTS)
overlap = naive_sum - union_total

print()
print(f"Naive sum of project months (overlap counted twice): {naive_sum}")
print(f"Months overlapping with another project:             {overlap}")
print(f"PMI's rule, each calendar month counted once:        {union_total}")

print()
print("Merged leadership intervals (year-month):")
for s, e in merged:
    y_s, m_s = index_to_ym(s)
    y_e, m_e = index_to_ym(e)
    print(f"  {y_s}-{m_s:02d} .. {y_e}-{m_e:02d}  ({e - s + 1} months)")

Project                       | From       | To         | Months
------------------------------+------------+------------+-------
Payroll data clean-up         | 2022-07-01 | 2022-10-31 |     4
Vendor portal pilot           | 2023-07-01 | 2023-11-30 |     5
Branch Wi-Fi upgrade          | 2023-10-01 | 2024-02-29 |     5
Admissions portal rebuild     | 2024-03-01 | 2024-12-31 |    10
Warehouse automation          | 2024-09-01 | 2025-06-30 |    10

Naive sum of project months (overlap counted twice): 34
Months overlapping with another project:             6
PMI's rule, each calendar month counted once:        28

Merged leadership intervals (year-month):
  2022-07 .. 2022-10  (4 months)
  2023-07 .. 2025-06  (24 months)

The naive sum reads 34 months, as if every project had happened in its own time slot. The real timeline has 6 months of overlap, so each calendar month counted once leaves 28 months of leadership, in two runs: 4 months in 2022 for the payroll clean-up, and a long 24-month run from the vendor portal pilot through the warehouse automation. The gap between the runs matters: a month with no project in it adds nothing. Even 28 is eight short of the 36 a bachelor’s degree holder needs, and it is only the arithmetic; whether each month was leading rather than supporting depends on what you did, which is why the log records your role.

Senior postings often ask for a number of years, such as seven years of project leadership. The same arithmetic applies if you want to answer honestly: seven years is 84 calendar months counted once, and two part-time projects in parallel do not shorten the calendar.

A portfolio of artefacts shows your judgement

Describing a project in prose is easy; a reader cannot tell whether the work was yours or your manager’s. A portfolioA career portfolio: a folder of real artefacts from projects you led, redacted, that shows the choices you made. It is not the organisation's project portfolio. is five kinds of short document that a hiring manager can read in ten minutes and see your judgement in: the project charter, the delivery plan, one page of the risk register, two status reports and the retrospective summary.

Step through the five artefacts of one invented project, the admissions portal rebuild from the months example, and notice what each one is for:

The charter is the project’s one-page claim: the goal, the scope boundary, the sponsor, three objectives with numbers and three risks already named. A delivery plan is more honest when the gaps it had at signing are labelled; a Gantt chart without gaps shows software, not judgement. The risk register in the portfolio holds only the risks that were acted on, with the trigger and the week each one became an issue; thirty untouched rows show paperwork. Two status reports beat twenty: pick the one that first called a slip and the one that proposed the trade-off. The retrospective summary is half a page, not a list of complaints: three things that worked, three that did not, and the one change the next project kept.

Confidential data is the main risk in sharing a portfolio. Remove the real names of people and clients, invoice amounts, vendor contract text and anything the organisation treats as personal data under the DPDP Act, 2023, which defines personal data as data about an identifiable individual. When a figure must stay for the artefact to make sense, keep a ratio instead of an amount: “the vendor quote exceeded the budget by 28 %”, not the raw currency values. Read your employer’s rules before you share even a redacted copy; if they forbid it, build the portfolio from a volunteer, community or personal-scale project you led instead.

Resume layout, applicant tracking systems and portfolio sites belong to the resume-portfolio track, which also reads a job description from the recruiter’s side. This lesson covers only the folder of project artefacts behind a resume, and the resume builder in the note above is where the counted months end up.

A posting is a draft: read the work, not the title

A posting rewards critical reading. The three roles compared here (Scrum Master, PMO analyst, programme manager) have postings that overlap in language and diverge in substance. The same words mean different work in different companies, and the words that signal substance are not always on the first line.

Walk the parts of a project posting (the title, the responsibilities, the requirements and the team shape) and the probes you will raise in the interview, and notice which words signal real work and which signal trouble:

The three roles compare like this across the parts of a posting that matter most. The phrases are invented, not taken from a real posting:

The red-flag phrases are the ones that give one person authority over a team that is supposed to self-manage, or responsibility over an outcome without the money or decisions to shape it. A posting whose requirements combine “PMP, a Scrum Master certification and six years running teams of fifty” describes three jobs in one line. The list may be a wish list or a copy of an older posting, so the sensible move is to ask the hiring manager which of the three matters most, and let the answer show what the role needs.

Practise: roles, months and judgement

The questions reuse the lesson’s three invented people, the five projects of the months program and the posting walkthrough. Work the number out before you choose an answer:

Interview questions

Warm-up: in a company that uses both plan-driven projects and Scrum, how do a project manager and a Scrum Master differ?

They are accountable for different things, and the 2020 Scrum Guide names only one of them. A project manager owns a single project end to end: the plan, the people the sponsor releases, the risks, the budget, the hand-over, the reporting. A Scrum Master is accountable for the Scrum Team’s effectiveness and for establishing Scrum: they coach the Developers to their own decisions, help the Product Owner shape the Backlog and remove impediments the team cannot. They do not run a project, assign tasks, chase status for the team or take trade-off calls that belong to the Product Owner. In a company that uses both, the same person is rarely both at once on the same team; a project manager coordinates vendors and contracts around a Scrum team, while the Scrum Master stays inside it.

Warm-up: how does a programme manager’s work differ from a project manager’s?

A project manager leads one project end to end: its plan, the people the sponsor releases, its risks and its hand-over. A programme manager runs several related projects together so that they deliver a benefit none of them would deliver alone, and spends the day on what lies between the projects: the dependencies, the shared risks and the integrated plan, including decisions such as which project to change or stop at a stage-gate review. The titles vary by company, so in an interview it is worth naming the work rather than the word: one plan and one team, or several plans whose dates and budgets depend on each other.

Warm-up: what goes into a project portfolio, and what do you take out before you share it?

Five short documents from one project you led:

• the charter
• the delivery plan
• one page of the risk register
• two status reports
• the retrospective summary

Together they show the choices you made, which a prose description cannot. Before sharing, remove the real names of people and clients, invoice amounts, vendor contract text and anything else that is personal data, and keep a ratio where a figure matters, such as a quote 28 % over budget. Check your employer’s rules first; if they forbid sharing even a redacted copy, build the portfolio from a volunteer or community project you led.

Turning a project into a spoken story is the work of the behavioral-interviews track. The questions here test the role knowledge a good story rests on.

Two harder questions follow: one about counting leadership months when some of them were only support, and one about a Scrum Master posting that sits inside a vendor contract. Say your answer out loud first, then open each first step:

Key takeaways

• These titles cluster into four kinds of work: coordinating someone else’s project, leading one project, running related projects together, and the two Scrum accountabilities.
• Senior roles and PMI-style certifications count months of leadership and count overlapping months once, so a dated log of your projects is the honest input to any application.
• A portfolio of five short artefacts from one project (charter, plan, risk register, two status reports and the retrospective summary) shows judgement a prose resume cannot, once names and amounts are redacted.
• Postings reward critical reading: compare responsibilities, requirements, team shape and the probes you will raise, and read red-flag phrases as questions to ask rather than reasons to walk away.
• PMI’s talent-gap figures are projections of the people organisations may need, not a count of open jobs, and no lesson can promise a job, a placement or a salary.