Quality Software Management: Systems Thinking (Hardcover)

by Gerald M. Weinberg (Author)

Editorial Reviews

Review
"This is one of those landmark books that comes along at the right time and addresses the right set of issues." -- Shel Siegel, CASE Trends

"Weinberg addresses more clearly the form and essence of quality that we software people worry about." -- Ed Yourdon, American Programmer

Product Description
In this first volume of the Quality Software Management series, Gerald M. Weinberg tackles the first requirement for developing quality software: learning to think correctly -- about problems, solutions, and quality itself.

Guidelines on management are introduced to stimulate the kind of thinking needed.

Product Details

• Hardcover: 336 pages
• Publisher: Dorset House Publishing Company, Incorporated (September 1991)
• Language: English
• ISBN-10: 0932633226
• ISBN-13: 978-0932633224
• Product Dimensions: 10.1 x 7.2 x 1 inches
• Shipping Weight: 1.7 pounds (View shipping rates and policies)
• Average Customer Review: 4.7 out of 5 stars See all reviews (6 customer reviews)
• Amazon.com Sales Rank: #199,402 in Books (See Bestsellers in Books)

  Popular in this category: (What's this?)

  #10 in

  Books > Computers & Internet > Programming > Software Design, Testing & Engineering > Quality Control

Customer Reviews

Most Helpful Customer Reviews

37 of 38 people found the following review helpful:

5.0 out of 5 stars Get it and read it., November 23, 1999

By	James Bach (Front Royal, VA USA) - See all my reviews

This book holds a special place in my heart. It's the first technical book I ever read in one sitting.

I've been in the software business since 1983. By the time I encountered Quality Software Management in 1992, I was thoroughly cynical about books about software project management. By and large they were, and still are, preachy tomes that quote unverifiable statistics and make dubious claims about "right" and "wrong" processes. Grow up, guys!

Jerry's books are different, and this is my favorite of all of his books. As I read QSM, I didn't feel preached at or condescended to. I felt like, for the first time, someone was offering me ideas for coping with the very difficult problems that face those of us who work on projects where we don't have enough time, enough information, enough skill, or enough money to do a perfect job of anything. Given our limitations, we have to make tradeoff decisions in light of the best understanding of cause and effect we can muster. That's exactly what my organization was trying to do, in '92, when we were competing and winning against Microsoft (oh, they eventually beat us by hiring away the top third of our team, but that's another story). We just thought of ourselves as pragmatists, but when I read QSM I realized that our approach was also scientifically sound.

Looking back, I see QSM as one of the handful books in this field that actually helped me to become more expert at my job, and it's the first book I suggest to anyone who is serious about software quality assurance or software project management.

Get it and read it.

11 of 12 people found the following review helpful:

5.0 out of 5 stars A most enlightening introduction to quality., June 13, 1998

By	Ned Hamson "Positive Futurist" (Cincinnati, OH USA) - See all my reviews (REAL NAME)

I am not a software developer. When I stumbled across Gerry's book, I soon realized that I had found a hidden treasure. It contains within it the best definitions of quality that I have ever read. And he has a great sense of humor that helps make the lessons and insights you will get from the book easier to take. PS: His other books are equally great and should be read by software folks, as well as everyone else. Ned Hamson, Senior Editor, Association for Quality and Participation.

10 of 11 people found the following review helpful:

5.0 out of 5 stars Examine how you think about software development, May 13, 1996

By A Customer

Why is software development so often plagued by crisis? Weinberg helps the reader step back from developing software and examine the dynamics and patterns of software creation. By discussing patterns of quality, patterns of managing and patterns of software faults, the author shows that quality software begins with keen observation and clear thinking about software development. The text is extremely thought-provoking and is spiced with anecdotes drawn from decades of software experience. When my software team considered the book in a study group last year, our insight into our efforts and understanding of each other took a leap upward. Highly recommended