Books.org participates in affiliate programs including Bookshop.org and the Amazon Services LLC Associates Program. We may earn a commission from qualifying purchases made through links on this page, at no additional cost to you.
Overview
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.
"Contents include: People, Process, & Product; Visibility; Configuration Management; Process; Planning; Risk Management; Requirements; Design; Testing; Managing a Project Day by Day; Managing Software Maintenance; and more.
Synopsis
Bring a new level of effectiveness to your software projects
Remember when creating software was fun? It could be again, if you use the methods in this book to help you plan and manage your project. In this new edition of The Software Project Manager’s Handbook, expert Dwayne Phillips outlines the fundamental principles that project managers and software practitioners can use to help them succeed on any project.
Success on software projects has more to do with how people think individually and in groups than with programming, asserts Phillips. In clear and concise steps, he shows software project managers and their team members how to manage projects effectively by paying attention to four basic principles:
- Balancing people, process, and product
- Making ideas visible
- Applying configuration management properly
- Using standards
The book describes the requirements, planning, and risk management stages of the development cycle and examines the middle and late stages of development including design, test and integration, and maintenance. Phillips shares proven methods for dealing with common stumbling blocks for managers such as customers who want a voice in the design and endless test-fix cycles, and for planning maintenance so the customer is not left out of the process.
Finally, the author examines past projects in detail—demonstrating why some projects were successful and why others failed. Phillips helps you apply these lessons with a "cookbook" formula that walks you step-by-step through a Waterfall, an Evolutionary, and a Spiral project.
New material added to each chapter covers current issues including the role of process in software projects and the Agile Methods. The Software Project Manager’s Handbook, Second Edition is the most innovative and up-to-date guide to making every software project a complete and painless success.
Booknews
Project visibility and communication, proper configuration management, the use of standards, and a balance of people, process, and product are key in this approach to effective software management. The author describes the stages of the software development cycle--from requirements gathering and analysis, planning, and risk management to design, integration and testing, and maintenance. The final chapter presents case studies using waterfall, evolutionary, and spiral process models. Annotation c. by Book News, Inc., Portland, Or.
Editorials
From the Publisher
"…clearly explains what it takes to be a good software project manager...a first-rate information source for novice project managers." (IEEE Software Magazine, November/December 2005)
"...a useful book for the classroom or the workplace...I advise purchasing this book and applying the author's ideas." (Software Quality Professional, September 2005)
"...a good reference for individuals just starting off as IT project managers...For those preparing for the CSQE exam, this book can be a good reference..." (Software Quality Professional, June-August 2005)
"…helps guide software project managers and their team members in working towards common goals." (IEEE Computer Magazine, October 2004)