Get the expert guidance you need to learn how to meet requirements and expectations, on time and on budget, with best practices for software development project management. Software project management can encompass specific methodologies, such as Agile, Scrum, CMMI, and IBM Rational Unified Process; specific tools, such as Microsoft- Visual Studio- Team System; or specific roles, such as architect, coder, tester, and project manager. But beyond the hot-shot code jockeys, the high-end equipment, and the time and budget available, one of the most important aspects of successful software development projects is management. Unlike other books on the subject, this book focuses on the critical manager role. Written by an expert with decades of experience and software development management expertise who has conducted extensive research on project management, this book shows managers how to lead a project successfully. And it shows how to manage for results without adopting philosophies from Genghis Khan or Machiavelli. (There is mention of Godzilla, however.) Drawing on best practices from allied industries such as business, psychology, accounting, and law, the broader methodology detailed in this book results in adaptable project management principles that help increase effectiveness and productivity. Packed with real-world examples, this book shows any development manager, new or experienced, how to successfully lead any software project.

Amazon.com® Reader Reviews (Ranked by Helpfulness)

Average Amazon.com® Rating:  Based on 3 Ratings

Software project manager? You will love this book! - 2008-07-31
Reviewer Rating:
Dr. Peters' book is the best project management book I have ever read (I've read quite a few). He has an easy style of explaining things, probably from his seminar delivery experiences. The book offers practical advice as well as explaining more complex tools, methods, and metrics. His real-life stories are quite good - many made me smile (been there, did that, seen that), but they also help make his points memorable.

This is a very serious book - essential reading for software project managers. Dispels the myth (or sometimes a personal self-delusion) that project managers just happen to be born with natural skills.

Although software project centric, it is broad enough to be of interest to anyone involved with technology projects at any level. It is recommended for upper management who might be interested in installing a "culture" of consistent project management disciplines (and successes). It might also be useful for HR personnel in screening candidates. Development team members will also benefit.

Manager-focused guide to great software results - 2008-08-17
Reviewer Rating:
This book is a guide for current and aspiring software project managers who would like to bring more determinism into their projects. Peters shows many statistics early on about the vital role of the project manager on the success of projects, and my own experiences agree with those. A good manager can help a mediocre team succeed; a mediocre manager will lead even a great team to failure.

There is fairly deep treatment of a variety of planning styles, project lifecycle models, and even information about how to best motivate your team. I particularly enjoyed the ties between what motivates people (like early involvement with planning and release date specification) and how that is an aspect of a variety of different planning frameworks. He also does a great job of providing specific examples of how to let the team, company, and situation help define the right process, rather than always doing exactly the same thing.

The only thing I didn't enjoy as much was the treatment of some of the more in-depth planning models. It felt like there was a lot of detail, but I still didn't come away with a good idea of where to get started with them if I wanted to use them immediately. A summary section at the end of each presentation with pointers to good "how to do it" books and tools (as opposed to the existing references to the definitions of them) would help. Also, some of the relative terms like small, medium, and large projects that he used to help with decision-making could use some clarification. After years of working at Microsoft, I still consider anything under a quarter million lines of code small, and it takes about 20 million to make a large project. I don't know how those numbers relate to his breakdowns.

Good but - 2009-02-17
Reviewer Rating:
I like the book.. but sometimes it jumps from amazing advices to purely technical or academic issues.