September 8, 2026 · 7 min read
TL;DR: Co-location is keyed 8 times and offered as a distractor 10 times in this bank, one of the most balanced splits measured across the whole set. The keyed cases all describe a communication bandwidth problem: information moving too slowly, or through too narrow a channel, for the project to keep up. The wrong ones describe problems that proximity does not touch, and one where the organisation has already said no.
Co-location is a genuinely effective practice, which is exactly why it makes such a reliable distractor. The exam is not asking whether it works. It is asking whether it addresses the thing the stem describes.
When information is the bottleneck.
The channel is too narrow. A team previously ran a single weekly working group meeting with email as its main channel, and is now moving to agile. Keyed is co-locating the team where possible for more face-to-face communication. Setting up a teleconference is offered, and the explanation puts it in its proper place: a teleconference is the fallback for a team that cannot be co-located, not the preferred change when co-location is available.
The sponsor is briefed rather than present. A sponsor works on a different floor and prefers email. Keyed is asking the sponsor to co-locate with the team a few days a week. The explanation is the best statement of the underlying principle in the bank: what agile wants from a sponsor is not more updates but shorter feedback loops, and those come from being present rather than from being briefed. A sponsor sitting with the team is in earshot of the conversations where problems first surface, can answer a question in the minute it arises rather than at the next scheduled slot, and can read the information radiators on the wall. Booking meetings to update them in person is offered and loses, because it keeps the sponsor a recipient.
The team lacks capability and has to absorb it fast. Team members are new, inexperienced and short on capability. Keyed is co-location together with a shared knowledge portal, training, and team assessments, because those are the tools that close a capability gap and then measure whether it is actually closing.
Speed depends on solving problems as they arise. Two records offer a small co-located team that can solve problems together as they arise, and the same wording is keyed in one and a distractor in the other, which is a useful reminder that the option text is not the answer. The stem is.
When the problem is about people, or about a constraint that has already been settled.
A personality clash. A co-located team drawn from technical and commercial units suffers clashes of personality and working style. Moving the project to a distributed way of working so co-location is no longer a factor is offered. So is building a schedule that keeps the clashing members working separately. Keyed is meeting with the team and agreeing what members expect of one another. The explanation is short and firm: separating people avoids the conflict rather than resolving it, and the project manager owns team performance. The team is already co-located, and proximity is not what created the friction.
A remote member being left out. A fully remote team member is rarely included when the co-located majority makes quick calls in the hallway or over lunch, and their input now arrives too late to matter. Assigning a co-located team member to relay hallway conversations each day is offered. Keyed is establishing a lightweight rule that any decision affecting the work is logged or flagged in a channel the remote member watches, before it is acted on. The explanation names the diagnosis: the problem is structural, not personal, and the fix has to change when the decision becomes visible to them, not how the team feels about them. A relay is a person patching a channel problem by hand.
The organisation has already said no. An agile project has a firm requirement to deliver quickly, the skilled people sit across four offices in different time zones, and the stem states that relocating or co-locating them is not something the organisation will fund. Accepting that the speed requirement cannot be met without co-location, and negotiating an extended timeline instead, is offered and loses. So does selecting the whole team from one office with less-qualified people. Keyed is designing overlapping working hours and asynchronous handoff practices so decisions and questions do not wait a full day for a reply.
Common trap: treating co-location as a substitute for a working agreement. The bank keys ground rules, decision-logging rules, and shared expectations in exactly the scenarios where a candidate reaches for proximity, and the reason is consistent: sitting in the same room changes how easily people can talk, not what they have agreed to do. A team that has not agreed how it will treat one another will do the same things at closer range. The bank explains this rather than just marking the option wrong, and the wording from the remote-member record is the one to carry: change when the decision becomes visible, not how the team feels.
| The stem's problem | Keyed | Not |
|---|---|---|
| Weekly meeting plus email is the whole channel | Co-locate for face-to-face | Teleconference (that is the fallback) |
| Sponsor emails from another floor | Sponsor sits with the team some days | More in-person update meetings |
| New team short on capability | Co-location plus portal, training, assessments | Conflict management and influencing |
| Personality clash on a co-located team | Agree mutual expectations | Go distributed, or schedule people apart |
| Remote member missing hallway decisions | Log decisions before acting | Appoint a relay |
| Relocation explicitly unfunded | Overlapping hours plus async handoff | Extend the timeline |
No, and the bank asks directly.
A question lists candidates for something that is not a Scrum event or artifact, and keyed is the shared area where the co-located team sits. The explanation lays out the framework in full: the artifacts are the product backlog, the sprint backlog and the increment, and the events are the sprint, sprint planning, the daily scrum, the sprint review and the sprint retrospective. It then makes the distinction that matters, noting that a shared area is a working arrangement widely associated with agile teams which genuinely helps communication, but is a physical setup rather than part of the framework.
The related move is worth knowing too. Asked what a functional manager on a waterfall project should do to get agile tools that expose problems before they happen, the bank keys putting the product backlog, Kanban board and velocity chart on display in a co-located team area. The co-located area is the setting; the visual management is the answer.
When is co-location the keyed answer on the PMP exam? When the problem is the bandwidth or speed of communication itself: a team relying on a weekly meeting and email, a sponsor who only sends email from another floor, a new and inexperienced team that needs to absorb knowledge quickly, or a project whose speed depends on problems being solved as they arise.
When is co-location the wrong answer? When the problem is interpersonal, structural, or a constraint the organisation has already ruled out. The bank rejects co-location for a personality clash, for a remote member excluded from decisions, and for a project where relocating people is explicitly unfunded.
Is co-location a Scrum artifact or event? No. The bank tests this directly. Scrum's artifacts are the product backlog, the sprint backlog and the increment; its events are the sprint, sprint planning, the daily scrum, the sprint review and the sprint retrospective. A shared team area is a working arrangement widely associated with agile teams, not part of the framework.
What replaces co-location on a distributed team? Engineered communication patterns rather than a substitute room. The bank keys overlapping working hours plus asynchronous handoff practices, so decisions and questions do not wait a full day for a reply, and it rejects routing everything through a single coordinator.
PMP Practice's 2,141 questions are certified against PMBOK 8 and the July 2026 ECO, with every wrong answer explained rather than just marked wrong. Start the free 20-question sample — no card, no signup required to try it.
Related reading: Virtual Teams on the PMP Exam: Why Forcing One Time Zone Is Never the Answer and The Team Charter and Ground Rules: 15 Keyed, 10 Distractors. Team tasks are mapped on the People domain study page.
When is co-location the keyed answer on the PMP exam?
When the problem is the bandwidth or speed of communication itself: a team relying on a weekly meeting and email, a sponsor who only sends email from another floor, a new and inexperienced team that needs to absorb knowledge quickly, or a project whose speed depends on problems being solved as they arise.
When is co-location the wrong answer?
When the problem is interpersonal, structural, or a constraint the organisation has already ruled out. The bank rejects co-location for a personality clash, for a remote member excluded from decisions, and for a project where relocating people is explicitly unfunded.
Is co-location a Scrum artifact or event?
No. The bank tests this directly. Scrum's artifacts are the product backlog, the sprint backlog and the increment; its events are the sprint, sprint planning, the daily scrum, the sprint review and the sprint retrospective. A shared team area is a working arrangement widely associated with agile teams, not part of the framework.
What replaces co-location on a distributed team?
Engineered communication patterns rather than a substitute room. The bank keys overlapping working hours plus asynchronous handoff practices, so decisions and questions do not wait a full day for a reply, and it rejects routing everything through a single coordinator.