
How to plan and run software development to keep schedules under control.
Chosen by shared topics, the entries that hold them, and the people who recommended both.
Lessons from IBM's OS/360: why adding people to a late software project slows it.
“Arguably the only classic book in our field. If you haven't read it, shame on you.” — Jeff Atwood
Source: Recommended Reading for Developers — Coding Horror
Recommended by: Jeff Atwood, Mohnish Pabrai, Paul Graham and 4 others
Essays on software development from a popular programming blog.
Recommended by: Ev Williams
Managing people, teams and projects for an effective organisation.
“If you've ever seen the performance of an all-star sports team suffer due to poor coaching, you'll appreciate this book. It doesn't matter how many "coding superstars" you've got when none of them can talk to each other, or agree on anything. No developer, however talented, can work effectively when constantly being barraged with minor interruptions.” — Jeff Atwood
Source: Recommended Reading for Developers — Coding Horror
Recommended by: Jeff Atwood, Drew Houston, Marc Andreessen
How to find, interview and hire good software programmers.
Recommended by: Ev Williams
A novel in which an IT manager rescues a failing project using lessons from The Goal.