This handbook summarizes more than 50 of the major problems of building and maintaining software projects, and outlines the prevention/control “therapies” available. KEY TOPICS: Considers in depth the software-related risks in the domains of methodologies, tools, organization structures, skills and specialization, client relations, and sociological issues. For software managers and software professionals in software engineering, software quality assurance, and related software areas. |
Average Customer Review:
 ( 5 customer reviews )
Write an online review and share your thoughts with other customers.
Most Helpful Customer Reviews
36 of 36 found the following review helpful:
 'Cure' problems with your Software Development Life CycleMar 21, 1997
The author proposes that we categorize software development risks like the Center for Disease Control categorizes disease. He builds on this theme by discussing risk from the perspective of symptoms, susceptibility, prevention, and therapies. The information is excellent., and is not available in this compact format from any other source (at least that I know of). This book is a 'must' for any manager intent on improving the system development life cycle. /// This book is primarily directed toward knowledgeable software professionals. It assumes you have a good understanding of development theory. Unfortunately, since the book was written in 1993, some information (related to vendor tools and products) is a little long in the tooth. That is the only reason I didn't give the book a rating of '10'. /// I would love to see a yearly update that included new symptoms, new 'diseases', additional therapies, and updated lists of vendor 'cures'. Overall content is first-rate and very relevant, not theoretical. The hard part -- detailed therapy -- is properly left to the reader, but several options are presented
9 of 9 found the following review helpful:
 Could be updatedMay 25, 2002
By Todd M Johns
The book is a great resource for brainstorming potential risks to your projects and strategies to handle them. Almost all are timeless. However, the book is 10 years old and much has changed over the last 10 years. The Internet is a prime example. This new medium has most of the risks of legacy systems, but the Internet brings new possibilities and new expectations.
9 of 10 found the following review helpful:
Still quite valid in all respects (unfortunately)Aug 26, 2002
By Mike Tarrani
"Jazz Drummer"
While an update to this book would be nice, the fact is that the major risks cited in this 1994 classic continue to be risks in 2002. What I like about this book is the way it's organized and structured. Jones starts with two chapters that highlight the most common and the most serious software risks. In that respect the essence of the book is provided up front.The rest of the book is a catalog of the top 43 risks, presented in a quasi-pattern format (that predates the GoF patterns movement), using a medical metaphor, based on the US Public Health Service publication titled "Control of Communicable Diseases in Man" as the pattern. The format is highly effective and intuitive, and also plants a subtle notion that the risk can be cured. The risks are arranged alphabetically for easy reference and range from Artificial Maturity Levels to Slow Technology Transfer, with the usual suspects that have plagued software engineering since its inception: corporate politics, excessive schedule pressure, low user satisfaction, malpractice (project management and technical staff), silver bullet syndrome ... sound familiar? In my opinion, until cures are found for the risks cited in the book we, as a profession, don't need an updated list of more. I strongly recommend this book to anyone who manages software engineering projects or processes. If you want a more condensed version of this book get Jones' "Software Systems Failure and Success", which was published in 1996. That book distills critical success (or failure, depending on your perspective) factors into a manageable group of twelve attributes. It doesn't fully replace this book, but does augment it well.
Complete and to the pointJun 15, 2010
By Sergio
This book is quite complete for anyone needing to deal with software risks and its organisation makes it particularly handy. It is a marvelous reference book when tackling complex projects, re assessing risks or trying to find out what went wrong. As a bonus it brings broad references of all resources that can be leveraged on each specific risk.
Assessment and Control of Software RisksNov 19, 2009
By Kirk Stephan Kalvar
If nothing else read the chapters on "Malpractice (Management)" and "Excessive Schedule Pressure". This book should be required reading for any project managment.
|
based on 5 reviews
