Fashion Sale Hier klicken calendarGirl Prime Photos Philips Multiroom Learn More saison Hier klicken Fire Shop Kindle PrimeMusic Lego NYNY

Kundenrezensionen

4,7 von 5 Sternen6
4,7 von 5 Sternen
5 Sterne
5
4 Sterne
0
3 Sterne
1
2 Sterne
0
1 Stern
0
Ihre Bewertung(Löschen)Ihre Bewertung


Derzeit tritt ein Problem beim Filtern der Rezensionen auf. Bitte versuchen Sie es später noch einmal.

am 24. November 1999
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.
0Kommentar|Eine Person fand diese Informationen hilfreich. War diese Rezension für Sie hilfreich?JaNeinMissbrauch melden
am 13. Mai 1996
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
0Kommentar|Eine Person fand diese Informationen hilfreich. War diese Rezension für Sie hilfreich?JaNeinMissbrauch melden
am 6. August 1998
While I generally like Weinberg's more humanistic take on managing software, sometimes I feel like his lack of rigor is a detriment. His strategies and ideas are all well and I good, I agree with them completely, but his models are often too vague and he usually doesn't provide the beleaguered manager with much to go on besides platitudes. Overall I would say there isn't much (if any) new information in this book. Of course, I guess that depends on what other books you have read prior to this :-)
0Kommentar|Eine Person fand diese Informationen hilfreich. War diese Rezension für Sie hilfreich?JaNeinMissbrauch melden
am 28. April 2016
Weinberg geht auf viele Themen mit überraschenden Ansätzen ein und das praxisrelevant.
Zum Shop auch noch: Alles sehr in Ordnung. Früher als angekündigt geliefert. Verpackung OK. Preis sehr gut. Bin sehr zufrieden und kann den Shop sehr empfehlen.
0Kommentar|War diese Rezension für Sie hilfreich?JaNeinMissbrauch melden
am 21. März 2010
In the first volume Jerry provides the cultural pattern model and relates it to the CMM levels and other approaches taken. Interestingly his view includes the culture around the people actually producing the software in first place, while other models focus on anything else but the people. First and foremost, Jerry defines quality as "value to some person". Based on this definition, the question we have to ask in software development - which I define as programming, testing and delivering - is whose values counts most to us.

Additionally Jerry introduces the reader to systems thinking. That is a model to think through difficult and maybe complex situations in software projects. He shows many graphs applying systems thinking, thereby creating deep insights into each of the cultural models, as well as the dynamics around the creation and maintenance of software.

Using systems thinking Jerry introduces the non-linearity of aspects in software development. He revisits Brook's Law and generalizes it to hold not only for late project, but for any project, when adding people, you're making it more complicated, and maybe even later.
0Kommentar|War diese Rezension für Sie hilfreich?JaNeinMissbrauch melden
am 13. Juni 1998
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.
0Kommentar|War diese Rezension für Sie hilfreich?JaNeinMissbrauch melden

Haben sich auch diese Artikel angesehen