Yesterday I listened to two of my colleagues who are actively "designing" our internal development processes. The one said "have you read DeMarco's 'The Deadline' ? Great book". The other one responded. "Oh yes, certainly, I recently finished 'Waltzing with Bears'. Great stuff". The conversation went on and on with exchanging project management book titles.
I've also read both but wasn't really that impressed because most of the advices sound great theoretically but reality often strikes badly. One of these colleagues worked the whole last year on a component in our system which is obviously over-engineered (more about that in later posts). He was so busy to stay to the process ("this is the design which you all voted for, now live with it" or "you can't have that feature, it isn't on the list of the original requirements") and the project really went from green to red as the component really munches memory like Godzilla (which is quite crucial in the embedded world).
Now I'm the one who is trying to cope with the beast. And I think: DeMarco's advices don't help here ! You must go way back to the bytes and carefully fix the design flaws with a very tight schedule.
So I really wanted to shout at them "Read this instead !
" and you will get good project managers: