red hot developer model
Let's face it: the larger, more complex and more demanding a project gets, the more distractions your various teams face. From various maintenance tasks, to "identifying the developer who's broken a build" type of tasks, to answering all those questions from different teams, that just keep piling up, to figuring out what's the deal with all those errors in the log files that keep coming up and everyone's stubbornly shutting their eyes to... these are all distractions that keep stacking up as a project grows. And which can grow into some major productivity drains. So how do you minimize them?