6 ms·
IBM's infamous "Black Team" (2002)
- DannoHung 17y agoWhatever happened to that team?
- sdevlin 17y agoThey talk about them in (I think) Peopleware. It's part of a segment talking about how fostering a unique culture for your team can increase motivation. They mention that this culture persisted in the Black Team after all its original members had moved on. I'm not sure how long it continued on after that.
- sh1mmer 17y agoIf you haven't read Peopleware you really should. It's one of the best books on managing people working in IT around, still. If you like Spolsky, DeMarco and Lister were talking about this stuff years ago.
- Luc 17y agoIt seems to be out of print: http://www.amazon.com/dp/0932633439/ http://www.amazon.com/dp/0932633439/ . $95 second hand... Is it worth it?
- TimothyFitz 17y agoHalf.com (ebay) has it for $30 http://product.half.ebay.com/Peopleware_W0QQtgZinfoQQprZ657091 http://product.half.ebay.com/Peopleware_W0QQtgZinfoQQprZ6570... It's probably worth the $95 anyway.
- RiderOfGiraffes 17y ago> Is it worth it? Actually, I think so. Yes.
- sh1mmer 17y agoIt's been in and out of print on and off for years, I buy a few copies whenever it's back at the regular price. I've given away 6 copies now to various people.
- gcheong 17y agoYou can get it from the publisher ~$46 ($39.95 + $6SH): http://www.dorsethouse.com/books/pw.html http://www.dorsethouse.com/books/pw.html You might also try a local brick and mortar bookstore.
- gcheong 17y agoThe 39.95 price includes shipping (UPS ground). Read it wrong the first time.
- pge 17y agoTry bookfinder for used book search - http://www.bookfinder.com/search/?ac=sl&st=sl&qi=5jevSN1SLn3IaoOAIsA,hk6X,AM_1403341439_1:7:102&bq=author%3Dtom%2520demarco%26title%3Dpeopleware%2520productive%2520projects%2520and%2520teams http://www.bookfinder.com/search/?ac=sl&st=sl&qi=5je... New for $55, used for $4-65, but several in the $28-35 range
- DrJokepu 17y agoThis story made me think. Until now I had the impression that mediocrity at large corporations is inevitable no matter how many smart people they employ, simply due to the size of the corporation. For every talented, competent employee they have 10 average or below-average employees. Even at Google, even (and especially) at Microsoft. Competent people cannot choose who to work with so whatever extra they do is lost in the mediocrity that surrounds them. After reading this article I have realized that even at large corporations if you make isolated and largely idependent small teams of highly competent people that can select their members themselves, you can create "startup" bubbles inside the organization that can deliver outstanding results. Maybe this is the way to go when growing large, from a medium-sized enterprise to a large corporation?
- philwelch 17y agoIt's not a new concept. Look up Kelly Johnson and the Lockheed Skunk Works.
- roc 17y agoIf you can sufficiently insulate a group from the corporation in general, sure, you can do better than corporate mediocrity. For a while. But that's harder and harder to do. Particularly for decent stretches of time. Consider: it would be in the best interest of any project manager to steer their project away from the Black Team. They aren't incentivized to ship good software, but to ship on schedule. And should avoidance be impossible, they absolutely will point corporate HR at any and every aspect of that strong team, to break-up, slow-down or demoralize them. Similarly, with higher-up management. They'll need certain projects to be treated with kid gloves. So they'll scheme and conspire to either defeat the team and ruin its effectiveness or defeat the process, so that the team's effectiveness is rendered moot. It's the perverted reward structure in large corporations that causes most of their problems. There's no lack of people trying to fix those problems. But any solution (including this one) will ultimately be defeated so long as that reward structure remains.
- raheemm 17y agoIts pitiful that building bug-free software is considered legendary. Speaks volumes about our industry.
- alexgartrell 17y agoSystems got orders of magnitude more complicated, time to release got orders of magniture shorter, and everything got a whole hell of a lot better.
- btilly 17y agoI agree with 2 of your points, but the third makes me wonder whether you work in the same industry that I do.
- nostrademons 17y agoWould you rather be working with a green-screen terminal hooked up to a mainframe, or a modern computer hooked up to the Internet?
- eru 17y agoAgreed. (Though I still have my terminal set to green-on-black.)
- omouse 17y agoYou forgot the third choice: using pen and paper. I'll take the pen+paper and the occassional green-screen.
- meatbag 17y agoCan I get a green-screen terminal hooked up to the Internet?
- Kadin 17y agoIf by "green screen" you mean 3270 terminal, then ... yes, but it would be pretty hard. The networking hardware for a 3270 is pretty expensive. (I was going to say "getting pretty expensive," but in reality SNA has always been expensive; it's just that other networking hardware has gotten dirt cheap by comparison.) And, of course, you need some sort of actual backend computer to attach the terminal to. But sure, if you had a terminal, a spare IBM system (the iSeries is probably the lowest end) set up to support SNA, and then a networking controller to attach the 3270 to, you could probably get Lynx working. Alternately, if you just want the effect, you could just pick up an old green/black monochrome display and hook it up (via a physical adapter) to any VGA card. Buggy implementations excepted, all VGA cards should be backwards-compatible to MGA. Add a nice IBM Model M keyboard and you'd be all set. I suspect someone has probably done this as a case mod before (if not ... I might); stick a modern mobo in an old IBM PC case with the original monitor and keyboard.
- rayvega 17y agoTimeless. Not just that this happened in the 60's, but I didn't notice the publish date (2002) of the post itself until after reading it.
- wouterinho 17y ago"Some individuals even grew long mustaches which they would twirl with melodramatic flair as they savaged a programmer's code." Love it!
- alexandros 17y agoI think a crucial reason this worked is that there was a measurable objective, the value of which was universally understandable. Find software bugs. This is how they measured and selected the initial team, and this is how the team itself could prove its effectiveness in a management-compatible, objective manner and therefore defend its existence. Finding other areas where this could work is an interesting excercise.
- tcskeptic 17y agoI agree that measurability is important, but there are plenty of measurable objectives that don't inspire this sort of espirit de corp exhibitted here. I would love to know more about the leadership of this group, and if the leadership of the group fostered this sort of group identification. Is there a leadership lesson here, or did this emerge organically?
- willwagner 17y agoHaving worked in similar environments in the early 90's on desktop software, there are some serious downsides to this approach. Basically, it can lead to having a rift between developers and QA, and in a big corporation, it can become a bureaucratic mess and a 'us' vs. 'them' attitude between groups. I've been in long heated meetings between QA and Dev arguing over individual bugs, not so much on behalf of the customer as opposed to face-saving exercise. From the article: "And the things they did to software went beyond all bounds of rational use testing and were more akin to software torture." In a perfect world with unlimited time, it's great to find bugs through contortions but usually there is some costs associated with it either with QA not focused on other areas that matter, or having a developer focused on confirming that bug as opposed to working on something else. Sometimes it's great in a bigger organization to have a unique culture so I agree with the jist of the article and to other HN comments. For instance, I worked at a company on a smaller Macintosh team that fostered a healthy competition with the much bigger Windows team which worked well. I'm just not so sure it works well when people are essentially working on the same project where interfacing with each other is a requirement.
- raptorex 17y agomaybe I'm just feeling negative today, but this sounds like some bullshit to me. it sounds like the kind of thing that would be appealing to managers: having "not exceptionally intelligent or talented" employees who become completely obsessed with doing their jobs. great, you can pay them average salaries and they will be so loyal to your giant company. the story and the events themselves are fine, but I feel like the reason this story (and some of these details seem pretty apocryphal to me, like programmers crying because of bug reports) is so popular is that management types are taking the wrong lesson from it: that it would be desirable if employees were unhealthily obsessed with doing their jobs. then they try and manipulate their own people into doing the same thing.
- numbchuckskills 17y ago"great, you can pay them average salaries and they will be so loyal to your giant company" The point is that they become loyal to each other, the company reaping a reward is just a side benefit of people working towards a common goal. I was on a similar 'elite' skunkworks dev team in a company of ~ 35,000 that had executive support, and the results were insanely good. You can't manipulate people to do this; You can however give them the freedom to make it happen.
- potatolicious 17y agoI've had the opportunity to work on much smaller 'elite' teams before (7-10 people), and if I didn't have to eat and pay rent I'd do it for free. The amount of productivity, support, and "you grok me"-ness is so extreme that it's really a wonder to behold. As a regular dev now I really do look back on those days and wish I can do it all over again.
- colbyolson 17y ago"Pictures or it didn't happen!" Edit: I tried searching for anything related to IBM and their Black Team. It seems Google saturates my search request with everything linking back to this article. Perhaps someone could help?
- nomoresecrets 17y agoAs mentioned already, the book Peopleware has a section the Black Team, which predates this article by quite a few years.
- mtrichardson 17y agoI really, really hope that the team that's in charge of Apple's app review process doesn't start emulating these guys, with legal things instead of technical things. Though it seems like they kind of already have.