Comments on: Top 6 Problems with Risk Management http://blog.brodzinski.com/2006/11/top-6-problems-with-risk-management.html Dealing with software projects in real life Fri, 10 Feb 2012 19:07:34 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Pawel Brodzinski http://blog.brodzinski.com/2006/11/top-6-problems-with-risk-management.html#comment-1759 Pawel Brodzinski Wed, 29 Nov 2006 11:53:00 +0000 http://blog.brodzinski.com/2006/11/top-6-problems-with-risk-management.html#comment-1759 Yes, it's hard to define uncertainty, but I think in many cases we're able to name some issues, which wring that uncertainty. <br /><br />I <i>feel</i> that we can have problem with meeting the deadline. OK, why is it so? Maybe I'm afraid that subcontractor won't do their work on time. Maybe I think that schedule is tight and there's no place for any slip. Maybe I guess the team can underperform because they're running third hard project in a row. And these all are candidates for risks. I believe, that where there's uncertainty and unease there're also some risks to find. You just need to dig deeper. Yes, it’s hard to define uncertainty, but I think in many cases we’re able to name some issues, which wring that uncertainty.

I feel that we can have problem with meeting the deadline. OK, why is it so? Maybe I’m afraid that subcontractor won’t do their work on time. Maybe I think that schedule is tight and there’s no place for any slip. Maybe I guess the team can underperform because they’re running third hard project in a row. And these all are candidates for risks. I believe, that where there’s uncertainty and unease there’re also some risks to find. You just need to dig deeper.

]]> By: Austin Bob http://blog.brodzinski.com/2006/11/top-6-problems-with-risk-management.html#comment-1758 Austin Bob Wed, 29 Nov 2006 08:48:00 +0000 http://blog.brodzinski.com/2006/11/top-6-problems-with-risk-management.html#comment-1758 Good summary. I think the thing that really gets my goat is the "nothing changed" status report. Or maybe it's the full-length repetition of last week's status report as if the reporter has forgotten the problem. In some cases your comment about setting a reasonable frequency will help, but other times someone (me?) just needs to do a better job of setting expectations and facilitating the session.<br /><br />Perhaps another problem lies in the difference between risk and uncertainty. A risk already has an identity and needs to be studied and (where possible) mitigated. Working on a risk involves a more-or-less obvious focus. Uncertainty, however, is based in a vague feeling of unease ... a sense that there are things we don't know that are going to cause problems. Of course, this is true! But until we shine the bright light of attention in those dark corners, it is not helpful to call it a risk. (I think this may actually be the kind of thing you mentioned in your #1.)<br /><br />Anyway, I am adding your site to one of my regular destinations. keep it up! Good summary. I think the thing that really gets my goat is the “nothing changed” status report. Or maybe it’s the full-length repetition of last week’s status report as if the reporter has forgotten the problem. In some cases your comment about setting a reasonable frequency will help, but other times someone (me?) just needs to do a better job of setting expectations and facilitating the session.

Perhaps another problem lies in the difference between risk and uncertainty. A risk already has an identity and needs to be studied and (where possible) mitigated. Working on a risk involves a more-or-less obvious focus. Uncertainty, however, is based in a vague feeling of unease … a sense that there are things we don’t know that are going to cause problems. Of course, this is true! But until we shine the bright light of attention in those dark corners, it is not helpful to call it a risk. (I think this may actually be the kind of thing you mentioned in your #1.)

Anyway, I am adding your site to one of my regular destinations. keep it up!

]]>