Long IT: final

Didn't change much from the original outline. I've posted links to all entries on the "Other Research" page. Here's the final outline with detail not already given:

Obligatory credentials page

• BS: RIT; MS: Cornell; PhD in progress: UMSL
• 25 Years Engineering/IT experience
• Have lead 5 “Ultra” projects (> 1 year)
• Currently Technical Lead at RGA
• Former pro bicycle racer and current ultrarunner

Distance running

• Short distance: 800m - 3000m
• Negative splits, big kick at the end, tactics
• Unsustainable effort levels
• Think "live production failure"
• Middle distance: 5K - 15K
• Even or slightly negative splits, strategy is where best to push
• "Normal" IT project space.
• Long distance: half to full marathon
• Even splits, attrition
• Key is moving well through the last quarter of the race
• Major IT projects with active project management and steering committee
• Ultras: 50K+, 100 miles is "standard" distance
• Varying/erratic splits, recovery is part of the race
• Long (> 1 year) efforts that constitute significant interruptions to career
• Requires that turnover planning, career development, promotions be built into project plan

A few slides contrasting marathons and ultras. Not indicating that one is necessarily harder, but that they require a different mindset.

The "10 Rules" slides.