"Never give a fool sterile information, because he cannot ignore it."
So says Nasim Taleb when discussing risk management in the financial industry.
The same can be said about our industry. Think about this paraphrased comment; If we all use the same risk management framework, but we price risk wrong, we are headed for a huge problem.
So, when you are assessing likelihood and impact you are assessing the cost of things going wrong. But are you thinking about the work that is required to manage your risk? Do you update your schedule and budget to acknowledge additional effort required to manage these risks?
There are two things going on here: Being transparent and accountable about the cost of managing risk and building resilience into your project.
17 October 2009
Subscribe to:
Post Comments (Atom)
Popular Posts
-
I have been having a bit of a discussion over at the IIBA blog with Kevin (VP BOK) and Julian (Chief architect.) It’s migrated over to ...
-
Due to popular demand I have aggregated some information on User Stories and created a simple template. If you feel this would be useful to...
-
Better Projects Templates I am uploading a couple of project document templates to Google Docs. As I add more I'll post them up here. You...
-
You've heard many reasons why project fail. Here is a discussion hosted by BCS on why projects work. The discussion covers four dimensio...
-
The Precedence Diagramming Method ( PDM ) was developed in the early 1960s by H.B. Zachry in cooperation with IBM. It has largely repla...
-
In the below video some of the #10yrsagile participants discuss the role of the Business Analyst. A question for you; Do you agree or di...
-
This is a guest post by Jeff Hobbs. Jeff is a project manager at ActiveState Software who provide pm and collaboration software. Email, ...
-
In one of the Carnivals of Business Analysts the theme was “ Requirements Analysis ." I searched the web far and wide and came up with a n...
-
The definition of a stakeholder is controversial. For example, project team members are generally not considered stakeholders, but in virtua...
-
I have written about the V-Model across several posts. The V model is a testing focused expansion of the software development lifecycle. In ...
2 comments: