I've been invited to present my survival guide to death march projects to Think IT, a regional professional group. I've got quite a bit to do to put the whole thing together, but here's the general outline:
Using running races as a metaphor for IT Projects, we have:
5K: Trivial updates to existing products: single developer; maybe QA
10K: Incremental functionality: small team; short timeline
Half Marathon: Major releases: requires project management
Marathon: ERP Upgrades, platform rehosting, redesigns: requires steering committee
Ultras: Major new systems, Operational overhauls
This last group is fundamentally different. The marathon is the "longest short race", meaning it's the longest race where you worry about seconds. Beyond that, success requires a different mindset. In particular, an ultra can't be "forced". If it is, it turns into a death march and will fail. Adjustments have to be made in a way that allows forward progress to continue while keeping the goal in reach. Here are 10 strategies from the limits of human endurance that translate well to long IT projects.
1) Have a realistic Plan
2) Take walk breaks
3) Keep moving
4) Run fast (when not walking)
5) Take small steps
6) Refuel
7) Expect setbacks
8) Have a support crew
9) Use pacers
10) Hire women
That last one may come as a surprise to those who know how much I disdain preferential hiring. I'll explain as the topic gets elaborated over the next few weeks.
No comments:
Post a Comment