Me: I’d like the fish strip basket.
DQ: The shrimp and chips basket?
Me: No… the fish strip basket.
DQ: OK.
Me: And a small Snickers Blizzard.
DQ: You want tartar sauce with that?
Me: *blink* I do with the fish strip basket.
DQ: Oh. Yeah… tartar for the fish, not the blizzard.
Me: Yeah. That would be gross.
was hesitant to post this since I’m fairly superstitious and this is one of those things that could easily be reverted, but last November I stopped biting my fingernails. I know, I know… it’s gross, etc., but it was a habit of mine for 30-something years, and those types of habits are hard to break.
I’ve attempted this many times before; I even used those hot-pepper polishes and tried a bunch of other techniques, but nothing ever worked. Then one day I was driving the kids home and there was Evan with his finger in his mouth and his nail on his teeth and I thought to myself “NO!”. I don’t want him to grow up like that. So I stopped right there and I’ve been free from nail biting ever since.
I find that I still instinctively move my hands to my mouth every now and again, but I always keep from actually biting them. I’m pretty darned proud of myself, actually. Quitting smoking in 1994 was much easier than stopping the nail biting.
<parody>What’s the one feature of an iPod that isn’t being talked about very much? Why it’s the spectacular portability as well as the incredible amount of space that you can store your porn with, of course!</parody>
Moe #1: <says_something_gross />
Me: Great. It’s a good thing I’ve got two kids, because now I’m sterile.
Moe #2: So you had a mental vasectomy?
If you work in software development you’ve probably been in or at least heard of a situation like this before: the boss wants some new swanky bit of tech and you’re the developer assigned the job. Not a problem… you love new challenges and this one seems like it’ll be fun. But then you learn that the project is deemed “important” so the BMOC wants to keep detailed tabs on it and assigns a Project Manager (PM) to the team.
Cue the scary music.
The history of project management.
Project management is, as my mother would say, as old as the hills. Shepards, farmers, and the like have all utilized aspects of what we now call project management for thousands of years; perhaps without even knowing it. Keeping track of where to plant, when to shear, and how to get the water from the river to the fields and animals are all tasks that could be found in the milestones of a project plan for running a farm.
Of course managing corn and sheep aren’t the only industries where project management has had a considerable effect; Ray Kroc of McDonald’s created an empire out of ground beef and sesame buns because he understood that efficiency and consistency were the keys to making it big in the burger world. Just watch a crew at your local McDonald’s; the burgers may not look like they do on TV, but if you buy one in Seattle it’ll look and taste just like one in San Francisco. And if you think running a restaurant doesn’t take incredible project management skills and/or processes, just follow a restaurant owner around for a day; or even for a dinner shift.
Project Management as we know it today (example 1, example 2) was founded in the government and by big business within the last hundred years or so. Employers were plagued by ever-present question as they grew larger: how do you control the work and resources for thousands of physically disconnected people (generally by location) while maintaining product integrity and profitability? It is all about making a buck, right? Right?
The pro’s of project management.
Project management is a wonderful tool that enables medium and large-scale efforts from slipping into a morass of ill-conceived “features”, maintain a semblance of fiduciary responsibility (stay on budget), assign responisibility to appropriate departments, and forge a template for similar projects in the future. Most project management methodololgies take a linear approach to the development process, defining specific milestones that will ideally lead to the successful completion of the project. Such milestones are often general in nature, such as:
With a smart team, a good PM, a detailed and accurate project plan, and enough sign-off from up on high (management), the product should come in on time, on budget, and will accomplish all of the goals and objectives of the project during the milestones given.
The con’s of project management.
Visions of reams of paperwork, long productivity-leeching meetings, and a general derth of anything remotely interesting (or, surprisingly, productive) are all heralded by the moniker of project management. Tech’s who’ve been around the block a few times will understand the importance of specs, but will more often than not feign death before willingly attend and/or comment on any of the fineries that accompany a project (read: meetings). Nothing makes a developer cranky like having to write a technical spec when they can write the actual code instead; and how can you blame them? Their job is to develop code, not essays on what the code will do (though hopefully they’ll comment their code).
Most meetings are generally over-bloated with people who don’t need or want to be there, and the hours spent talking are hours that aren’t used for doing the work that is being talked about. Jeff Bezos, of Amazon.com fame, was smart enough to implement “Two pizza teams” at Amazon, in which a team is too big if 2 pizzas couldn’t feed all members. Meetings should be run the same way.
Using the right tool for the right job.
Ask any carpenter, mechanic, or plumber and they will readily extoll the benefits of using the right tool for the right job… you wouldn’t use a jigsaw to stop a pipe from leaking, would you? The same principle applies to project management. But too often a process for project management will be thrown at a task that isn’t well suited for it and ruins the fun for everyone; and by fun I mean productivity and profitability. Like all humans, PM’s tend to take what they know best and mistakenly apply it wherever it may (or may not) fit. Do you really need a Six Sigma Black Belt or a certified PMP to get a corporate blog off the ground? Doubtful at best. Do you need one to manage the creation of a new production line for an auto manufacturer? I’d be surprised if the answer wasn’t yes.
My view on project management.
I’m sure that proponents of project management and their adherants are probably readying their typing their fingers to flame-on with this post, but please don’t take this as a knock on the fine work that they do. Project management is a great tool when used correctly and can help keep focus on what’s truly important with any project where products and/or services are being created. But it should be done when and where it’s appropriate, and it’s not necessarily appropriate for every single task that comes down the pike.
Small projects don’t need to be tracked within an inch of their life. Proof-of-concepts and models don’t need to be micromanaged. In most cases, a small team of creative and intelligent people should be able to take control of a task and come up with an outstanding product in less time and with less hassle than if it were put through the project management paces. And you did hire creative and intelligent people, right? Let them do the jobs that you hired them to do; the jobs that they want to do (and well).
Look at the history of some pretty swanky companies like Google, Yahoo, SixApart, and Flickr… all of them started with just a few outstanding people, a great idea, and a drive to succeed. Do they have PM’s now? Maybe. But that first core product that was pushed out the door that people grew to rely on… I’ll bet it didn’t.
Smart people can, if given the opportunity, manage themselves and create all sorts of wonderful things. That’s what I believe, at least.
Several big things happened today around our house:
OK… the last one isn’t that big of a deal, and it’s taken me long e-damn-nough to finish the fence. But the rolling over and having kids asking if Evan can play; that’s big news.
My friend Greg and I are always talking about all aspects of development, and something that I’ve always thought is much more elegantly described in the following quote:
It is worth remembering that a new programming language is sometimes viewed as a panacea, especially by its adherents; however, there is no one language that will supplant all the others, no one tool that is unarguably the best for every possible task. There are many different problem domains in the world, and there are many possible constraints on problems within those domains.
- Hal Fulton (in “The Ruby Way”).
Now that’s what Willis was talkin’ ’bout.
I believe that it’s not the language, specifically, that is used that will determine the success of a (software) development project; it’s the design of the system as a whole and the considerations made in the Planning and/or Analyze phase of the project.
I really bothers me when I hear people (developers are people, aren’t we?) saying “You must use OOP for this…”, or “Java is the best for that…”, or anything even vaguely similar to those sentiments. A poorly designed application using Ruby will fail just as miserably as one using PHP or Java. I primarily develop in PHP, but I know that it’s not the best choice for everything… I wouldn’t even suggest that it is; but when techno-religious zealots rise up from their pulpits it gets me spun up like mad!
And it’s not just developers; it’s folks in the Program management world, as well. Take software development and the oh-so familiar Software Development Life Cycle (SDLC). Software development and web development are not the same: stop treating them like they can be managed the same way. Sure there are similarities, but there are huge, gaping chasms of differences as well. You cannot take the same processes for software and expect them to work every time in a web development project.
I guess I’m done with my rant now… Oh, and for the record, Grefo, I’d like a strawberry PB & J.
Ah… there’s nothing like a smiling baby in your arms. Or in this case, your wife’s arms.
I’ve been looking to buy a digital camera recently so I checked Google for reviews, I poured over hundreds of Amazon.com product pages for features, and I searched high and low for folks who had/have owned digital cameras and sought their help. Tonight I made a purchase at my local Best Buy; a Sony DSCP200 7.2MP digital camera.
I talked the ear off the poor guy at the digital camera desk at Best Buy, and I’ll bet he was sorry that he asked me if I needed any help! He was very informative and wasn’t pushy about anything at all, which was nice. After about a half hour of questions, specification/feature comparisons, and in-store demoing I had my camera. I even bought the extended warranty, which I usually don’t, but the $60 for 4 years of service seemed like a good deal, especially with all of the features the service has (like if it’s not in pieces, they’ll replace it).