Best Seating Arrangement For a Team of Developers? 520
TekNullOG writes "I was given the job to prepare the logistics involved with moving our office. At the same time my bosses asked me to look into buying new desks for a small team of four developers and to consider if it could benefit the team to sit at a round table. In many offices and departments it increases productivity and makes collaboration easy. However, I am concerned that putting developers around a table could potentially be distracting consequently diminishing productivity by increasing coding errors. What are your thoughts?"
can we tag the article flamebait ? (Score:4, Insightful)
can we tag the article flamebait ?
Re: (Score:3, Insightful)
Spartan is best to focus the mind (Score:5, Insightful)
Re:Spartan is best to focus the mind (Score:4, Funny)
Ask your team (Score:5, Insightful)
You want to know how to arrange your developers? Why in the world don't you just ask them? Why are you asking slashdot?
Your developers know their preferences and corporate culture better than a bunch of strangers on a web forum. And they will happily tell you what they think would be optimal and why.
I don't understand why it is so popular for managers to think that they can maximize the productivity of their team by ignoring input from the team. It is utterly ridiculous. What...are you hiring children? Bums off the street, perhaps? Retards? Or are you hiring intelligent, professional, problem-solving specialists who are predisposed to have an interest in effeciency?
Sheesh.
Re:Ask your team (Score:4, Funny)
Depends on the size of the company, in my experience. The bigger the corp, the higher the chance that they mostly hire bums that try their best to just goof off instead of doing any sensible work.
Re:can we tag the article flamebait ? (Score:5, Interesting)
The last gig I did, I sat opposite the other developer who I needed frequent contact with. Everyone else got me by email, and I would initiate return phone calls. This avoided unnecessary interruptions in my workflow, and I could queue their requests to allow me to optimize my time.
In the past I've used similar setups. Do all the developers need almost constant face time with each other? Probably not. Then why stuff them in the same room?
At one company, everyone in the same office suite had their own office. That was maybe 1/3 of the development and systems staff. The rest were around the world. Communications were generally by email, except when live interaction was required. This kind of setup worked very well for me, so I could be at home, the office, or the datacenter, and there was no interruption to my workflow, except when I was traveling. It all worked out very well. It didn't matter what timezone someone was sitting in, the communications flow worked fluidly. That was a situation where all of the members of the crew were very good at their tasks, and didn't have to ask for help for stuff very much. Communications were limited to status updates and functionality interaction statements. Well, we'd BS sometimes, which was good for morale and to get to know each other better. I worked with a developer in Russia for probably two years before I ever heard his voice, and never did see him in person. I did know his work was accomplished properly, and his requests to me were usually "I need this functionality on these servers." I may ask for clarification, but since he knew what he was talking about his request were usually very clear.
I guess if you have a team who are going to have lots of questions because they aren't totally clear on what they're doing, stuffing them all in a room is a good idea. A well thought out and documented project plan would alleviate a lot of those problems though. I can imagine a room with 10 developers who can shout questions to each other would create an amazingly high amount of unwanted distractions. Verbal communications also reduce the paper trail. If everything is done via email, no one can say "I asked you for ..." and it wasn't done because it hadn't actually been asked for. The simple "You requested X at 3:30 and I responded it was completed at 5:00" is amazingly useful down the line. It completely eliminates mistakes in memory where we thought something was asked.
I've annoyed a few people before where I've told them to always email the requests to me. When they've failed to do so, but insist that they did ask for it, I can usually recite the conversation verbatim, and then they'll remember that they had only intended to ask for it, and never actually said to do it. That's usually enough to initiate the email papertrail so the same mistake doesn't happen again.
Re: (Score:3, Interesting)
Re:can we tag the article flamebait ? (Score:5, Funny)
It was a second story window, so I wasn't so scared of getting my back stabbed :-)
I'm far more worried about my boss doing the back-stabbing than a stranger through a window.
Re:can we tag the article flamebait ? (Score:4, Funny)
Good man. Keep your enemies close.
Re:can we tag the article flamebait ? (Score:4, Funny)
You are retarded. (Score:4, Interesting)
At first I thought you were being sarcastic, and it was modded insightful as further sillyness.
Then I realized you were serious.
You sound just like a PHB who has no understanding of the beauty of code.
A programmer taking pride in his work can create much better code then an "unhappy programmer working 9 to 5 and constantly afraid of losing his job".
I've worked in unhappy environments, and also happy ones. Guess which one I was more productive in.
I don't know what type of sweat shop you are running but I don't think I would last there 5 minutes. I'd be gone as soon as you said assembly line. And for your information, a workhorse can't read specs, and a programmer without passion for his job will not follow them.
Why not (Score:5, Insightful)
Re:Why not (Score:4, Insightful)
However, I am concerned that putting developers around a table could potentially be distracting consequently diminishing productivity by increasing coding errors.
I agree with parent, and have you considered that developers whose code quality is affected by seating arrangements relative to other developers might not be...um, the best developers? Otherwise, I'd say you might be overthinking the issue.
Re:Why not (Score:5, Insightful)
I agree with parent, and have you considered that developers whose code quality is affected by seating arrangements relative to other developers might not be...um, the best developers?
That's pretty dumb. Of course having face-to-face exposure to other people will have definite effects on productivity, some of them positive, some negative. Being in close proximity to other people, being able to hear them sighing, muttering, seeing the expressions on their faces, this is going to have some kind of impact. We're geeks, not fucking aliens.
Good plan (Score:5, Interesting)
Re:Good plan (Score:5, Interesting)
The current situation I'm in: (Yes, it's a rant...)
I sit in a half cubicle (where the wall only wraps the desk and no more and it's short enough to peek over without standing) and right next to me is my boss. Everyone else on our team is in different states. My desk also happens to be right next to the break room where people religiously burn popcorn, microwave fish, and speak to each other as if they are in a stadium because the television is turned up loud enough to drown out said people. There is someone about 12 feet behind me in a similar such cube whom I constantly hear sucking on one of those water bottles and randomly taking a bite out of an apple or other similar food product. I get a whole 5 minutes a day to do something that's not "work related" because someone thought it would be a great idea to take our Scrum process and turn it into a timesheet detailing what we did the previous day and if we don't account for at least 6 hours of work, who knows what will happen. But we are asked on our Scrum meetings to justify at least 6 hours of work.
My only solitude is late at night when most of the people have gone home, and that's when I get the most work done.
We used to be able to work from home, but some idiot decided it would be best to move to a VPN system that requires system validation to determine if you are on a work Laptop before granting you access to RDP to your own PC and I am not in a line of work that "requires a laptop." Said VPN system limits me to only browsing web pages. Big waste of time and resources since they are paying for my RSA token and account access that I can no longer use.
My suggestion for the OP... ask your developers. If you have the chance to give your developers a choice, DO IT! Then ask them again in 6 months to see if the situation is working. Above all, give them a chance to find a quiet place and don't force them into an open arena where people are constantly looking over their shoulder.
Re: (Score:3, Funny)
My desk also happens to be right next to the break room where people religiously burn popcorn, microwave fish,
There could be another reason for that: http://www.dilbert.com/strips/comic/2008-11-02/ [dilbert.com]
Re:Good plan (Score:4, Insightful)
Re: (Score:3, Informative)
You might want to reconsider doing such things - you could end up in prison.
http://www.lightlink.com/spacenka/fors/ [lightlink.com]
"In late July 1995, a trial jury convicted Schwartz of three felony counts under Oregon's Computer Crime Law. The charges related to his activities while working as a consultant at an Intel Corporation facility in Beaverton, Oregon."
Re: (Score:3, Informative)
My desk also happens to be right next to the break room where people religiously burn popcorn, microwave fish, and speak to each other as if they are in a stadium because the television is turned up loud enough to drown out said people. There is someone about 12 feet behind me in a similar such cube whom I constantly hear sucking on one of those water bottles and randomly taking a bite out of an apple or other similar food product
Try some noise canceling head phones - I recommend Bose QuietComfort 15 [crunchgear.com], an
Re: (Score:3, Informative)
Re:Good plan (Score:5, Insightful)
There is some group goofing off that occurs, but no more so than any other work arrangement I have seen.
Best arrangement I have seen:
- 2, maximal 3 people per room
- large desks, large monitors
- keep it quiet, put some plants there
- make it easy to collaborate without interrupting people (e.g. Instant messages*)
- Block Youtube et. al., they eat your time
* Instant messengers allow you to signal when you want to be left alone, and the program postpones showing you incoming messages.
Re: (Score:3, Interesting)
Best arrangement I have seen:
- 2, maximal 3 people per room
- large desks, large monitors
- keep it quiet, put some plants there
- make it easy to collaborate without interrupting people (e.g. Instant messages*)
- Block Youtube et. al., they eat your time
I was with you up until that last one. Eliminating the ability for developers to take mental breaks is a great way to just piss people off. If your developers aren't disciplined enough
Re:Good plan (Score:4, Funny)
Like in prison, but more regularly.
Re: (Score:3, Informative)
- Block Youtube et. al., they eat your time
Don't block YouTube/Google Videos/Vimeo, they might actually need those for their job. If your developers have a problem with YouTube, tell them to stop going on it. Do not rely on technology to solve a management/employee problem. A goof off will always find something to distract him, even if he doesn't have access to youtube.
Re: (Score:3, Informative)
- 2, maximal 3 people per room
4 or 5 is ok, too, IMO but only if all of them are in the same team (QA in one section of the office, office IT in another, etc). After all, the reason why the people are organized into different rooms is to encourage them to work better as a team.
- large desks, large monitors
The desks should be arranged so that one person can't see other person's screen. Everyone facing towards the center of the room, for example.
- keep it quiet, put some plants there
Provide the employees good headphones or encourage them to buy those themselves. Have soundproof conference rooms that peop
Re: (Score:3, Insightful)
Regarding instant messaging, you're quite right. We've established a few habits of when to try to be online, but in practice, most people have so many problems with random unwanted messages from random stalkers that they set themselves to invisible if the client allows it. Instant messaging benefits a lot from a fine-grained access model - 'I'd like my family to be able to see that I'm online except for the hours between 9 and 5; I'd like my co-workers to see me as online between 9 and 12 and 3 and 5; I'd like that creepy woman who nonetheless happens to be an important customer of ours to be unable to detect that I am online at all, unless I specifically have to be online for a meeting with her.'
Or, you know, have a separate account specifically for work.
Re:Why not (Score:5, Insightful)
I work under these conditions, and I'm looking for a new job. Unlike the other freaks on here, I do NOT like a work environment where I have zero privacy, where I get distracted every time someone walks by or a big crowd gathers around a neighboring engineer and has a loud conversation, and where I can't have a private phone conversation without everyone in my group hearing every word I say. Worse, this company has very few conference rooms, so it's frequently hard to find a private place to talk on the phone during breaks, and I end up in the hallway half the time (as do many other people).
Generally, the work I do is individual, though sometimes engineers will ask each other questions. I've worked in offices with standard cubicles before, and that arrangement is FAR preferable. It's not hard to stand up and go to someone else's cubicle if you have a quick question, and is good for your body too. Having a bit more privacy and quiet helps productivity immensely in people who are quiet and introverted by nature.
Generally, it's the stupid loud-mouth extroverted bosses who come up with these stupid seating plans, and think it's wonderful for productivity, yet they themselves have their own walled offices. Can you say "hypocrite"?
Re:Why not (Score:5, Insightful)
Much (probably most) of my career I've had a private office and, compared to those times I was in a cubicle bay, I got more work and better quality work done in the office environment. Although, that may be not entirely due to the office vs. cubicle difference as the companies that gave offices to developers were also understood more about what developers needed to be productive - less PHB MBA crap and heavy handed IT rules etc.
The need for continuous collaboration suggests that interfaces are not well documented or perhaps even well defined and/or the system/feature architecture is not well thought out. It also suggests that too much information is "in people's heads" -- and hence the company will incur unnecessary expense if one or more people get hit (very hard) by a bus (or, I suppose, a buss) or leaves the company. This isn't to say some collaboration isn't necessary (certainly for brainstorming about design issues and for the occasional "WTF is this code trying to do and why?") - indeed, if no ad hoc collaboration is needed, I suspect that too much effort has been expended on design and documentation. There's a happy medium.
So, the answer to the original question is "Yes, every workspace needs to be surrounded by floor to ceiling walls except for a door that closes! I once worked at a company which was locating to new facilities which were being built out for us. The facilities folks decided that cubicles for all was the answer. The developers pretty much stood up and said "over our dead bodies" and in the end all developers had private offices except for very junior ones (this actually made some sense because the less experienced one is, I think the more likely one is to learn from "random chatter" vs. be distracted by it - the first discussion you overhear about cache coherency models is much more valuable than the 30th one). Funny thing was, I noticed that even the facilities folks mostly had their own offices in the end - even though they were the ones arguing that wasn't necessary and citing studies that cubicles were more productive!
Re: (Score:3, Funny)
not if other people are in the room
Re:Why not (Score:5, Insightful)
No, you're underthinking it and ignoring the human element. Different people have different needs and react better to different environments. Some people hate noise. Others blare music in headphones. Some people multitask and deal with distractions well. Others can't. Some people like human interaction throughout the day. Others hate it.
It also depends on the task their doing. If the stuff they work on is closely interrelated, ease of communication may help improve productivity. If they aren't, increased distraction will likely reduce it- its pretty hard to concentrate on your work when 2 or 3 people around you are discussing something, code related or not.
The best situation I ever had was my last job- I had an office with an actual door I could close when I wanted privacy, next to a bunch of cubes where friends worked, so I could leave the door open and interact when I didn't (said interaction may or may not be code related).
Personally I would hate the round table idea though. Everyone needs some space to themselves for papers, books, pictures of the kids, etc and a round table just doesn't do that.
Re:Why not (Score:5, Funny)
We're the developers of the round table
we code when we're able
we eat pizza with cheese
work when we please
and we don't act real stable
on second thought...this is a silly post. Let's not go there.
Re:Why not (Score:5, Interesting)
I don't know, it may not be something they're immediately aware of.
A seating arrangement I've found works well is on the inside of a ring.
Have the desks setup with dividers so if someone needs to buckle down
and focus, they can, but if they need to confer, they can turn around.
I've tried cubes, offices, labs, and that setup, and I'd have to say,
for small groups, it seems to work out the nicest.
Re: (Score:3, Interesting)
Re: (Score:3, Insightful)
How do you get your reptile brain to turn down the fight or flight response?
You don't - you just invoke the fight response and shoot the people behind you - problem solved.
Re:Why not (Score:5, Insightful)
I agree with parent, and have you considered that developers whose code quality is affected by seating arrangements relative to other developers might not be...um, the best developers? Otherwise, I'd say you might be overthinking the issue.
Or maybe they are the best developers. Look up Asperger's syndrome.
And yes, ask them. Also, be prepared to possibly replace the desk(s) if it doesn't work out.
Re:Why not (Score:5, Interesting)
Re:Why not (Score:5, Funny)
Use a staged plan:
Week 1: Set each developer across from a failed 80s comedian. Yakov Smirnoff, Carrottop, Gilbert Gottfried.
Week 2: Remove the comedian.
Note that regardless of your seating arrangement, you'll get an unimaginable boost in productivity during week two.
What's an office? (Score:5, Funny)
I bet your programmers would be most efficient with a laptop on the beach, I bet they would even volunteer to work late.
Re:What's an office? (Score:4, Funny)
Re: (Score:2, Funny)
You forget. These are software developers, not sales people.
Re: (Score:3, Insightful)
They're usually less clothed at the beach.
Re: (Score:3, Insightful)
Why hooters? If you want live porn, go to a strip joint. If you want food, go to a better restaurant.
Re:What's an office? (Score:5, Funny)
I dunno. Strip joint sounds like an awful long way to go for porn. Don't they have internet at work?
If it's good enough for SEC Lawyers, it should be good enough for engineers...
Isolation Doesn't Increase Productivity (Score:2, Insightful)
It's extremely helpful when programming to ask a colleague to borrow their eyes from time to time, or to help work out a tech design on a nearby whiteboard. Around a circular table keeps the side-by-side, where they can easily wheel over to a neighbor's station to help out.
Sierpinski carpet (Score:5, Funny)
The best arrangement is to lay them out as a fractal a la Sierpinski carpet. Produces a decent tight packing and ensures that you are able to maximize your space. Other options that came to mind are if you have curved desks you could arrange them in a 69 fashion. Or get desks of different dimensions... some square, some straight, a few L-shaped ones. Then you could make the developers arrange their desks daily in a game of office Tetris.
Re: (Score:2, Funny)
Just make sure you don't arrange the desks in a perfect line going from one end of the room to the other.
Re:Sierpinski carpet (Score:5, Funny)
Or get desks of different dimensions...
Yeah, and if you use 4 dimensions, they could all occupy the same space!
Non sense (Score:5, Informative)
In addition, the foul odors emitted in that room were quite offensive. The farting, sweating, lack of showering...etc.... The best configuration for programmers is individual offices.
Re:Non sense (Score:4, Insightful)
I'm actually working somewhere right now where evryone has their own office. I loved having an office myself, but with everyone having their own its just too quiet. No interaction, no way to get to know anyone. There has to be a happy medium between that and the cube farm.
Re:Non sense (Score:4, Interesting)
Re: (Score:3, Interesting)
Re:Non sense (Score:4, Informative)
Agreed. I've worked in a shared space, a cube, and an office.
The office is the best.
Pair coding (Score:3, Interesting)
Pair coding can be surprisingly effective - it sounds a ridiculous idea, have one person code, and another just sit there and watch. But it works pretty well - the second person acts a check on the first, and the error rate drops. There will be interaction, humans are like that, and it's all to the good.
Also, you will have two people familiar with the code, not just one, so some pressure is reduced - holidays become easier to organise, for example.
I have worked in an office (now), a cube farm, a shared room
Re: (Score:3, Interesting)
Re: (Score:3, Interesting)
But the key words are "if done properly". Just stuffing two programmers on the same desk is, as you say, a good way to not get stuff done.
Re: (Score:3, Insightful)
Re: (Score:3, Insightful)
"Having separate offices does not in anyway cut down of non-work related conversations. "
It does cut down on person A's chat with person B interrupting and annoying person C. The problem with groups of people together is that any two talking are interrupting the entire group.
I could never get anything done in a setup like that, you can have my office door when you pry it from my cold, dead hand.
Scientific Evidence (Score:5, Interesting)
There are scientific studies that show significantly increased productivity by giving each developer their own office with a door they can close. Interruptions and distractions can torpedo productivity. These are mentioned, for example, in Steve McConnell's book, Rapid Development.
The agile crowd claims that having all the developers together increases productivity because you might overhear a conversation and be able to contribute something of use. In support of this they cite only personal impressions and anecdotal evidence. I know of not a single scientific study that supports their claim.
Best seating for 4 developer productivity? (Score:5, Insightful)
Re:Best seating for 4 developer productivity? (Score:5, Informative)
At my work R&D has offices in a circle around a shared bench area. If you want to collaborate you can go to the center area or use someone's office. If you want to listen in you just have to leave your door open. If you need some privacy and no distractions you can close your door. Best of all worlds.
Wha? (Score:5, Insightful)
My suggestion is: encourage people to work in a central common area. Put a conference table there. Whiteboard. Snacks. Some stupid toy from ThinkGeek. But also give them a "home base" where they can check their email, make phone calls, have a little privacy. They need a place to recharge.
"Coding errors" are not the problem-- those are easy to fix, because they're mostly typos. "Thinking errors" are the real problem. So make sure that their thinking environment is conducive to correct thinking. Shit-- if more developers used their brains before they touched a keyboard, the world would be a better place. When they're done thinking, they can go back to their desks and hammer out the code, because that's what coding should be: brainless hammering.
Re:Wha? (Score:5, Funny)
Fuck your bosses.
Well, that's one way to get ahead....
Use a square and face outward (Score:5, Insightful)
Re: (Score:3, Insightful)
This is basically our set up only we have 4 L-shaped desks in the middle of each wall since one of our corners is occupied by the door. It works out nicely. They get room for their two monitors and a bit of privacy, but if they need something, it's roll over to the guy you need to talk to and figure it out.
That being said, if you look at the code commits they do just as much from home from 10PM - 2AM as they do in the office from 11AM - 4PM.
Re: (Score:3, Insightful)
Agree completely - I've sat in all sorts of office situations - shared a "private" office with other developers, individual cubes with high walls, low walls, etc. The best arrangement is the bullpen - 4 developers with their backs to one another but a circular table in between them. Its a great balance between privacy and being able to collaborate when they want to.
Cubicles (Score:3, Insightful)
Seriously.. a well designed cube farm is pretty nice..
Monitors should be positioned such that someone walking by can't see what's on the screen..
As a programmer.. I hate all this "open concept" stuff. If I want to talk to someone.. I can get up and go visit them. Little pow wows around someones cubicle are insanely common where I work.. and very effective. Anything bigger than 3 or 4 people.. go find an empty room somewhere...
Re: (Score:2)
I second cubicles. I need walls. So I can do whatever I need to do without thinking my monitor is on show for the world to see. If I want to spend short (sub minute) breaks browsing this or that, catching up with my personal life, then so be it. But if I feel forced to always "look like I'm working" I can guarantee you I will be unhappy. And when I'm unhappy I code very poorly.
You have to have a level of trust in your developers. Development is not like laying bricks, it is a creative process. Emotional w
Shared offices (Score:4, Insightful)
Offices with doors that close. Big whiteboard in each office. Couple of guest chairs. Two developers to each office. Desks on opposite sides of room so they aren't stuck elbow to elbow, but still can swivel and wheel over to the other.
I worked at one company that did this in their LA branch office. I was in NYC but flew out there a few times a year. Most productive setup I've seen. Physical layout offers quiet, respect for technologists, room for collaboration whether pair programming, "other set of eyes", or effective (as in small =5 people) meetings, prevention of "mismanagement by walking around".
Nobody will do it nowadays. Those offices are given to clueless middle managers instead.
Sickness (Score:4, Interesting)
Yes the fad are Agile teams that all sit next to one another... but people tend to forget you will be down 1 FTE regularly because you all sneeze and cough on each other. Sickness runs rampant in those rooms... particularly if you have someone who is not hygienic in the group.
An office (Score:4, Insightful)
Jesus God stop trying stupid shit just leave me in peace you fucks.
Re:An office (Score:5, Funny)
Re:An office (Score:5, Insightful)
What the fuck is with these moronic companies that hire all these software engineers and then cheap out when it comes to physical plant? I mean, you must pay these guys 60-80k a year each, plus benefits. Figure 4 of them cost you 400k a year total, when you include cost of benefits.
Why in the hell would you want to cram them all into 100 square feet of bullpen shit cube space and waste at least a hundred thousand bucks a year worth of productivity? Lease expense for even the finest of office space is what, 30 bucks a square foot a year, so to give them 400 square feet of space (four 100 square foot offices) costs you at most an extra $9000 a year for the whole team in question.
That's about 2% of what you are spending on these 4 developers each year. It's a fricking rounding error. Shit, if it makes them happy and gets them to be even 5% more productive, it's well worth it. In reality, the difference between a non-productive, noisy office environment and a productive, happy quiet one is more like 50%-100% from my personal experience.
Sounds cramped (Score:2)
Sitting everyone round a table sounds like it could get a bit cramped. Development tends to generate loads of notebooks, post-its, design scribbles etc. Put those on a round table and you're going to get people running into each others mess.
Personally, I like to be in an open-ish (not too big, definitely not a cube) space with an area that's clearly identifiable as my desk. A nice cask nearby also helps but I havent been able to sell the idea to management.
A cross with medium height partitions (Score:2)
Aspergers much? (Score:3, Insightful)
Arthurian setup would suck for high functioning autistics. Sounds like a job for Temple Grandin.
Backs to each other, table in center (Score:4, Insightful)
I once worked in a somewhat similar arrangement. We had L-shaped desks in a cross arrangement. Each person sat in one of the inside corners of the cross.
Pros:
- It was easy to talk to each other.
Cons:
- It was harder to look at the person across from you over the monitors
- If you ever wanted to show each other your code, one of you had to walk around the desk or roll around it in your chair.
That last one was the dealbreaker. It might be easier on a round table (but then each would have very little room for their stuff), but you'd have the same problem to talk to someone who is not right next to you: you'd still have to walk around your neighbors.
I'm currently working in another department with the same desks, but arranged as the outside of the square. Takes up about the same space but it is much easier to roll over to someone's desk and work with them. You can take your laptop if you want (and wifi permitting).
And let's face it, it's just as easy to turn around to talk to someone behind you as to someone next to you. And if they are wearing headphones they won't hear you either way. Add rolling chairs and anything but carpet and it's just as easy to take something to show them too. Even without the corner desks, you can set them up in two rows back to back and it still works.
You could add a small central table for quick meetings, but I prefer the back to back arrangement any day.
(And people tend not to slack off as much because someone might be looking over their shoulder :) )
in offices (Score:2)
*big enough to hold the entire team, plus anyone they might be pulling in on something.
and for the love of god[des[es]|s] please give them a quality keyboard to type on, with quality being defined as whatever they want.
Group of 4, good, but concerned about tables... (Score:2)
The best arrangement I've been in is with 4 devs in a group, but each dev has 3 tables. Front, left, and right. Cube wall blocks in group of four with back to each other, but it's easy to turn around and convers, plus we had a hell of a lot of room to spread our work out on. I suppose a desktop software developer could get by with less room, since having bench equipment (oscopes, signal generators, etc) at hand aren't really helpful, but I'm sure you could find a use for the space...
And having our backs to
Sitting around a circle... (Score:2)
Means that when I want to look at the screen of my coworker across from me, I have to run around half the table to see it... Sitting in your typical square cubicle-type style means I can seem me peer's screen easily reducing potential wasted time. Plus it makes them less likely to surf for porn knowing there's potentially 3 people looking over their back =)
Private Offices (Score:4, Insightful)
Themed Arrangements (Score:3, Funny)
The NORAD Command Center in "War Games" was always a favorite of mine, but Starfleet(tm) Bridge or Engineering could be fun too. Folks could have uniforms of differently colored company polo shirts.
A generic command post with visitor theater above it might be intriguing.
Replicating part of the cubical farm in The Matrix could just be an interesting "after-work" team-building project.
Whee!
In order of preference (Score:4, Insightful)
1 - office w/door, see joel on software for an example
2 - cubicles w/entries facing a common area
3 - bullpen, desks in middle of room
Above all, have the team and management agree on a daily 2 to 3hr 'core time' when there are no conversations, pages, phones, meetings, or other distractions.
If everybody buys into core time, the cubes vs. offices, etc. will become a non-issue.
Re: (Score:3, Insightful)
DO NOT USE A ROUND TABLE!!! (Score:4, Interesting)
Use a RECTANGULAR table if you want to fit 4 or more people around a desk.
Smells like Management Fad to me (Score:3, Informative)
The idea that the seating arrangement matters much smells to me like Management Fad.
You say "In many offices and departments it increases productivity and makes collaboration easy." Is there a shred of data to back that up?
In Peopleware, DeMarco and Lister concluded that there was only one variable that correlated with programmer productivity: number of square feet of office space per programmer. If so, then to the extent that seating people around a round table puts them closer together, it will reduce productivity.
Peopleware (Score:4, Informative)
Collaboration vs Privacy (Score:3, Informative)
In 25 years, with experience being both the developer who had seating arrangements dictated, and the manager of a group who had to dictate seating, I have never heard a developer complain over the long haul that individual offices on the same short hall were causing too little collaboration and cooperation between the people on the team. OTOH, there were numerous complaints that being jammed all together created large impediments to ever finding a quiet time without interruptions to think through a complex problem.
Ask your experienced people which they prefer; someone who is six months out of school is not qualified to have an opinion.
Work from home? (Score:3, Insightful)
Unless your boss is big on pair programming, hire competent people and save on a building.
As the comments re: blocking out background noise via headphones attest, frequent interruptions from co-workers do stress people out and destroy productivity. Skype/Jabber can substitute for brief chats. VNC can substitute for showing a problem on someone else's machine. Record incidents by screencast for bug reporting - Often far more productive being summoned to a co-worker's machine to view a problem that is then mysteriously not reproducible at that precise moment.
Having worked on a project with staff in multiple timezones I can relate that 'the process' is more important than cramming as many people into a physical location.
Oh, and commuting sucks. Flexible hours from home fit in better with modern family life than worker bees who leave home at 8am and return at 6pm. I for one would prefer the Spanish model of a mid-afternoon recharge...
Bull pens and War rooms? Stink 'em out! (Score:3)
Oh yeah, been there done that. It's distracting. It's designed to intimidate people so they don't goof off.
The way to stop this is load up on beans, mexican and indian food. Cut farts that peel the paint off the wall. Maybe get a contest going with a likeminded coworker. It's biological warfare.
getting in the Zone (Score:3, Interesting)
Most coders perform best when they are "in the zone", free of distractions, free to concentrate on what they are doing. Focus is important. Coders don't need all day to collaborate, distractions throughout the day are highly destructive to productivity. There NEEDS to be collaboration, but not while you're trying to code. That's what morning meetings are for. Get your communications out of the way, discuss what the goal for the day/week/month is and what's the progress, and then split up and get it done.
If people have an easy opportunity to knock my out of my Zone every 10 minutes to ask a question or bounce an idea off my, I won't get anything done. And what I DO get done will be lower quality. When someone DOES do that to me, I drop what I am doing, completely. I give them whatever interaction they want, and make it crystal clear to them that they have COMPLETELY stopped my work while I interact with them. Trying to multitask a discussion requiring any amount of thinking breeds bugs faster than a bowl of Alpo on a cockroach farm. After they're done, I take a deep breath, try to remember where I was, and work my way back into my Zone and pray Susy doesn't wander back in 20 minutes with some followup questions. Most people quickly come to understand that the work I do is not compatible with multitasking and interruptions, and are more careful about when they interrupt my work. All of the managers I have had understand how this works, and will politely suggest to the coworker "couldn't this have waited until tomorrow morning?", when they'll find I'm MUCH more social.
Or maybe you're one of those rare few that can carry on a conversation and code flawlessly at the same time. Not me, not many of us. Face it, limited autism is conducive to good code. ;)
An easy choice for me (Score:3, Informative)
I've worked in quite a few different situations over the years, both as a developer and developer/manager:
a) a shared trestle table with 6 programmers facing across each other in pairs
b) a private office in a group of 8 offices surrounding a common area with couches and floor-to-ceiling whiteboards
c) a low bench in the back of a semi-trailer on a folding chair (luckily only for a week of 14-hour days)
d) a shared office with one other person
e) a regular private office
f) a shared office with three other people
g) a standard 6' high cubicle farm with your back to the 'door' on busy aisles, next to the creative department with 'open plan' tables, 4 to a 'pod' all facing the center
By FAR the best situation was b). The doors and half the wall facing the common area were glass with blinds. You could leave the door open and blinds up if you felt like being 'part of the community', or you could close the blinds and the door and turn on some music - without headphones - to focus for as long as you wanted. Discussions were held in someone's office or taken out to the common area for more of a group discussion.
The shared offices weren't bad, as you'd establish a rapport with your office mate(s) and come to some understanding of how your mate(s) worked.
The worst is the situation I'm in now - the cubicle farm next to the 'open-plan' teams. There's random noise all day, people having meetings in their cubicles or on the phone all day with customers. The only way to focus is to put on studio headphones and crank up the volume, and then you end up with people standing behind you in the cubicle talking at you for five minutes before you realize they're even there.
And since it's all open, everyone feels free to shout questions to each other over the cubicle walls instead of sending an IM, walking over to ask a question quietly, or take the discussion to a meeting room. And having a conversation with one of your direct reports means scheduling a meeting room or standing out in the hall outside the office.
Needless to say, I get at least twice as much done in a given period when I work at home. The dev team is always coming up with new excuses to work from home. And, of course, senior management, who all have nice window offices, can't understand how it could be difficult to work in that environment.
The best set-up, gauranteed (Score:4, Funny)
That's easy, the best seating arrangement is in a ring around my desk with their backs turned towards me so I can watch their monitors, at all times, and make sure they aren't doing anything other than coding. The best seats are backless stools with only one or two legs so they can't relax/loose focus without falling over.
WHAT!? My employees love me!
Visual Audio isolation a must (Score:5, Interesting)
Having gone through many office arrangement fads in the last 15 years, the one thing that consistently works, when management is good, is pretty much standard cubes or offices.
Collaboration without thought is simply placing people next to each other. Collaboration that is well thought out, is a good design process, good tools, and consistent clear management directives.
Another thing I've found useful is to not be stingy with tools (computers, software, extra monitors, etc...) and allowing people to have multiple of whatever they want. Let programmers have their own space or office (office is ideal), with 2 computers in each. If a couple folks want to team up for an afternoon, they can work in the same office. But come the next day, when they need to go back and focus on individual areas, zero distraction is what works. Computers are cheap in comparison to the salaries you're paying.
And lastly, the rest factor. If someone hits a wall, and just wants to zone out for 10 minutes browsing, say, slashdot:) for a while, doing so guilt-free because others can't see them is very beneficial. If instead there is pressure to work constantly, the quality of the work is going to go downhill. It has been estimated in various studies that people only do real work 5-6 hours out of an 8 hour shift.
That occurs for various reasons. But if people are pressured/forced to work longer than that national average, you'll still end up with people only working 5-6 hours out of an 8 hour shift, wasting 2-3 hours interrupting other people or zoning out pretending to work. And zoning out on nothing is boring, and de-stimulates the mind, making getting back into work slower/harder. If instead, a person is allowed to 'zone out' on something engaging (youtube video, phone call to friend, etc..) their mind will both be rested and still turned on when they return to work.
Circular Tables are Bad... (Score:3, Insightful)
I have been working with a team of 3-6 developers for quite some time. Recently we moved offices and ended up sitting around a big round table; and our productivity went to hell as a result. It didn't take very long before the team scattered, with many people working from coffee shops or home, and the remaining devs claiming vacant desks.
The problem is that development is done in two phases: You work with others to develop a plan, and then run off and get into "the zone" and get stuff done. The problem with "the zone" is that it is very fragile, and so all it takes is hearing two devs laughing about something through your headphones and now you aren't working either.
In other words, putting all the devs tightly packed together all day means that every time one dev is distracted for any little reason, suddenly they all become distracted.
If your dev team is important to your company's product and/or revenue, do everyone a favor and give them each an office with a window, as well as a common room to "hang out" in when they need to collaborate.
Cubicles ripped apart (Score:3, Interesting)
We (a team of 5) moved into new office space a month ago. We were put into 5 adjacent cubicles in a very large room. Which sucks: you are close enough to annoy each other by noise, e.g. phone calls, but not close enough to cooperate (which requires line of sight).
After a few days we removed the walls separating 4 of our cubicles, which took us a good hour and created a space of roughly 4x6 meters. The walls of the resulting big cubicle are lined with small tables, which we use when we want to work separately. In the middle, we have a table, which we use when we meet. When someone calls in a meeting, everybody just swings his chair around, and viola, the meeting starts within seconds.
On the central table sits a computer with two screens (sometimes facing opposite directions, showing same contents, sometimes side by side with different windows), two keyboards and two mice, so each of us can easily grab a device to point, write, etc. This computer has a complete IDE, and all documentation is in a wiki, the code is in SVN etc., so it has basically the same configuration as the others and everybody is familiar with it. Our meetings sometimes escalate when all of us compete for control of the mouse cursor, but generally discipline is high enough.
We found that this arrangement is the ideal balance between single and group workplace:
You want to work alone, turn your back to the others, face the wall. It gives you just about the privacy you need. You can listen to the discussions in the middle, but you don't have to.
You want to co-work (pair programming, discuss, etc.) turn around and face the middle.
We will definitely keep this arrangement, because we all find it very convenient, and we think that our productivity has increased a lot through it.
Of course, it might require more tables or computers than you have, but Ikea is around the corner, and you probably have a few unused PCs around your place anyway.
The tally so far (Score:3, Informative)
Here's how it pans out, give or take one or two that I misinterpreted, and not counting wafflers and OTs:
Private Office: 77 (62%)
Cube Farm: 14 (11%)
Open Area: 33 (27%)
The "privacy and peace required" advocates are in the clear majority.
Re: (Score:3, Informative)
Re: (Score:3, Insightful)