Why do you need a project manager on your team?

An extended team needs its own project manager once coordinating the work takes more time than your product owner or tech lead has left: several teams or suppliers, a fixed deadline with outside dependencies, or stakeholders who want a regular picture of progress and risk. Below that point your product owner and tech lead carry the role between them, and a separate project manager mostly adds a layer of meetings.

What does a project manager do in a development team?

A project manager guards the plan, makes risks visible and keeps stakeholders informed, so the people waiting for the result know where the work stands. The role does not decide what gets built and does not decide how; it keeps the route between those two decisions clear.

Day to day that comes down to:

• Turning a goal and a date into a plan with milestones, and keeping that plan current and realistic as the work moves.
• Tracking dependencies on other teams, suppliers and your own organisation: an API that has to be ready, a data migration, a legal review.
• Naming risks early, with a proposal: cut scope, move a date, add capacity, or accept the risk consciously.
• Reporting progress to stakeholders who are not in the sprint, so they do not have to ask the developers.
• Removing blockers that sit outside the team: access, environments, decisions that are waiting for someone.

Does an extended team need its own project manager?

Not by default. In an extended team you direct the work and the sprints and set the team culture yourself, usually through your product owner or tech lead, while the partner handles recruitment, office, HR and operations.

That split matters for the question. The partner handles the employment administration: HR and absence. Your team still plans around absence and changes in capacity, but nobody on your side has to administer them. What is left for a project manager is coordinating delivery, and whether that needs its own person depends on your situation, not on the model.

An extended team can start with one developer beside your own people and grow when the work calls for it. At that stage a project manager mostly adds meetings. The question becomes real once the work spreads across several teams, suppliers or departments, or once a date is fixed by something outside your control.

How does a project manager work beside your product owner and tech lead?

Each of the three typically owns a different decision, though governance varies per organisation. The product owner typically owns what gets built and in which order, the tech lead how it gets built, and the project manager when it arrives and what stands in the way.

Friction starts where those decisions overlap. Two people who both reorder the backlog confuse the team. A project manager who promises a date without the tech lead’s estimate has made a promise nobody can keep. Agree up front who takes which decision, and write it down, so the team knows whom to ask.

A workable arrangement:

• The product owner keeps the backlog and the call on what may go live.
• The tech lead keeps the architecture, the estimates and the definition of done, together with the team.
• The project manager keeps the plan, the dependencies, the risk list and the stakeholder updates, and escalates when priorities and the date no longer fit together.
• Sprint planning and refinement stay with the team and the product owner; the project manager joins to hear what changes the plan.

When do you add a project manager?

Add a project manager once coordination structurally crowds out the work of your product owner or tech lead. You notice it when the backlog is not ready at the start of the sprint, code reviews wait, or stakeholders go straight to developers for status.

Concrete signals:

• More than one team or supplier works on the same release.
• A deadline is fixed by something outside the team: a contract, a regulator, a launch campaign, a system being switched off.
• Stakeholders ask for status every week and nobody has the answer at hand.
• Risks surface in the sprint review instead of weeks earlier.
• Your product owner spends more time planning and reporting than refining the backlog.
• A migration or integration depends on parties who do not work in your sprints.

If none of these apply, spend the budget on capacity that builds, such as another developer or a QA engineer.

How do you fill the project manager role?

There are four routes: your product owner or tech lead takes it on, you appoint a project manager in your own organisation, you bring in an interim project manager for a bounded period, or a project manager joins the extended team as a team member you direct like the developers. They differ on who owns the plan afterwards and how close the role sits to the work.

Your own product owner or tech lead is the lightest route and fits a small team with few outside dependencies. Watch the signals above: once coordination eats their time, the product suffers first.

A project manager in your own organisation fits when the coordination runs across departments: sales, legal, operations, other suppliers. That person knows your organisation and its politics, which a project manager from outside has to learn.

An interim project manager fits a peak with a clear end: a migration, a launch, a replatforming. When the assignment ends, much of what the role learned often leaves with it. What stays behind is what was written down: the plan, the risk list, the decisions and their reasons.

A project manager inside the extended team sits closest to the developers. The condition is the same as for every role in the team: you direct the work, so the project manager reports to your product owner or to you, not to a separate chain of command. At Backstage IT a project manager can be part of your extended team.

Whichever route you take, the rest of the team stays yours to shape. The same decision for the builders is covered in why you need a front-end developer on your team and why you need a back-end developer on your team.

Backstage IT builds extended teams in Moldova, with developers who work nearly the same hours as the Dutch workday. We recruit on the profile we agree with you, we hold the interviews together, and you choose the developer. It takes 3 to 6 weeks from the first conversation to the day your new developer starts, depending on the requested profile, and you can start with one developer.

Not sure whether your team needs its own project manager, or whether your product owner can carry it for now? Lay out your situation briefly and we will look at it with you. Get in touch.