". . . full of good advice on what institutional and team policies
help to promote good software practices among engineers. . . .
this book is aimed at managers, as with most books of this nature, all levels
of engineers can benefit by reading it. You can use the tips in this book to either
improve your own engineering culture, or to identify the problems in your group,
that you just haven't quite been able to put a finger on."
". . .
the book leads you through the phases of system development, focusing on practical
problems and suggesting project-oriented solutions that use modern, proven methodologies.
Even though Wiegers clearly has preferences, he also provides excellent, well-written
descriptions of alternative methodologies."
"This book is essential
reading for anyone responsible for systems development and, even more importantly,
for anyone responsible for managing teams of systems developers. Well written
and easy to read, it is filled with information that will definitely help improve
your products' quality."
"The most important thing this book does
is make you aware that the software engineering culture within your organization
is critical to the success of development projects.
". . . Karl Wiegers
writes using a practical manner that leaves you asking for more. A must-read for
anyone interested in improving the way they develop software."
the book, every step in the process, from the first idea down to the post release
bug fixes, is stated, developed and critiqued from a team perspective. The author
is a software process engineer who has clearly learned from his experience, both
positive and negative."
Charles Ashbacher Technologies
Mathematics and Computer Education
"Firmly rooted in the
experiences of its author, this book offers the reader not just practical ideas
of what to do, but also of ways to learn and think while doing them."
new book has a good chance of joining the select few books that top 100,000 copies
and become standard references for the software engineering world. What Karl's
book has in common with the classic software engineering books are these four
- It starts a new theme of important research or goes beyond
- It covers important and practical topics dealing with
- It is well written and easy to read.
includes real data rather than just the author's opinions.
sets Karl's book apart from the other treatments is that it deals with how real
people react to changes, to mandates, to new methods, and to both success and
failure in their work.
". . . not just a theoretical discussion of
how software engineering is supposed to work, but rather some informed observations
of how things really do work in an actual company that wants to improve software.
. . .
". . . a graceful writing style, clear illustrations, and a
very extensive set of bibliographic references. . . . a welcome addition to the
software engineering literature."
Software Productivity Research, Inc.
"I give it Four Stars! A book in which both managers and technicians can
find practical guidance in their common quest for a more productive, healthier,
and happier software development organization."
". . . an insightful description of a healthy
software engineering culture. His culture builder and culture killer tips present
good commonsense advice to both software developers and managers on how to evolve
a professional culture. . . . a very readable book."
Co-Founder and Chief Scientist