Managing Risk: Methods for Software Systems Development 1st Edition, Kindle Edition

3.3 out of 5 stars 7 customer reviews
ISBN-13: 978-0201255928
ISBN-10: 0201255928
Why is ISBN important?
This bar-code number lets you verify that you're getting exactly the right version or edition of a book. The 13-digit and 10-digit formats both work.
Scan an ISBN with your phone
Use the Amazon App to scan ISBNs and compare prices.
Kindle App Ad

Deliver to your Kindle or other device

Buy for others

Give as a gift or purchase for a team or group. Learn more

Buying and sending eBooks to others

Single copy
(Sent by Amazon)
Amazon emails the eBook to a recipient on your behalf.
Learn more

Multiple copies
(Send on your own)
You send redemption links to your recipients.
Learn more

These ebooks can only be redeemed by recipients in the US. Redemption links and eBooks cannot be resold.

This item has a maximum order quantity limit.
See all 2 formats and editions Hide other formats and editions
New from Used from

The Amazon Book Review
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
click to open popover

Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.

  • Apple
  • Android
  • Windows Phone
  • Android

To get the free app, enter your mobile phone number.

Try Kindle Countdown Deals
Explore limited-time discounted eBooks. Learn more.

Editorial Reviews

From the Inside Flap

The growing pains of the software community continue with the increased demand for software systems. The fact that software, the code developed to execute in a computing system, is pervasive in todayIs society is both a problem and an opportunity for managers and engineers. Many software professionals see the problems, but only a few see the opportunities. Problems that cause projects to be late, over budget, or of poor quality are collectively known within the community as the software crisis. Application of traditional problem solving methods to solve the software crisis has been U for the most part U ineffective. The source of the software crisis is the project, process, and product risk that turns into problems because risk management is not done. Risk management differs from traditional problem solving, for the simple reason that a risk is not a problem. By analogy, risk management is to a risk what an algorithm is to a problem. Whereas problems may be solved by application of algorithms, a risk may be resolved by application of risk management.

Software-risk management is a practice to resolve risks that affect the software project, process, or product. The purpose of Managing Risk is to help people responsible for software systems to acquire the knowledge necessary to apply software-risk management. This book provides a handy reference to help busy professionals assess and control software risks.

This book will enable you to answer the following questions: What does it take to manage software risk? What is my current ability to manage software risk? How can I increase my ability to manage software risk? This book is a practical guide for managing software risk that is easy to use. It describes an approach to manage risk based on proven practices. Whether your level of expertise in managing risk is novice, beginner, intermediate, advanced, or expert, the five stages of risk-management evolution ensure that you know where to start your journey.

Because risk is defined as the possibility of loss, traditional works often portray risk with a negative connotation. This book is distinctive in that it has a broad and positive perspective on risk. Risk has long been associated with unmet reliability, safety, and security requirements. Although these requirements are important applications of risk concepts, they do not preclude managing risk to satisfy any other requirement U such as profitability, reusability, and quality. This book makes no assumptions about what your requirements are; it simply encourages you to take a broad view of managing risk to satisfy your requirements and achieve your goals. This book does not judge the consequence of a risk. Instead, risk is reframed in a positive manner; opportunity cost is viewed as a loss. A broad and positive perspective of risk challenges us to exceed expectations through possibility thinking: How can we manage risk to benefit from the enormous opportunity that exists today in the field of software?

This book is written for people who manage and develop software systems, including those who hold the responsibilities for oversight and improvement of a software project, product, or process. I assume that you are a busy professional, interested in maintaining a competitive advantage for yourself and your organization. Your job could be one of these: Senior manager, responsible for management of an organization that has a core competency in software. Engineering manager, responsible for functional management of technical individuals who develop or maintain software systems. Project manager of software systems acquisition, development, or maintenance. Software manager, responsible for directing software teams. Systems engineer, responsible for meeting the technical requirements of software systems. Software engineer, responsible for large-scale software development or maintenance. Quality-assurance specialist, responsible for verification of process and product compliance using risk identification and problem prevention as a proactive strategy. Measurement analyst, responsible for either short term or long term measurement of software projects. Engineering process-group or process-action-team member, responsible for organizational technology transfer, process definition, and process improvement. Change agent, working with software organizations as a corporate trainer. Process consultant, performing risk assessment and risk management for clients within the government or commercial software sector. College professor, teaching software-project management or risk management. Book Overview
The book is divided into five parts that describe a risk-management roadmap designed to take you from crisis to control of your software project. The path to increasing your ability to manage risk is shown through progress in four synergistic dimensions of people, process, infrastructure, and implementation. These dimensions provide a separation of responsibility and focus that map to the specialization of the roles required on a software project. Parallel efforts in each dimension may speed the transition of risk management in your organization.

Each book part is introduced with a brief overview that summarizes the key topics covered in each Chapter, and why they are important. These five parts are: Part I, Risk-Management Discovery, lays the foundation for understanding the role of risk management in Part II, Risk-Management Process, elaborates the activities to perform risk management using a standard process-definition notation. Process steps, inputs, and outputs are fully defined. Methods and tools used by the process are shown by example. The process dimension describes the steps to predictable risk management results in terms of what and how. Engineering process-group or process-action-team members and process consultants can appreciate this reusable process component. Part III, Risk-Management Infrastructure, provides the organizational foundation that supports the establishment of a risk-aware culture. Training metrics help you provide just-enough information just-in-time. Techniques for project oversight are included, as well as a method for establishing a baseline for quantitative process improvement. Without infrastructure, there is no strategic plan in place to institutionalize risk management. Senior managers, engineering managers, and change agents should benefit from these organizational building blocks. Part IV, Risk-Management Implementation, instantiates the standard process within a software project. Risk management activities throughout the lifecycle are planned, budgeted, scheduled, and staffed. The implementation dimension describes who, where, when, and why. The details of the risk-management plan are presented, with tailoring suggestions for the standard process. Project managers, software managers, systems engineers, and software engineers behind schedule may tailor this plan to quickly claim progress. Part V, People in Crisis and Control, describes different project teams whose practices formed the basis of the risk-management evolution stages. These case studies provide a wealth of experiences, ancedotes, and benchmark data from the 1990s. I had the opportunity to survey and study peopleIs perceptions of the performance and importance of their risk-management practices. Effective and ineffective practices were identified by project managers, engineering managers, configuration managers, quality assurance specialists, systems engineers, software engineers, test engineers, and the customer. These insights and lessons learned should be invaluable to people struggling to manage software-systems risk. How to Read This Book
The approach for reading this book depends on your job category, and your risk-management ability. Everyone should read Part I to provide the background for the rest of the book. Read Chapter 1 completely if you are a risk-management novice. Read Chapter 2 to learn the success formula for managing risk. Read Chapter 3 to understand the roadmap to increase your risk-management ability. Depending on your job category, Parts II-IV will apply. Read Part II if you are responsible for risk-management process definition or execution. Read Part III if you are responsible for establishing risk-management policy, conducting training, verifying compliance, or improving the process. Read Part IV if you are responsible for planning, tailoring, or performing risk management on a project. Everyone should read the case studies in Part V to benchmark their personal, project, and organization risk-management capability. As you read the case study that characterizes practices most similar to your own, you should be able to identify with the people and their behaviors. Note the similarities and the differences. More than likely, there will be differences due to individual risk preference, and your assessment of practices either above or below the level described in the case study. Read the following case study to help you determine the next steps in evolving your risk-management ability. You can use the questions at the end of each chapter to support retention and learning.

I would like to acknowledge the pioneers in the field of software-risk management for their foundational material. In order to add to the body of knowledge in this area, I stood on the shoulders of Dr. Barry Boehm, Dr. Robert Charette, and the Software Engineering Institute (SEI). Their ideas inspired me to develop risk-management methods for use by the software community.

Several managers were responsible for my process-improvement experience at Harris Corporation. Phil Henderson, as General Manager of the Information Systems Division (ISD), established the Software Process Team and funded the Software Engineering Process Group (SEPG) to improve the software engineering process. Hank Eyster, as division Director and Steering Committee representative on the Software Process Team, supported training and use of risk assessment and risk management on projects. Gary Natwick, who as SEPG Manager, recognized my enthusiasm for risk management and allowed me time to write articles and present papers. Those who worked with me on the Software-Risk Management Action Team were Clay Eberle, Jane Eden, Gary Natwick, Lon Hixson, Russ Hooper, and Steve Morris. Their cross-functional perspectives helped to evaluate and expand the current documented policy for risk management with a focus on practical-project implementation.

The benefits derived from the SEI efforts in technology transfer cannot be overstated. I was able to leverage their expertise to assist pursuits, proposals, and project teams in establishing effective risk management practices. Ken Dymond, Walt Lamia, and George Pandelios at the SEI Risk Program provided my early training in risk assessment. I am grateful for them, and others who contributed to the SEI Risk Program. Those with whom I worked to write a key process area for risk management were: Dr. Robert Charette, Dr. George Kambic, Roy Kimbrell, George Pandelios, and Charlie Weber. Those who made the SEI/Harris technical-collaboration agreement possible included Julia Allen and Clyde Chittister. For help in streamlining the risk-assessment process, I want to thank Carol Ulrich and Marvin Carr. Thanks to Mike Dedolph and Julie Walker for on-the-job training in Software Risk Evaluation, and Audrey Dorofee for training in the Risk Clinic.

