I've recently received a book I ordered off Amazon:
"Code Leader: Using People, Tools, and Processes to Build Successful Software" by Patrick Cauldwell.
I'm really enjoying reading it. It's been a while since I've got my hands on a book that talks about the very important non technical aspects of writing software. Forget about cool new technologies, languages and libraries that will do everything for you. That's not what makes successful software. Its people working well together that make good software. The book give practical approaches to implementing Test Driven Development and Continuous Integration, talks about what it means for software to be done, Testing, Source Control and more in a practical context. Everyone more or less knows what has to be in place to deliver good software, but implementing these processes is not always as straight forward as it seems. The book talks about the What (needs to be in place), the Why (it needs to be in place) and the How (to put it in place).
So far i'm very exciting about Continuous Integration and CruiseControl.NET which can be used to set it up. I've been trying to get a setup going myself using Subversion for Source Control, MSBuild and MSTests. The following pages have helped:
http://www.testearly.com/2007/06/20/running-mstest-against-net-20-on-cruisecontrolnet/
http://msdn.microsoft.com/en-us/library/7z253716.aspx
http://paltman.com/2006/12/06/3-steps-to-integrating-cruisecontrol-with-msbuild-mstest-and-code-coverage/
