Part 3: Need for software risk management

Primary tabs

Risk Management -

There are many reasons that risk management is currently in use on software

  • The ability to manage uncertainty
    on projects is a requirement designed to deal with scarce resources, advances
    in technology, and the increased demand for complex systems in a rapidly changing

  • Given the current business climate
    of shrinking profit margins, the global economy and its uncertain market conditions,
    and the competitive forces pressured by rapid technology advances.
  • Risk management techniques were
    introduced to the software community in 1980’s
  • The father of software risk management
    is Barry Boehm, whose contributions include the Spiral Model, a software life
    cycle model that is iterative and risk driven.
Risk in the large

  • Those who practice risk management
    agree that it must be performed regularly throughout the life cycle of a software
    system. Risks are dynamic, meaning that they change over time
  • Risk is neither more nor less
    important than work; it is, instead a part of the effort remaining.


  • Two perspectives
    hinder routine risk management

    Risk viewed as extra activity: The danger perceiving risks as less important
    then assigned work is that we may not address risks when work priorities escalate

    Risk viewed as outside activity: The pitfall in perceiving risk as someone
    else’s responsibility is that when that person is not around, risk management
    will cease.