My involvement in systems engineering process improvement through the International Council on Systems Engineering (INCOSE) has broadened my perspective in risk management. For those who discussed ideas with me including Dr. George Friedman, Dr. Jerry Lake, Jim Brill, and Dr. Larry Brekka, former Chairman of the INCOSE Risk-Management Working Group. Members who shared their experiences in risk management with me including Art Gemmer, John Hazelwood, Rudy Elam, and Bob Shishko. To members who contributed technical papers on risk practices to the national symposium, especially Dr. Dennis Beude for enlightening me on tools for risk analysis.

Many organizations contributed to the Department of DefenseIs Software Acquisition Best Practices Initiative. Those that shared risk practices included Aerospace Corporation, C&C Associates, Ceridian Corporation, Harris Corporation, Mitre Corporation, and Unisys. Norm Brown, initiative coordinator and Director of the Software Program Managers Network (SPMN), deserves the credit for condensing industrial strength software management strategies from the reported best practices. At the SPMN, I learned commercial best practices and the need for them to help meet defense needs at lower cost. The Airlie Software Council, especially opinion leader Tom DeMarco, deserves the credit for encouraging consensus that the number one best practice in software acquisition is formal risk management. I thank the attendees of my Software-Risk Management seminars at the Defense Systems Management College, and in London, Orlando, New Zealand, and Washington, D.C. for sharing their risks, questions, and improvement suggestions.

Peter Gordon, my sponsoring editor, provided the opportunity to share my knowledge and experiences. Reviewers who contributed distinctly different perspectives are Tom Gorsuch, Dick Newman, Wade Shaw, and Hank Stuebing. Thanks to those at Addison-Wesley who made this book possible, and especially to Helen Goldstein, who made it a delight.

Elaine M. Hall


From the Back Cover

- Daniel P. Czelusniak, Director, Acquisition Program Integration Office of the Under Secretary of Defense (Acquisition and Technology) The Pentagon

"Since it is more than just common sense, the newcomer to risk management needs an intelligent guide. It is in this role that Elaine Hall's book excels. This book provides a set of practical and well-delineated processes for implementation of the discipline."

- Tom DeMarco, from the Foreword Risk is inherent in the development of any large software system. A common approach to risk in software development is to ignore it and hope that no serious problems occur. Leading software companies use quantitative risk management methods as a more useful approach to achieve success.

Written for busy professionals charged with delivering high-quality products on time and within budget, Managing Risk is a comprehensive guide that describes a success formula for managing software risk. The book is divided into five parts that describe a risk management road map designed to take you from crisis to control of your software project.

Highlights include:

  • Six disciplines for managing product development.
  • Steps to predictable risk-management process results.
  • How to establish the infrastructure for a risk-aware culture.
  • Methods for the implementation of a risk management plan.
  • Case studies of people in crisisÐand in control.

  • Product details

    • File Size: 5444 KB
    • Print Length: 381 pages
    • Simultaneous Device Usage: Up to 5 simultaneous devices, per publisher limits
    • Publisher: Addison-Wesley Professional; 1 edition (February 5, 1998)
    • Publication Date: February 5, 1998
    • Sold by: Amazon Digital Services LLC
    • Language: English
    • ASIN: B001FBFHE2
    • Text-to-Speech: Enabled
    • X-Ray:
    • Word Wise: Not Enabled
    • Lending: Not Enabled
    • Screen Reader: Supported
    • Enhanced Typesetting: Enabled
    • Amazon Best Sellers Rank: #2,278,757 Paid in Kindle Store (See Top 100 Paid in Kindle Store)
    • Would you like to tell us about a lower price?

    Customer Reviews

    Share your thoughts with other customers
    See all 7 customer reviews

    Top customer reviews

    June 29, 2001
    Format: Hardcover|Verified Purchase
    12 people found this helpful
    |Comment|Report abuse
    June 25, 2005
    Format: Hardcover|Verified Purchase
    One person found this helpful
    |Comment|Report abuse
    December 6, 2007
    Format: Hardcover|Verified Purchase
    2 people found this helpful
    |Comment|Report abuse
    January 29, 2014
    Format: Hardcover|Verified Purchase
    April 1, 2005
    Format: Hardcover
    January 29, 2009
    Format: Hardcover
    May 16, 1999
    Format: Hardcover
    One person found this helpful
    |Comment|Report abuse

    Set up an Amazon Giveaway

    Managing Risk: Methods for Software Systems Development
    Amazon Giveaway allows you to run promotional giveaways in order to create buzz, reward your audience, and attract new followers and customers. Learn more about Amazon Giveaway
    This item: Managing Risk: Methods for Software Systems Development