On an adaptive team the work a project manager traditionally does gets split three ways. Deciding what is worth building goes to whoever owns the value. Deciding how to build it and in what order within a cycle goes to the team. What remains is everything that faces outward from the team, and that is a substantial job rather than a residue.
Candidates find this topic awkward because the popular framings say the role disappears. The exam does not take that position. It assumes somebody holds accountability for the project, asks what that person should do in a described situation, and marks the answer that respects the team's autonomy while still owning the outcome.
What moves and what stays
| Responsibility | Where it goes | Why |
|---|---|---|
| Ordering the work by value | Whoever owns the outcome and the budget | The order is a business decision, and splitting it from accountability for value produces an order nobody stands behind |
| Deciding how the work is done | The team | The people doing the work know the most about it, and instructions from outside are guesses with authority attached |
| Estimating and committing within a cycle | The team | An estimate made by somebody else is a target, and a commitment made for a team is not a commitment |
| Removing organisational blockers | The project manager | Most blockers sit outside the team, and clearing them needs the standing and the relationships the role carries |
| Managing dependencies between teams | The project manager | Nobody inside a single team can see across them, and dependencies are where multi team delivery fails |
| Funding, contracts and procurement | The project manager | These are commitments made on behalf of the organisation, not decisions inside the delivery |
| Risk beyond the team's horizon | The project manager | A team manages the risks it can see. Regulatory, supplier and strategic risk arrive from outside it |
| Reporting to governance | The project manager | Somebody has to translate delivery into the terms the organisation funds and governs in |
The right hand column is the useful part. Each split follows from who holds the information or the authority, which means an unfamiliar responsibility can be placed by asking the same question rather than by recalling a table.
The failure at each end
Managing an adaptive team as though it were a predictive one produces the familiar symptoms. Task assignment, individual utilisation targets, status requested rather than observed, and a plan maintained privately that diverges from what the team is doing. The team stops raising problems, because raising a problem to somebody who will solve it for you is how you lose the ability to solve it yourself.
Withdrawing entirely is the opposite failure and it is less discussed. A team left alone still has dependencies it cannot resolve, a sponsor it cannot influence and a funding conversation it is not party to. A project manager who has decided that self management means non intervention leaves that work undone, and the team is blocked by things it was never positioned to clear.
The position between them is that the team owns the work and the project manager owns the conditions the work happens in.
Serving the team is a set of specific acts
Servant leadership is easy to agree with and hard to recognise in a scenario question, because every option sounds supportive. The acts that count are concrete.
Clearing a blocker means going to whoever controls the thing that is stuck and returning with a decision or a date. Protecting focus means absorbing the requests that arrive mid cycle and holding them for the next planning conversation rather than passing them through. Supplying context means the team knowing why the work matters and what happens if it is late, which is what lets them make sensible trade offs without asking.
Each of those is something done rather than a posture held. In a question, prefer the option where the project manager takes an action outside the team on the team's behalf over the one where they address the team about how it should work.
Scaling changes the balance
With one team the role is light on coordination and heavy on the organisation around it. With eight teams delivering one product, coordination becomes the larger half.
What appears at that scale is dependency management between teams, a shared view of the whole, integration and release coordination, and consistency of standards where inconsistency would cost. None of that is inside any team's remit, and none of it is a reason to take back the decisions that belong to them. The common error at scale is reinstating central planning under a different name, because coordination genuinely is needed and central control is the familiar way to produce it.
What the sponsor is entitled to
A sponsor funding adaptive work is entitled to know what has been delivered, what it has cost, what is expected next and with what confidence, and what could stop it. Those questions are answerable from a release burnup, a spend figure and a risk register, and answering them is part of the role.
The answer that fails is a description of the process. A sponsor asking when a capability will be ready is not helped by being told that the team works in two week cycles and reprioritises continuously. They are helped by a range, its basis, and what would narrow it.