"War Rooms" Double Software Productivity 186
matt20 writes "Teams of workers that labored together for several months in specially designed "war rooms" were twice as productive as their counterparts working in traditional office arrangements, a study by University of Michigan researchers has found. Say goodbye to little cubes; it's war baby. I used to get tons done in a living room full of other people watching tv, doing
homework, and programming, but the biggest problem is always choosing the music.
War room is great, but... (Score:5)
War rooms? (Score:1)
"War Rooms" (Score:1)
Sense of purpose, perhaps? (Score:2)
Sitting down facing a screen, it doesn't really care if you work on the programming task at hand or if you play a couple rounds of xmame. With your peers all with you, you can't let the team down. So, by creating a team atmosphere, the end result is probably a constant fear of not wanting to screw things up for everyone ;)
On a lighter note, does anyone out there work in a "war room" type enviornment? It sounds like somewhere I'd like to work, but only if the chairs were leather and really comfortable ;)
extreme programming (Score:5)
Yeah. (Score:2)
I often find myself going to the Operating Systems lab to get stuff done, just because it's quiet, it's locked, (to only let the real nerds in) and there are lots of computers there, and comfy chairs, and a big table in the middle and stuff...
Now if only I could get to the article. Anyone have it mirrored or cached or something?
---
pb Reply or e-mail; don't vaguely moderate [ncsu.edu].
What do you mean flawed code? (Score:3)
luckman
i know what this is all about (Score:5)
the old cubicle system didn't allow for huge hookah-parties, thereby forcing employees/programmers to smoke out of their own small pieces, which didn't really get them that baked, just enough that they couldn't concentrate on anything anymore.
as a side note, picking the music is never difficult in a bong parlor-- no matter what you pick, everybody will start bobbing along to the groove and saying, "dude this is pretty sweet. what is it?".
love,
grizzo
www.grizzo.com [grizzo.com]
it's 100% grizzo
Re:Sense of purpose, perhaps? (Score:1)
I think you meant to say "IANACP"
Headphones save lives (Score:2)
We've got a wee micro company, in an industrial unit converted into a nice little open plan office. All the furniture is in a big loop and it can be very productive having everybody in the same space to bounce ideas off and go for mad creative and production drives.
But remember kids, headphones save lives!
War Rooms (Score:2)
XP favours a similar approach (Score:1)
It's worked wonders in my organization, and I suspect that the "war room" approach lends itself to similar types of productivity gains.
Re:i know what this is all about (Score:5)
yeah, but you better have good headphones (Score:3)
it's a nice way to create a feeling of working as a team, but i think that instant messaging & lunches together or something like that works just as well.
Re:extreme programming (Score:1)
I'm a slacker, and generally my partner is too, so we both end up screwing around. But we get stuff finished in time. However, I can do that by myself, too.
The only thing I can think of that working in pairs might really help is the design. Since you have to agree on stuff to write code, you have to decide on a standard way to do things, and that will help you a lot more in the end...
---
pb Reply or e-mail; don't vaguely moderate [ncsu.edu].
I will never believe otherwise (Score:1)
Re:War rooms? (Score:2)
I suspect it all sounds too touchy-feely new-agey for most organisations to paint their walls pink (or "rose") as a means of increased happiness/productivity. In fact, businesses in general tend to mistrust new and substantially different ideas about how they should be working. Ergonomics, colours for moods, war rooms, flex hours; and most of us are still working 8-5, M-F (theoretically!) in cube farms not much different from the secretarial pools of the 1940s.
As a corollorary, it's easy and happy to experiment on kids, because it's just as easy to dismiss important results as, "well that wouldn't work in the REAL world!"
Sorry--this is all off on a tangent. Nonetheless, business doesn't like to change.
Re: (Score:1)
Re:Sense of purpose, perhaps? (Score:1)
It's WAY better than being off on your own, since we're always asking each other questions or commenting about
We do have one rule - if you want to crank the music, bring your own headphones...
As far as 'war' goes, lan gaming is also much more fun when you can gloat right in front of your opponent..
Slacking off (Score:1)
Meanwhile, all around were other pairs of tables. I can't say we had great communication, but at least you knew when someone was making a pot of tea.
What exactly is a War Room anyways? (Score:2)
So forgive my ignorance of the terminology, what exactly is a War Room layout anyways?
personallity conflicts (Score:1)
Would being in an enviormnet like this increase such conflicts and cause the general demise of the project.
Conversely it may push those with conflicts to come to swifter resloutions realizing that they must work in such a close enviorment for an extended period of time.
The main thing I found interesting about this article was the mention at the end on how this may help developers create better team software so that we can share this kind of enviormnet without being in the same physical space.
Tools like AIM and MSN Messanger as well as wEBX, XDrive, NetMetting and others are a great start but we definatly need more.
Maybe VR ala Snow Crash [amazon.com] would be the anwser. Who knows. This is the type of research that needs to be done to find out though.
war room works here (Score:1)
we have what we call the "Engineering War Room" where i work. generally the Engineers are set up in four-person megacubes (or whatever :), but when there's a big piece of the project to finish we'll all go into the "war room" for a few days.
i find that that many people working towards a common goal really get things done. the room is coated in whiteboards, and everybody is free to comment and join in.
i'm not sure if it would work on a regular basis however. the "war room" only seems to work when we have a very clear goal to achieve, and it can't be a task that spans over many weeks. but for getting specific tasks done, i definitely suggest using that model.
on a related note, i once interviewed with a consulting company called Sapient [sapient.com] who the "war room" model almost exclusively. i imagine that this would work especially well in a consulting scenario.
- j
Re:Use of terminology... (Score:2)
"Can't we all just get along?"
Nope. Not in a capitalist economy. Capitalism implies (hell, it defines!) competition, conflict, and 'only the strong survive.' Competing agencies getting along is anathema to capitalism.
Sad, ain't it?
For a while, yes ... (Score:1)
But, yes. Put 3-4 persons and their teamleader in the same room when they're developing new software from scratch, and the whole process of architecture and designing will almost solve itself, if those persons are software engineers and not just simple hackers .. ;)
Get 'em coding (Score:1)
Re:What exactly is a War Room anyways? (Score:1)
Re:extreme programming (Score:1)
The reason it works (Score:5)
Ours is a generation that likes to surf and take lots of 'mini-breaks' when we are working by ourselves.
Having your boss sitting with you constantly changes the workhabits to create better productivity.
I'm not saying everyone does it, but I'm sure you have people at your office doing it, and 'war-rooms' would make them more productive...
--
with many eyes, all bugs are shallow (Score:2)
Writing this as I am from a 8x10 cube right now, I can tell you that if I was in the same room with other people that worked on this code and could just shout out questions to them I would be a lot more productive.
Instead, I might spend a substantially longer time thrashing through the problem myself. Or when I do resort to tracking someone down, it's a lot harder to find them in this maze of cubicles. Sometimes I can spend half a day on and off just trying to find one guy.
Re:Crappy Buzzword (Score:1)
War Rooms (Score:1)
Random Dr. Strangelove Quote: (Score:1)
Re:Sense of purpose, perhaps? (Score:1)
The only problem is that we have a lack of space for non-computer activities, which usually results in an ad hoc "meeting area" of a circle of chairs between "prongs".
We don't do any programming work, alas, but the variety of tasks (raw creation, proofreading, article writing, proofreading, tweaking layout, etc. (did I mention proofreading?) approximated the various stages of programming.
Re:War room is great, but... (Score:1)
"War rooms" connect with men's egos (Score:1)
It's not just a placebo effect. Numerous medical studies [webmd.com] indicate that people behave differently in war-geared situations, even in times of peace. If you can convince software-developers to tap into their subconscious desire for conquest, then they can even begin to forgo sleep and food (though interestingly, not sex), in a pursuit of the artificially placed goal set by the company.
Building special "war rooms" both placates men's self-images (power-seeking) and provides a modicum of logistic support to enhance the illusion (nurture-seeking). Rather than discourage competition, today's companies are elevating it to the highest ideal, unmasking sublimated urges and unleashing great profit potential.
Re:What do you mean flawed code? (Score:1)
Re:Sense of purpose, perhaps? (Score:1)
ITYM "ITYM IANACP".
CompUSA (Score:3)
They never did make that goal, or so it would seem. They appeared to be at war not with other computer sellers but the customers.
Warroom = Hell (Score:2)
Higher productivity in the shortrun doesn't make up for the higher stress and loss of company loyalty in the long run.
-Zane
Re:extreme programming (Score:3)
War room worked fine, until... (Score:4)
He chased one programmer into the server room. This resulted in an entire rack filled with fried boards.
So, it might be effective... as long as general stupidity is taken into consideration.
Peopleware and IRC as War room (Score:3)
I telecommute and we use IRC as our war room. It works great 'cause I can tune in and out w/o hassle.
--
Re:What exactly is a War Room anyways? (Score:1)
Re:War room is great, but... (Score:1)
Re:The reason it works (Score:1)
I wonder if I need counseling...
Re:yeah, but you better have good headphones (Score:2)
Another problem I have with this is that, well, when I'm coding I get kind of weird. I sit around with my tongue sticking out of my mouth, I make odd noises when something works or doesn't, I hold long, one-sided conversations with my code ("Why are you doing this to me? What have I ever done to you that you would behave like this? Oh, don't you dare tell me I wrote you that way, that's no excuse...") or start swearing at it - and I have a foul mouth when something just won't work. If my headphones are on, I bop around to the music and lip sync. All in all, I'm faced in the "farm" with the choice of looking like an idiot or making sure I never fall into "the zone" - which of course means I'm not doing my best work.
OTOH, it is really useful when you're working with other people who you need to be in close contact with, or if you're mentoring/being mentored by another programmer, and the guilt factor probably does lead to less goofing off. I think it's really dependent upon what you're doing and what kind of environment you work well in (not to mention whether you look like a kook while you work).
-Cyclopatra
Bah (Score:1)
Bah. Come on, people. There are 1001 better ways to improve efficiency than to rearrange the office furniture and give everyone a pretty view.
Re:Use of terminology... (Score:2)
Nope. Not in a capitalist economy. Capitalism implies (hell, it defines!) competition, conflict, and 'only the strong survive.' Competing agencies getting along is anathema to capitalism.
Bull. Capitalism is NOT "only the strong survive," and "getting along" is NOT "anathema to capitalism." Capitalism is freedom; often players in a capitalist economy specialize and then work together, because they are free to do so and it is to their benefit.
Sad, ain't it?
Slurs and misunderstanding sure are.
________________________________________
Re:Sense of purpose, perhaps? (Score:1)
Even though it nearly gave me carpal tunnel, due to both the crappy furniture and the insane amount of code we produced, we has a really great time, and it allowed us to produce a demo of our ideas really, really fast, which in turn allowed "the suits" (who occupied "real" offices in a different city), to gather enough VC to get us started.
Needless to say that, now that we have offices and moving to bigger ones next week, "Jeff's basement" has a mythical ring to it in our company, and even though production is still pretty good, it's really hard to recapture that atmosphere...
Is this warroom enough for ya?
Jan.
Re:For a while, yes ... (Score:1)
"You can't fight in here, this is the War Room!" (Score:3)
No cubicles, no dividers, and no monitors that faced into walls or corners. Everything was public and open to inspection at all times. At first, the lack of privacy was maddening. Even if you had time to surf for porn, you wouldn't dare. The noise was a problem, but I found that you quickly adapted. Most people were pissed to fuming at the beginning but this passed.
The most amazing thing was the teaming that went on. You would think this sort of forced teaming wouldn't work, but it did. Programmers that normally played their hands close to the deck became show offs. Spontaneous groups would form for discussion or demos or to show off some nice coding tricks. By simply removing cubicles, a totally different dynamic was created!
I now work alone much of the time and I miss my "war room" days. Maybe more companies will follow if the productivity claims are proven. Maybe in the future, programmers will be placed in open glass enclosures to be shown off during company tours. As long as those touring are advised to keep their hands away from the programmers, there should be little injury. Most programmers might be surprised that they would actually thrive in a fishbowl of an environment. I know I was.
It is prisoner's dilemma (Score:2)
Sure, when you play PD once, there's no reason not to defect. If you play a thousand times against the same player, on the other hand, defecting even once is dangerous.
Of course, it breaks down a little... in PD, if you both defect, you both lose. In real life, if you both goof off, but not so long that you delay the project, you feel like you've both won.
Bad Habits? (Score:2)
I'm sorry but most certification programs do nothing but teach people bad habits. Asside from Cisco's, very few of them deal with real world scenarios that a typical admin will experience. And a certification is not experience... its nothing but a bit of fact learning and memorization for things that will prolly not ever get used much in the real world.
A Certifcation doesn't show a desire to stay current, it shows a desire to pad one's salary.
Bring in young admins who are eager and smart. Its that simple. They needs certifications to prove they are smart... simple lay out a couple of problems (some of which have nothing to do with computers) and ask them how they would solve them.
Keep code isolated? Where do you work? In the real world lots of people touch other people's code because thats the only way its ever going to work. Source control is a wonderous thing... learn it.
Re:What exactly is a War Room anyways? (Score:1)
Re:Sense of purpose, perhaps? (Score:1)
I do, and it works. It really makes up for lack of communication, makes consultation easy, promotes a general group-organism kind of thing. Pretty cool, really.
War .. What is it good for ? Absolutly somethin` (Score:2)
finally, someone who supports my movement away from cubes.
I have probally been a lucky guy. All the companies I have worked for (for the most part) have been of the 'war room' mentality
Actually @home (Comcast division) was the one that started out NOT as a WarRoom. It was cubicle world, and i'll tell you .. productivity was horrible. (nothing like having absolute privace when you want to play a little quake eh ?) but I moved to the web side, and that was like a bullpen. It was great. If I was having a code problem - I just had to say 'HEY!' and someone might have an answer.
C.H.I.M.P's abounded, so we might not even have to look away from our screens. Pr0n surfing, and goofing off was not activly discouraged, but when all your companions are busting a$$ to meet deadline - you feel a LOT more guilty looking at e-bay, (or slashdotting i suppose *grin*)
at the contractors im working with now (for the new blackanddecker.com [blackanddecker.com] site), its a low cubicle wall place .. in nice ordly rows, with lots of caffinated beverages for free in the kitchen. Its a more-or-less war room environment. There are tv's here, and people talk to each other more readily. (The graphics part of the company was busily setting up a slot car track about 30 mins ago .. smelled of Ozone galore !) However, in the last week (of crunch time) i have probally worked 60+ hours with this site .. and honestly .. its been a HELL of a lot easier to do so, than if i was stairing at the grey fabric covered walls of a cube.
Last week (admist a spontanious poll of how many people had a sock monkey [thinkgeek.com] as a kid - so far its 28 vs 20 .. close race - 2 voted "what the hell is a sock monkey", prompting for some RATHER interesting drawings on the 'warboard' )
we were here untill midnight (with some chineese food as fortification.) Much easier, and actually kind of FUN. Although I kinda glad that im not expected to do that it every day.
I'm all for the war room, sides .. its easier to shoot your boss with a nerfball when you can see him all the time.
Hawthorne Effect ??? (Score:5)
Researchers many years ago at a GE plant in Hawthorne, England wanted to demonstrate the effect of improved lighting. So they increased lighting levels, and lo, productivity went up.
The problem came during the check-back when they lowered lighting levels to the original lux. Productivity went up even further!
It turns out the Heizenberg's uncertainty principle applies to people as well: If you measure and watch something, people react to the closer attention.
Re:Crappy Buzzword (Score:1)
There already is one of those, it's called the photocopy room ;-)
Re:For a while, yes ... (Score:1)
Army perform their best in war mode but they
will just end up being nuts if the war mode is
turned on too long (e.g. Vietnam war etc.)
So, unless you are looking forward to pay
a ton of cash to service your software engineers'
visits to the shrink... war mode should be like
DefCon 5... used only when it really calls for it.
When the "troopers" come home victorious, the
management has better give out "medals" and maybe
even a "heroes' welcome".
--
DevCon5 in computer world == A new Outlook virus
out when your entire system is 100% MS based.
--
I worked in one of these... (Score:5)
1) A very large whiteboard on one wall - with no furnature in front of it.
2) A spare computer and desk for "guests" to use during technical discussions (also used as a second terminal for the residents if they needed to run something that took a lot of resources)
3) It was a corner office in a tall office building, so it had an awesome view
4) Each person had their own phone
5) Nice workstations with 21" monitors
6) A comfortable "poof chair" (it is sort of a "full body" bean bag)
7) A shared bookshelf, so that you could borrow each other's books.
8) A collection of office toys, including a rubber-band powered plane (OSHA wouldn't have liked us flying that in the cube; too bad) and a bat suspended from the ceiling (it claimed to have a "soothing motion" - it didn't).
It worked VERY well since the three of us that shared the office all worked on the same projects at the same time. This environment was easily the most productive environment I've worked in.
People have mentioned "noise", though. It was true that music could be an issue. I recommend that companies buy GOOD headphones for every employee - a pair of $200 headphones can sound better than a $1000 set of speakers; once everyone has a set of these, you won't be able to pay them to listen to music on crappy computer speakers. The headphones should allow outside sound in and have at least 25' of cord (use an extension if you must).
As for ringing phones, that WAS annoying! It wasn't too bad, though, because we also had a "mini room" (actually two spare offices) across the hall. These rooms were used when people needed to have a long phone conversation, as they could go in and shut the door. This also gave some privacy. It was considered rude to talk for hours in the megacube, unless you were talking to everyone else there.
The furnature consisted of whatever we could dig up. I would recommend nice desks (single piece, not a U or L shaped desk) with LOTS of small tables. The ones that we had were 3' by 3' tables that could be configured however we wanted. If you wanted a "L" desk, you just grabbed three of these and put them on the left of your desk. I actually had a wrap-around desk build out of these. The nice thing is that you can reconfigure your space as appropriate for your work. We could, for instance, build a conference table in the middle of the room in a matter of minutes. All those nice "executive" desks really fall short in the ability to adjust to the work environment - they are nice for people who crave status symbols, but not for many others.
As you can see, though, this didn't save the company any money. The three of us had about twice the space we would have had if we lived in cubes. Not many companies could justify buying a poof chair for a space like this. Most environments I've worked in refuse to buy the most modern workstations for programmers, and 21" monitors are, sadly, rare. But, we were much more productive and I believe that our space and equipment cost less than additional employees would have.
I would also say that some of the positives of this environment came accidently. For instance, the company didn't think that being cheap on a bookshelf would increase productivity, but it did!
sustainable productivity? quality? (Score:2)
Pushing people do do more and to work longer and get things done faster is not the best way to get a productive work enviornment.
The problem is morale (Score:2)
Re:Use of terminology... (Score:2)
OK, maybe instead of 'defines...', I should have said 'is de facto...'
I'm afraid that I don't believe it, though. Capitalism invariably degenerates into economic head-butting. Companies that work together, only do so to compete more aggressively against the competition. Intel and MS, for instance have worked together for years because they don't directly compete, but rather complement each other; and they've leveraged that collaboration to keep the upper edge. How many Alphas running OS/2 were sold in 1995-1997? (when the agreement was at its strongest, and also when those competing companies were producing very viable consumer products)
You may not agree, but that's how I see it.
Re:Peopleware and IRC as War room (Score:2)
As long as we get some new equipment (Score:2)
I love working in an environment that includes other people next to or nearby. Where you can just ask a question out loud at normal volume levels and have somebody answer it vs. having to walk through a maze, schedule a meeting, or call a telecommuter at home.
It's all about instant communication. You need to tell somebody something, they're right there. You need to go over some specs, you give yourself a good shove and slide your chair over. How can that NOT be more productive that isolation.
When everybody is nearby it also turns into somewhat of a competition. I did 1200 lines today, how much did you do? I just fragged my 34th bug of the day.
Re:Bah (Score:2)
You seem to be mixing up hetero and homo here.
Re:Bah (Score:2)
Within Win32, you need to do QA on at least four platforms: Windows95, Windows98, NT4.0 and Win2000. If you're a *nix software shop, you'll need at least four of the following: Irix, Tru/64, AIX, FreeBSD, OpenBSD, NetBSD, Linux, OS/X, QNX or BeOS.
And I agree with the previous poster; Certs show nothing and teach little. On the other hand, experience is something you can't pay enough for. When the raid on the fileserver starts to go, do you want a MCSE who barely knows how it works and has to spend forty minutes in the Knowledge base and manuals to deal with it, and then has to run to another tech to double check, or the uncertified guy who has seen the problem before and could deal with it on the spot??
It would increase my.. (Score:2)
what??
oh WAR room. nevermind.
Re:Bah (Score:2)
relevent links... (Score:2)
Re:XP favours a similar approach (Score:3)
I'd like to see more research. Take the same team, put them in cubes, offices, and war rooms, and see how they do. It strikes me as entirely possible that the practices they talk about in the article as only being possible in "extreme collocation" are in fact applicable to any development team. Thus, the real factor is the implementation of software development best practices, and not the work environment. And there's plenty of studies that show good software process to be helpful, so it's not surprising that there was a big jump in productivity.
Well, I'm off to do some software process, by myself in my office. Gotta get those requirements written down...
Walt
slacking (Score:3)
Also: Whipping and video surveillance help too (Score:4)
--
Re:Use of terminology... (Score:2)
You stated your position a little more reasonably; and I more or less agree with the content of your statement, but not the sentiment. You think that competition is a bad thing; I think it is a good thing.
With what would you replace competition? Who knows so much that they can pick the correct product/strategy/etc. at the outset? And are people so homogenous that they would be happy with a pre-ordained choice? Or are you thinking of some method of having choices in similar products somehow without competition?
________________________________________
It's all about communication! (Score:2)
In a war room, direct interpersonal communication is easily available at all times. Advantages compared to technology aided communication of any kind are the very high bandwidth of communication (tone, body language,
Since people are in the same room most of the time, communication is always a multicast to all people related to the project. Using headphones, people that don't want to be disturbed can "filter" out such multicasts.
Sitting next to each other also makes social contacts very easy. People get to know each other. After a short while, they also feel a team spirit which shows in toys, t-shirts and common habits.
From my personal experience I can say that war rooms not only improve productivity, but make work a lot more fun!
War Room Veteran Speaks out :) (Score:3)
Hi,
We just (end of October), came out of a 2 month War Room based project. Normally we live in lil gray cubes. We had a hell of a schedule - 2 months to build a meta-search engine for prices of Books, Music and Video, that used a commercial data source for book music and video data, and dynamic scrapers to get prices.
Three of us went into the conference room, and we got it done on schedule (Books, Music and Movies [goto.com])
Why ?
I don't think I could work in one of these 365 days a year - and I suspect that being THE SOLE War Room was kind of ego-boosting - if everyone was in one, who knows.
Also, you really have to be involved in a tight project, with the ability to tell anyone coming into the room to f*ck off if it disrupts you or is not relevant to the project. In a normal multi-person office, the day to day interrupts can drive multiple occupants mad...
Winton
p.s. There is also a similar article in the New Yorker this month (page 60, Dec 11 Issue).
Re:Use of terminology... (Score:2)
Competition (between companies) isn't a problem. Cooperation (aka collusion) is a problem.
Competition gives you faster hardware, low-cost bandwidth, cheap long-distance service, and other nice things.
Cooperation/Collusion gives you MSFT OEM licensing agreements, the MPAA, the RIAA, price-fixing, etc. etc.
If I read swordgeek right, he's saying the same thing.
-Isaac
Re:I will never believe otherwise (Score:2)
IBM had it right (Score:3)
The IBM Santa Teresa report 25 years ago showed the right way to build offices for software developers: private offices with a door and window. They need to be near common areas for meetings. This was later supported by Peopleware.
The big problem with the Santa Teresa design is that it is an optimal solution. Since no brain power goes into finding better solutions, it all goes into finding excuses for not implementing it.
These war rooms were only compared to "traditional offices", ie those dreaded cubicles.
This article also used an oxymoron: "private cubicle".
Headphones (Score:2)
The problem with this, as outlined in Peopleware is that music engages the creative centers of the brain, resulting in work that is measurably less creative than if the work was conducted in a quiet environment.
My feeling with war rooms is that it is likely they work for short term projects where the quality and creativity of the result is not that important. Otherwise they are inappropriate.
War Room method works for CS classes too. (Score:2)
This saved them many hours of coding the rest of the class had to sweat through, yet in the end their programs looked different enough to qualify as individual programs(at UNM you are not allowed to work on programs in groups in most CS classes) because they implemented the psuedocode separately.
I watch the sea.
I saw it on TV.
Re:ITYM "ITYM "ITYM IANACP"" (Score:2)
(That's What He Said.)
Re:War Room Veteran Speaks out :) (Score:2)
Does this imply that a war room will only work if people's private lives and personal preferences are closely matched? I am not a sports fan, don't drink everynight and avoid sports bars. I'd avoid the group on off hours if I were placed in such a group. Would too much "diversity" ruin the dynamics?
Re:Use of terminology... (Score:2)
Then he's saying it poorly, or in a way that I'm failing to understand.
I agree with what you said. Unfortunately, the government during the FDR period rigged the laws of this land to favor collusion, condone monopoly, create and legitimize cartels, and weight things towards large interests in the name of "stability."
I would prefer a system that favors many smaller competitors, rather than a few large MegaCorps. I.e., I would prefer real capitalism to the government-by-pressure-group system that we currently have.
Along those lines, I would prefer the end of government-created and sustained monopolies, the busting up of cartels (like the banking industry), the limiting of patents and copyrights to shorter amounts of time as they once were, and either the inclusion of the "corporate death penalty" in law enforcement (i.e., corporations obey the same laws real people do) or the end of the corporation as we know it. Corporations used to be very special things, set up by the U.S. Congress and granted special legal status and exemptions. The Postal Service, for example. Private business was confined to being companies, not corporations.
This day of government licensing of all activity and "public-private partnerships" is really detrimental to capitalism, to our culture, and to our system of governance (a federal republic -- which is neither a democracy or a corporate state).
________________________________________
Re:Sense of purpose, perhaps? (Score:2)
Re:Headphones save lives (Score:2)
I have a headphone rule. I am fair game in all rocket fights *unless* I have my headphones on.
Then, if I am hit with a rocket, it is for informational purposes only.
One Rule for War Rooms (Score:4)
Do not all go out together for a TexMex lunch.
Re:slacking (Score:2)
Re:Peopleware and IRC as War room (Score:2)
I don't know how you'd convince people to do it otherwise. If they're using ICQ or AIM, or telecommuting some of the time, you could relate it to that (it's much better for a group environment). Otherwise it might be a hard sell.
Alpha 2 (Score:2)
Our team is the best and most tighted together among all here. We passed over crises, problems of different kinds and till now many "old guards" are still working here, while they "officially" already left their job. Most decisions are considered and weighted by the team and only then a decision is taken. Frankly, we don't have "soldiers" here. There is only one trouble - music. Tastes are so different that it gets some conflicts here.
I should note that this team is a hallmark around here. While not being the biggest ISP, we are the most influential in terms of methods and technologies. One of the biggest ISPs is made mostly of our "old guards". And this structure has proved to be the best. The examples of "cubicle" schemes on this fiels and which I work with, had all failed. Specially due to the fact that there was no normal communication schemes between the boss and you.
In a work that demands the minimum of failures possible, the boss should not only be in contact with the team but also be an effective member of it. Yeah it is hard for some, any private/confidential talk is nearly known by all. But we are also decisiomakers so it does not make a big difference. It may also look hard to divide work between business deals and technical tasks. But this brings decisionmaking into a more strightforward position. The boss knows things as a captain should know the battlefield. This is very fundamental under the intensity of some tasks we have.
Could one say... (Score:2)
Have a team go back to their respective cubes/offices/whatever after every meeting, and you can only judge at meetings.
Have the team in their own war-room, and you quickly know who's not a player.
Re:extreme programming (Score:2)
We had both forgotten the due date of the project. I realized, on Saturday, that it was due Monday, and tried to contact him. I was unable to do so until early Sunday afternoon. At the time, he thought it wasn't due till Wednesday, and was busy working on another project, so I went at it. This was at about 2PM Sunday.
Being that I'm not the best programmer in the world, and more of a 'systems guy,' writing the program was fairly difficult for me. The course is pretty crappy, being a first year CS program, and was oritented for the non-geek... For instance, we went over C++ vectors in the class, which IMNSHO, are total crap, and didn't go over linked lists, arrays, pointers, etc... lots of STL stuff, and little practical things.
I ended up having a lot of practical things in my final project, and only as many vectors as were required. :) ~40k of commented code and 22 hours with no sleep later, my online friends and I were done with the project. (Thank God for their help!) It was mostly broken, but it worked decently enough to submit.
Needless to say, I shall crush the balls of my supposed project partner, and feed them to him in a bottle.
-------
CAIMLAS
What's different? (Score:2)
There was once an office manager for a medium sized company. Productivity was lagging, so it came down to him to help the problem. He decided it was time to change the lightbulbs. Changing the lightbulbs up 10 watts increased productivity 20% "Wow!" thought the manager. "What an increibly increase for just lightbulbs!"
So he decided to do it again. Up another 10 watts. Another 5% increase! "Excellent. By upping the wattages on the bulbs, i've gotten higher productivity." He tried it again, another 5 watts. Another 2% increase, but people were complaining about the lights. So he took it down those 5 watts. Yet another 2% increase in productivity.
Why?
It has nothing to do with the lights, it's the change. People need an engaging changing environment so that they do become stale, and can remain productive. War rooms probably provide that sort of dynamic environment, but most likely at the cost of high stress.
Maybe they should look into new light bulbs instead.
--jay
Re:IBM had it right (Score:2)
It's interesting that everyone seems to assume that cubicles are the norm. Here in the UK, they're virtually unheard of. I've never worked in a cubicle based company, and although my girlfriend once did, that company has since got rid of the cubicles...
Re:slacking (Score:3)
I took a quick poll of my developers recently and asked "How busy do you feel you are on a scale of 1-10? Say a 5 or less is equal to I'm bored I need something to do, where a 9 or 10 is more like oh shoot even if i never leave my cube I still don't know if I'll meet my deadlines." The idea was that we were aiming for about an 8 for everybody. Some of my results:
So back on topic I'd suggest that ALL programmers should be spending about 70-80% of their day coding. If you have good coders, then the solution is not to let them be productive for less time during the day, but to give them more to keep them challenged. (I used to have a job where I played games 90% of the time because there was no challenging work to do. I *hated* that!)
phone (Score:2)
Too bad you could not put ALL the phones in there. Any ring is anoying. When will people stop using those stupid things except for emergencies? I hate it when people reach out and grab my attention like that. Even the awful Outlook, which interupts my typing, is better than the dying bird sound the phone makes.
Re:Use of terminology... (Score:2)
Well, let me try again here. You're both sort of getting what I mean, and at the same time, not quite. (I take full blame for not explaining myself clearly. :-)
Competition per se is a good thing, on the whole. However, it's fairly ruthless--companies (or individuals) go up against one another, and in the end someone wins and someone loses.
The best way to become a stronger competitor is to ally yourself with someone else. In other words (ironically enough), Competition leads to collusion.
At this point I should probably point out that I'm posting from Canada, which is definitely less of a free-enterprise capitalist country than the US is. That undoubtedly colours my opinions in some manner.
Also, I don't claim to be absolutely right about this, although I do believe it. Of course, I also think that all economic and political systems are inherently unstable, and won't last more than about a century at a time, so what do I know?
It's been an interesting discussion at any rate.
Re:Use of terminology... (Score:2)
The Byzantine Empire lasted 800 years with the same economic system, though; they were really strict about how money was to be handled. The penalty for debasing the currency (shaving gold coins in those days) was to have a hand cut off. Their currency was accepted the world over, even after the fall of their civilization.
________________________________________
Re:War rooms? (Score:2)