Average Reviews:
(More customer reviews)This book covers Software Project Management broadly with a lot of good information for both the new project manager as well as the old hand.The material is presented as a comprehensive overview rather than a detailed instruction.By itself the book does not go deeply enough into any of the areas to provide a novice with enough useful information so it's a good book to use in conjunction with books providing more detail.
Despite its lack of detail, the book presents many important points - the importance of the human equation, analysis/organization tools such as Tony Buzan's MindMap, having a Management Information Center, and using standards without having a programmer's revolt.There is only passing mention of key issues such as scope creep, the tendency of management to try to throw more personnel at a project in trouble, needing to build testing into the initial design process, and the pro's and con's of the various development methods (waterfall, spiral, etc.). A number of references are quoted, including many IEEE documents (IEEE is the publisher) plus books by Gerald Weinberg, Capers Jones, Tom Demarco, and other recognized gurus - which make good adjuncts to this handbook.
Phillips perpetuates one of my pet peeves, the issue of including the top ten risks in the risk assessment document.What if there are only 7 risks which seem to be significant?What if there are 12?Granted, it would be unwieldy to track & evaluate dozens of risks routinely, but it doesn't make sense to suggest that exactly 10 be tracked.
The discussions of Configuration Management are quite lengthy and in a bit more detail than other topics covered.
Although the book is fairly short at 500 pages and is easy reading, there is a substantial amount of information covered. The 5 star rating is for the breadth of information covered, with the caveat that other references would be needed by those unfamiliar with the concepts presented.
Click Here to see more reviews about: The Software Project Manager's Handbook: Principles That Work at Work (Practitioners)
Product Description:
Software project managers and their team members work individually towards a common goal. This book guides both, emphasizing basic principles that work at work. Software at work should be pleasant and productive, not just one or the other.
This book emphasizes software project management at work. The author's unique approach concentrates on the concept that success on software projects has more to do with how people think individually and in groups than with programming. He summarizes past successful projects and why others failed. Visibility and communication are more important than SQL and C. The book discusses the technical and people aspects of software and how they relate to one another.
The first part of the text discusses four themes: (1) people, process, product, (2) visibility, (3) configuration management, and (4) IEEE Standards. These themes stress thinking, organization, using what others have built, and people. The second part describes the software management principles of process, planning, and risk management. Part three discusses software engineering principles, the technical aspects of software projects. The fourth part examines software practices giving practical meaning to the individual topics covered in the preceding chapters. The final part of this book continues these practical aspects by illustrating a sample project through seven distinctive documents.
Get 10% OFF
Want to read more honest consumer review about The Software Project Manager's Handbook: Principles That Work at Work (Practitioners) now ?
0 comments:
Post a Comment