Software Build and Release Specialist

Software Build and Release has such a hectic schedule–sometimes you just can’t help it but to get caught in it all and get burned out.  Aside from a successful proposal of a new build and release infrastructure and getting all the development teams on board, the headache starts when the implementation and back-to-back release schedule begins.

Project after project, build after builds and releases gets implemented and soon the SCM team experiences what I would like to call the avalanche of legacy build project conversion requests.  Early adopters get to experience the bliss of a particular new build and release infrastructure and suddenly good words and reviews spreads like wild fire to other groups.  Soon every group within the developmental organization is knocking on the SCM group’s door asking to have their projects converted over.

So what do you do when business is good and the team seems like it can do no wrong?  You pay attention to the burnout factor of each of these overworked and overstressed SCM Engineers.  Offer telecommuting options or flex days (days off for extra hours worked), pay attention to each Engineer’s sentiments and get frequent feedback.  Failure to do so will be the quickest way to drive talented SCM Engineers out of the company and into the doors of your competitor.