#10 – ALARP – AS LOW AS REASONABLY POSSIBLE – PAUL KOSTEK

ALARP – As Low as Reasonably Possible.

Paul Kostek PixFor anyone with any experience with risk management this is one of the key terms used to make a decision about applying risk mitigations.  It is used when going beyond a certain point (cost/weight/performance), open to definition by every company, that the resulting cost/performance of the product no longer makes fiscal sense.

Continue reading

#8: UNADDRESSED RISK – PAUL KOSTEK

Paul Kostek PixWhat’s the risk of not addressing a risk?  What happens on a project when a risk is identified and not addressed/mitigated?    There may be reasons not to correct it, e.g low probability of occurrence and minimal impact,  but how do we document and track this decision?  And if we’re delaying an implementation how do we insure the risk is addressed at a later date, e.g. next version release?   How do we insure that if an audit takes place the project team can clearly explain the reasons for the decision?  Is this even acceptable?
Continue reading

#7 – SOFTWARE RISK MANAGEMENT – PAUL KOSTEK

Paul Kostek PixFor anyone involved in risk management the thought of applying risk techniques to software opens many questions, including can we really identify risk areas in code?  Can we identify what software items contribute to hazardous situations? Can we identify mitigations and be sure we have covered all cases?

Continue reading