You’ll find many blogs listing recommended reading for developers, including my own: 6 Books Every Programmer Should Own. I thought I would come up with a list for Project Managers and Business Analysts that go beyond what they would teach you in the Project Management Body of Knowledge.
You will notice that many of these books were written prior to 2000, but their content remains relevant.
Rapid Development: Taming Wild Software Schedules
Rapid Development points out several mistakes that project managers and project teams consistently make that end up causing projects to fail.
Frederick P. Brooks Jr.
Brooks exposes several myths of running projects such as: adding people to a project doesn’t shorten the completion time, and the silver-bullet solution that will solve all problems.
Peopleware: Productive Projects and Teams
Tom DeMarco & Timothy Lister
The main theme in this book is that it’s people who make a project successful – if you take care of your good people, success will come.
Software Requirements 2
You’ve probably seen the classic tree swing cartoon (), effective requirements gathering is what can prevent these differences from happening. Quality requirements come from spending quality time upfront and effectively communicating throughout the process.
Software Project Survival Guide
This is the second book on this list written by Steve McConnell, you’ll also see him mentioned among the books for developers. This guide is “No Silver Bullet”, but it is an approach that typically will work for you most of the time.
What other books do you as a Project Manager or Business Analyst have on your bookshelf that have acted as your bible?