Blog moved. Please update links. 3
I’ve moved web hosts and decided it was time to relaunch my blog as well as rechristen it ’Full Fathom Five’. It was also a good opportunity to smoke some of that red coloured crack (a.k.a. Ruby) by way of Typo.
Please update your feed links. The old feeds will stay valid for some time but will not reflect new posts.
New feeds can be found at:
Sincere thanks to Neale at Metawerx for 2 years of excellent customer service hosting my Java-based blog. Thanks also to Simon Brown for Pebble, my faithful blog web application for the last year or so.
Challenges - knowing when to say no 1
Many dynamic and energetic developers I have known share a characteristic of reflexively accepting the challenges put to them by their organisation. I think many people are just wired that way - they are presented with a challenge and their sense of self worth or their desire to please or whatever it is compels them to accept it; and beat it.
What do you do when the challenges are nonsensical, not worth doing or based on clearly broken assumptions. In a ‘can do’ culture that places a high value on ‘being pro-active’ a challenge can often take on mystical properties that make it unasailable and immune to rational questioning or discourse. If it was uttered thus must it be worthwhile.
It takes a lot of guts to say to someone (especially someone you report to or someone in a position of substantial power) “your challenge doesn’t make sense, I refuse to accept it”. In such organisations rejecting a challenge is often worse than failing the challenge itself and you may run the risk of being labeled a recalcitrant, nay-sayer, lazy or worse.
If a friend came to you and challenged you to invent a perpetual motion machine, would you accept or reject the challenge? Kooks aside, most of us would reject it and we wouldn’t judge ourselves by the standards of the challenger - we’re not failures because we refuse to invent a perpetual motion machine. We know it’s sheer folly.
Organisations should do the same when they’re forced to into a Mythical Man Month scheduling ‘challenge’ by overzealous upper management eager to make their mark. Adding manpower to a late (or tight) project will just make it later (or tighter) and we shouldn’t be afraid to rebuff a challenge to come up with aggressive project plans based on the assumption that “men and month are interchangeable”. This, too, we know is sheer folly.
Technorati Tags: development, management, Mythical Man Month, projects
