Apply today for a FREE subscription to CIO Magazine!
Fri, Jan 11, 2008 16:17 EST

|
Posted by: Esther Schindler in Best Practices Topic: Personal ManagementBlog: Developer Wisdom
Current Rating: |
Need more productivity from your software development staff? Need 'em to put in more hours to get a project done on time? Buy 'em a pizza and hand out t-shirts. It's an age-old and effective method to get programmers and techies to willingly (sometimes enthusiastically) give up a weekend. But why do they come so cheap?
Recently, I was researching an upcoming article related to software development quality. In other words, I visited several online communities where developers congregate, such as the excellent SQA Forums, and asked for input. To my mild surprise, several suggestions for improving software quality include the appearance of a pizza delivery van.
It's not that I'm shocked that developers appreciate offerings of food. It's that their desires are satisfied with such a simple answer. A steak dinner? Sure, that'll get anyone's attention. Pizza and cheap beer? Why does that work?
It isn't that developers are unaware of the effect. Wrote one correspondent, "Even though we really know that [pizza] means overtime... we somehow still get excited about it."
Surely, you think, that can't be all they want. If free food was the only thing that motivated developers, people would be dying to work at Google. Hey, wait—
I have a hard time imagining this being effective in other professional communities. Would doctors show up at a New Medicine briefing for a pizza? No. Want accountants' attention? You'd better throw in a free round of golf. Even cynical computer journalists require more than pizza and a t-shirt for attention-acquisition. A seriously good buffet can do it. A vendor polo shirt, at a minimum. (One friend from Seattle confided, "Only if it's long-sleeve.")
But give techies a t-shirt that says, "The lost weekend: 1,500 bugs, 48 hours!" and they'll abandon plans for whatever approximates their real life. This can be extended from developers to technology enthusiasts; as user group officer, I could get members to spend their weekends demonstrating someone else's commercial product at the local CompUSA store... simply with the promise of a Team OS/2 t-shirt.
And pizza? Some call it a rotary debugger.
I'm not sure what makes developers different in this regard. It may be reflection of the "creative endeavor," that is, a design-centric profession in which one starts with a blank screen and invents something new. (Are painters and novelists as pizza-driven?)
Or (and?) it may be due to the solitary nature of that creative effort; food becomes an opportunity to gather, and edible gifts (however minor) are an acknowledgement of team contribution.
For example, another correspondent wanted the boss to bring breakfast (Egg McMuffins is his personal preference; "if it must be a special treat then bring in some strudel. Really anything that sounds foreign or contains more than two syllables would be fine"), leave it in a common area, and send out a short, simple e-mail that states you wanted to surprise the staff with a little thank you for all of their hard work. Adds Brent:
"Do not make it part of a presentation. Do not include any work details. Do not link it to overtime. Do not mention [the food] again later. Just bring them in and leave them for your team. This is a huge morale booster that people will remember."
Somehow, though, I'm not sure that those two items fully explain the phenomenon. Got any better ideas?
—Esther, who requires chocolate for motivation. Dark chocolate, and none of that cheap stuff.
Believe me this is effective not just for developers but for most I.T. geeks in general.
One of my prouder career moments was in February of Last Year when our Infrastructure Group fired up a new Data Center and relocated all the equipment and systems from the previous server areas between a Friday afternoon and a Sunday afternoon.
Pizza and Caffeinated drinks were a given. Total consumed:
9 large Pizzas
48 Donuts
5 Gallons of Coffee
10 gallons of Soda
Unfortunately I couldn’t do the T-Shirt thing (could not get the expense OK’ed) but I do believe your Pizza theory holds water and yes, it probably is kind of sad to think we can all be bought so cheaply…
Hackers generally like solving problems, building things, etc. Many times after work, they (we) go home only to basically do the same things as at work, but on personal projects. That's of course when you go home, if you're not sleeping under your desk or in the server room.
So, "work" is often not "work" if your workplace is even mildly engaging and tolerable. Of course, you can't keep hacking/coding forever, you have to stop to eat, so free pizza and beer is a HUGELY convenient and valuable perk.
The only thing better than pizza and beer would be giving people Lay-Z-Boys with a built-in porta-potty as well. Then you'd never even have to get up :)
There are far fancier options -- not to mention more healthy ones. What is it about pizza that makes it universal and accessible (as well as cheap)?
I'm behind the times, just now reading this, but as I blogged about, the cheap-ness is the giveaway. (Although, it had better meet the crew's standards.)
We're easy.
We love what we do. When we're not at work, we're often doing approximately the same things we do when we ARE at work. (Although minus the B.S.)
Give me enough money to retire and my activities would change very little. The focus would be different--I'd probably program games rather than political, medical, financial, whatever, data--but, no, when you love what you do, all you really want is some assurance that it's appreciated.
I mean, I can get taken advantage of anywhere. Show me why you deserve my work? Pizza? OK, good enough....
How do you get more productivity from your software development staff?
Fire the ignorant management who think that longer hours means more productivity.
This deathmarch style development sets the project back, as it is at this point that the quality and maintainability of the code take a nosedive. This hacked-together codebase written by tired frazzled developers is then a drag on the product for years to come when it is time to add features or fix bugs.
It is because the idiots are in the majority in software management that same mistakes happen over and over again. Completing one of these disaster projects counts as 'experience', and this culture becomes so ingrained that new managers start to think ahead at the start of a project to how the team can be bribed/coerced into doing these hours, instead of how to schedule the work correctly.