I would run through "Driving Technical Change" by Terrence Ryan for a few ideas. It's short and to the point:

http://pragprog.com/book/trevan/driving-technical-change

http://www.amazon.com/Driving-Technical-Change-Terrence-Ryan...