Death March

Death March by Ed Yourdon.

"Death March", by Ed Yourdon. Most of the reccommended books In this thread are about trying to keep a project in a good place. This book is about what to do when it has already gone wrong. You can make a not terrible argument that much of the industry has gone to an all-death-march-all-the-time model. This book can help.

"Death March", Yourdon. Doomed software projects - how to recognize and deal with them, and sometimes use them to your advantage. "Software Craftsmanship", McBreen. Take pride in your work.

1. Mythical Man Month - obvious reasons 2. Deathmarch: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects- also a classic. 3. Thinking fast and slow - a great introduction to biases that will affect your thinking in any project. 4. The Art of War - strategy and tactics for attacking any problem. My personal favorite translation is by Thomas Cleary.

I've had to make up for a college education so these may be old hat. Alan Kay's UI lectures: http://webcast.berkeley.edu/course_details.php?seriesid=1906978270 Ed Tufte, especially Envisioning Information Structure and Interpretation of Computer Programs (SICP) http://www.swiss.ai.mit.edu/classes/6.001/abelson-sussman-lectures/ Ed Yourdon: Death March... this is a great guide to dealing with enterprizey development. This shows you what to avoid in your own org.