in reply to Retaining Top Developers

Hi samizdat,

What kind of answers are you expecting: economic impact studies, team morale impact studies, productivity impact studies, ...?

In any case, here are some links that might help you in your quest:

You should also have a look (if you haven't done so already) at On Finding, Hiring, Inspiring and Keeping

Cheers,

lin0

Replies are listed 'Best First'.
Re^2: Retaining Top Developers
by samizdat (Vicar) on Jun 28, 2007 at 19:58 UTC
    Thanks, lin0!

    I'm mostly concerned with the business costs associated with defects that would not have happened, schedules that would not have slipped, and late hours that would not have happened to make up for the loss. Standard HR metrics for "hiring replacement costs" exist, but they do not tell a fraction of the whole story, espeically in terms of senior software and firmware developers. The developer.* story was very insightful, and in words, it said what needs to be said. I've added it to my list, but some more numbers would be helpful.

    Don Wilde
    "There's more than one level to any answer."
[reply]
[reply]

In Section Meditations