Scrum: Weight Watchers for Managers.
Sunday, January 13, 2008
One thing that struck me was how similar Scrum and Weight Watchers is. Scrum is basically weight watchers for managers whose eyes are bigger than their team, so to speak.
With Weight Watchers, you get so many points per day. If you eat more points, then you get fat. Everyone knows that. What I didn’t know, till I started, was how having a set number of points forced me to consider what I was spending my points on. Sure, I could have a sausage mcmuffin, but thats like a bujillion points, and most importantly, I’m hungry an hour later. All that white flour turned instantly to sugar, my insulin hit the roof, I’m hypoglycemic and can’t think straight. Long term, my arteries are clogged, I’m overweight and I’m heading for heart failure. And, the more weight you carry around, the more you have to eat just to break even.
Its like that for programming. Most managers probably know that they are demanding too much from their team, their body, but they aren’t aware of all the poor choices that get made. They just want the candy, the donuts, the feel-good food. A demo by Friday, a new feature here, a deadline when. Hack it in. All those hacks are like cholesterol, and fat, just clogging up the program’s arteries. Things like tests, refactoring, team communication, are the leafy greens of programming, and managers just don’t like them. They know they should be putting it on the menu, but damn, that Bacon-Guacamole-Cheese Burger looks tasty and I can have it right now!
Are You Satisfied?
Weight Watchers puts the points in your face. I hate salad. I’ve eaten more salad this last week than in the entirety of 2007 I think. Its zero points for the lettuce, and then I add like a roast chicken breast, some fat free dressing and some kidney beans, and hey, I’m stuffed. With only so many points, I’m worried about one thing: am I satisfied?
That’s what Scrum does for you. Its about making you, the manager, the product owner, confront the costs of your eating choices. Yes you could eat what you want but your body, your team, your code, will be a lethargic, sickly, bloated thing that will ultimately cardiac arrest.
Presumably, this isn’t a chartable project. This is a product going to fight it out in the market. If you, the manager, are the brains of this operation then you need to make smart choices about what you put in your body. You need to be aware of how that donut and coffee not only puts on the pounds, but doesn’t actually satisfy you for very long. You need to think about what really satisfies you.
Scrum does two things:
1. It forces you, the manager, to consider how much you can “eat” per period, usually two weeks. You can’t eat more than that. So choose what you want on the menu wisely. You’ll also need to eat some of that nasty leafy-green stuff, like testing. Stuff that you may not like the taste of, but that keeps you fit.
2. It shows you the long term effects of your eating. For example, if you want to overwork your team, you’ll see an initial productivity increase, but within a few weeks you’ll see the productivity drop to less than it was before, and with more bugs. Your body has gotten fat, your arteries clogged, and you can now do less for the same effort. However, if you eat well, make good choices, you’ll see the muscle build, and you’ll learn more about your body and how it works. You’ll learn when to eat a few extra points, and how to make tasty, yet healthy choices.