The room thing just comes from the visual of a rockstar coder coming into work and locking himself in his office and saying don't worry, everything's fine, trust me I'll have it done in time. Beware of that.
While that is part of the underlying point, "beware of a guy in a room" is very much "don't stick a guy in a room by himself and let him do his thing" (he emphasizes it more in the video I linked to). The larger, more figurative point about having regular, public milestones is rule 4, "don't go dark", of which he claims rule 6 is a special case.
It really has little to do with the physical office space configuration. This problem could happen in open plans too, assuming a sufficiently complex project that can't be assessed by merely glancing over their shoulder.
It's largely due to the conventional wisdom created in the 90s by Microsoft's Jim McCarthy known as "21 Rules of Thumb for Shipping Great Software on Time".[1] Rule 6 (or 8 in his later talks[2]) is "beware of a guy in a room":
> Specialist developers who lock themselves away in a room, going dark for long stretches, are anathema to shipping great software on time. Without regard to their individual brilliance, before investing a developer with a significant assignment, it is essential that they understand and agree with the type of development program you intend to run. They must be capable of performing on a team, making their work visible in modest increments and subjecting it to scrutiny as it matures. Some people find this intolerable, and though there is a role for people of this disposition in the software world, it is not as part of a team devoted to shipping great software on time.
[1]: http://blogs.msdn.com/b/david_gristwood/archive/2004/06/24/1...
[2]: http://www.youtube.com/watch?v=oY6BCHqEbyc