« Refactoring for Fun and Profit | Main | ServletTestHelper - you're my hero! »
September 16, 2004
Preaching to the Inconvertible?
My collegue Patrick and I have been pacing each other reading Peopleware recently, and I've just about finished when a thought occurred to me...
Who reads Peopleware?
The book explicitly claims it's principal audience are IT project managers, given the majority of the book discusses how poor application of PM can completely derail projects and the people associated with them. No doubt a secondary audience are people above and below PMs in your typical organization's food chain; upper management and developers respectively. Yet given the principal audience, I don't know of any project managers who have proactively read this book, only developers. This is surely due to the fact that my peer group are predominantly developers, but I do know a handful of professional PMs and some were even unaware of the title 'Peopleware'!
What does this mean? Well, it's possible that I'm associating with the "bottom feeders" of the PM gene pool (maybe I've fallen in with the "wrong crowd", as my Mum was so wont to say), but I don't think so. All of the PM's I keep in contact with are very good at their jobs, to a greater or lesser degree. Which leads me to another, more fundamental question?
Where are the PM geeks?
Most of my developer friends are what I would good-naturedly call "geeks". In other words, they view development much more as a vocation than a profession. Their commitment to development entends way beyond the normal work day and their current project. They spend a considerable amount of personal time indulging in their passion for technology, with the most obvious side effect that they're all extremely capable developers. They think nothing of reading books like Peopleware to gain a better understanding of what factors influence the nature of their projects and how best to maximize the positive ones whilst minimizing the negative. These behavioural patterns contain the true essence of a geek to my mind.
They also spend non-trivial amounts of time reading other developers' blog. So if you're reading this and were in the denial stage of accepting your geek nature, it's too late now :-)
But what of our PM bretheren? Is there such a thing as a PM geek? What activities do they partake to fuel their fire for all things PM-y? Do they volunteer to PM open source projects? Do their congregate to play Risk at the PMI every Thursday night? Do they have vast collections of PM text books? Do they read development text books (or even Leading Geeks) in order to better understand the people they manage and what makes them tick?
I'm not sure whether such a thing as a PM geek exists, saving people like Demarco and Lister and their peers. Maybe the lack of a tangible nature to project management work and the ready availability of a toolset (i.e., their equivalent of the developer's PC and software) prevents such evolution from being widespread in the PM crowd.
Given this, it is no wonder that books like Peopleware are created? If a 9-5 project manager is put in charge of a team of geeks, the impedence mismatch is so large that things are bound to get rocky sooner or later. Where a high performing team normally just needs to have a path cleared for it to get the work done, so many PMs insist on applying their cumulative knowledge to the letter of the law, thus almost guaranteeing friction between the developers and the PM.
And the solution? Buggered if I know, I'm just a geek.
Posted by Andy Marks at September 16, 2004 07:32 AM
Comments
PM "geeks" get their information from conferences and training courses, as a rule. Few tend to read these sort of books, however. This is one reason why DeMarco runs a lot of seminars.
I have to agree that Peopleware is a great book... I bought the 2nd edition a while back, but while I was waiting for it to arrive (via mail order), I found the first edition in a used book store. I liked what I read enough to not cancel the order... I wanted those extra chapters (and I wasn't disappointed).
My favourite section is the bit on the phones & voice mail. It really makes you think about the cost of phone calls in terms of interruption time. More and more, I find that if really want to get work done, I need to take the phone off the hook... not just my phone, but the phones of the people around me who aren't at their desk to answer their phones.
(What's really sad, of course, is that nearly invariably the person on the other end says "Oh, I'll just send them an email, then"... well why didn't they do that to begin with!)
Posted by: Robert Watkins at September 16, 2004 08:54 PM
There are a few wandering around. Try Clarke Ching : http://www.clarkeching.com/ or David Anderson: http://www.agilemanagement.net/Articles/Weblog/blog.html and just follow the links
Posted by: ade at September 16, 2004 11:00 PM
Andy, I think your post makes an interesting observation of our industry. I agree that there is a big difference between De Marco and Lister’s perception of their audience and their real audience and that there are at least two main reasons for this gap. The first is the assumption mistakenly made by so many companies that their top (and maybe not even that sometimes) software engineers will naturally make good PMs. The second is the presumption that any person from a business background will make a good PM.
Those who fall into the first category or might eventually be pushed into that category have good reason to read the book. Those in the latter category scare me a lot more because I imagine that most of their reading revolves around traditional forms of management theory (but I hope I am wrong).
Then again my reading on this area seems to suggest that good managers are so good at their jobs that you never really notice them doing it.
Posted by: Patrick at September 19, 2004 04:26 PM
Thanks for the links Ade - the agilemanagement one looks particularly interesting
Posted by: Andy Marks at September 20, 2004 09:34 AM
Post a comment
Thanks for signing in, . Now you can comment. (sign out)
(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)