Project Management

Please login or join to subscribe to this thread

MP4PM: business case review - Risk Assessment

linkedin twitter facebook   Business Analysis   Business Case   PMO   Risk Management  
avatar
Markus Kopko AI Enabler for Project & Program Mgmt | Founder PMotion.ai / The PM AI Coach| PMotion.ai Hamburg, Hamburg, Germany
Hi,

for the background to this discussion thread please refer to this posting here:
https://www.projectmanagement.com/discussi...ss-case-review-

===================================
Risk Assessment
-- Risk #1

--- Description

--- Probability

--- Impact

--- Prevention

--- response strategies

---- negative risk/threat
----- avoid
----- transfer
----- mitigate
----- accept

---- positive risk
----- exploit
----- enhance
----- share
----- accept

--- Contingency Plan


=====================================

Any changes, additions or feedback here?
Sort By:
< 1 2 3 >
avatar
Thilo Wack Head of Existing Product and Test Lab| optimed Tholey-Hasborn, Germany
Dec 14, 2016 8:23 AM
Replying to Markus Kopko
...
Hi Thilo,

thanks for your comment. I see your point (like Rami's); please refer to my answer i have given to Rami's posting.

The intention was NOT to kickoff a complete risk management process at this point BUT to initiate collecting risks and to assess them where possible.

If you will see when the map is online, the risk sassessment branch within this map will have several levels.
The first level is just naming the risk or give them a title.
Of course it is possible to stop this part right here and go on with it at a later stage.
The great thing with the mind map and especially with the so called "map parts" is, that you could easily transfer them to other maps (to risk management in this case for instance).
And this feature supports the developing character of the project management processes in a great way.

But i am open to change this to a plain risk list at this stage when the majority of you likes that more.

Regards,

Markus
Hi Markus,

got your point and I like it. Using the map parts is actually a really neat idea. You just show the more detailed levels, which are hidden as a default setting, and fill them as it makes sense at the time. Probably takes some discipline, though if this is a team effort. Lots of opportunities to lose focus...
...
1 reply by Markus Kopko
Dec 15, 2016 5:58 AM
Markus Kopko
...
Hi Thilo,

absolutely correct! You can check the online version (beta) now (see posting above with the link).

I have left the risk assessment branch as it was from the beginning so you can see it and play around a little bit.
I do absolutley agree with you about the needed discipline and the risk of loosing focus.

So meanwhile i am tending to a change of the list here what may look like the suggestion by Vincent earlier in this thread.
What do you think about this?

Regards,

Markus
avatar
Markus Kopko AI Enabler for Project & Program Mgmt | Founder PMotion.ai / The PM AI Coach| PMotion.ai Hamburg, Hamburg, Germany
@all:
i have put the beat version of the map online now for your consideration and a better overview and understanding of the different branches, you may have a look here:

http://www.projectmanagement.plus/mp4pmmap...ess%20Case.html

Regards,

Markus
avatar
Markus Kopko AI Enabler for Project & Program Mgmt | Founder PMotion.ai / The PM AI Coach| PMotion.ai Hamburg, Hamburg, Germany
Dec 14, 2016 10:15 AM
Replying to Stéphane Parent
...
I agree with Rami and Thilo. The risks listed in the business case are meant to support the decision: do the benefits outweight the costs and the risks?

The decision makers have a specific risk appetite and threshold that need to be met.
Hi Stephane,

thanks for your input here; i am tending to a shorter list of attributes here meanwhile. What do you think about the suggestion by Vincent?

Regards,

Markus
...
1 reply by Stéphane Parent
Dec 15, 2016 7:21 AM
Stéphane Parent
...
The business case is NOT the place for risk analysis, with all its attributes and processes. The business case lists risks that should be considered for the decision.
avatar
Markus Kopko AI Enabler for Project & Program Mgmt | Founder PMotion.ai / The PM AI Coach| PMotion.ai Hamburg, Hamburg, Germany
Dec 14, 2016 11:00 AM
Replying to Rami Kaibni
...
Hi Markus,

I would include this level of details under Risk Analysis but not the business case as again it is very high level and if too much information is mentioned there, it loses its essence as a business case.

Those are my 2 cents.

Cheers,
RK
Hi Rami,

thanks again and your 2 cents are very important to me!

What do you think about the shortage of the list by Vincent? Any additions/comments on that one?

Regards,

Markus
...
1 reply by Rami Kaibni
Dec 15, 2016 11:28 AM
Rami Kaibni
...
Hi Markus,

For a business case, if you want to include details, I would include only:

Risk #1
Description
Probability (high level)
Impact (high level)

This my personal opinion.
avatar
Markus Kopko AI Enabler for Project & Program Mgmt | Founder PMotion.ai / The PM AI Coach| PMotion.ai Hamburg, Hamburg, Germany
Dec 14, 2016 12:58 PM
Replying to Thilo Wack
...
Hi Markus,

got your point and I like it. Using the map parts is actually a really neat idea. You just show the more detailed levels, which are hidden as a default setting, and fill them as it makes sense at the time. Probably takes some discipline, though if this is a team effort. Lots of opportunities to lose focus...
Hi Thilo,

absolutely correct! You can check the online version (beta) now (see posting above with the link).

I have left the risk assessment branch as it was from the beginning so you can see it and play around a little bit.
I do absolutley agree with you about the needed discipline and the risk of loosing focus.

So meanwhile i am tending to a change of the list here what may look like the suggestion by Vincent earlier in this thread.
What do you think about this?

Regards,

Markus
...
1 reply by Thilo Wack
Dec 15, 2016 12:14 PM
Thilo Wack
...
Hi Markus,

thanks for uploading the map; it's much easier to review than the lists (which is exactly why we use maps, isn't it?). While I agree with Rami and Stéphane that a business case only includes a high level view on risks used to make decisions, I think I know what you try to do by using the unique properties of software based mind maps. I need to think a bit more about this and how I would structure such an approach. I will get back to you latest this weekend.

Regards,

Thilo
avatar
Stéphane Parent Self Employed / Semi-retired| Leader Maker Prince Edward Island, Canada
Dec 15, 2016 5:53 AM
Replying to Markus Kopko
...
Hi Stephane,

thanks for your input here; i am tending to a shorter list of attributes here meanwhile. What do you think about the suggestion by Vincent?

Regards,

Markus
The business case is NOT the place for risk analysis, with all its attributes and processes. The business case lists risks that should be considered for the decision.
avatar
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates New Westminster, British Columbia, Canada
Dec 15, 2016 5:54 AM
Replying to Markus Kopko
...
Hi Rami,

thanks again and your 2 cents are very important to me!

What do you think about the shortage of the list by Vincent? Any additions/comments on that one?

Regards,

Markus
Hi Markus,

For a business case, if you want to include details, I would include only:

Risk #1
Description
Probability (high level)
Impact (high level)

This my personal opinion.
avatar
Thilo Wack Head of Existing Product and Test Lab| optimed Tholey-Hasborn, Germany
Dec 15, 2016 5:58 AM
Replying to Markus Kopko
...
Hi Thilo,

absolutely correct! You can check the online version (beta) now (see posting above with the link).

I have left the risk assessment branch as it was from the beginning so you can see it and play around a little bit.
I do absolutley agree with you about the needed discipline and the risk of loosing focus.

So meanwhile i am tending to a change of the list here what may look like the suggestion by Vincent earlier in this thread.
What do you think about this?

Regards,

Markus
Hi Markus,

thanks for uploading the map; it's much easier to review than the lists (which is exactly why we use maps, isn't it?). While I agree with Rami and Stéphane that a business case only includes a high level view on risks used to make decisions, I think I know what you try to do by using the unique properties of software based mind maps. I need to think a bit more about this and how I would structure such an approach. I will get back to you latest this weekend.

Regards,

Thilo
...
1 reply by Markus Kopko
Dec 16, 2016 5:25 AM
Markus Kopko
...
Hi Thilo,

yes, that is exactly the reason why we use and why i am a fan of using mind maps and mind mapping. ;)
As a LL i will put the beta version of the map online first next time, before creating the discussion threads.
Can't await your further input on this.

Regards,

Markus
avatar
Thilo Wack Head of Existing Product and Test Lab| optimed Tholey-Hasborn, Germany
@ Rami, @ Stéphane:

Agree with you that the business case is not the place for a detailed risk analysis but should only contain high level information about risks as the BC section about risk is meant to provide information used for making decisions. Now mentally putting myself in the place of the guy who's making such decisions I'd like to know about the top 5 risks (based on risk impact and probability) and the respective risk response strategy (high level, w/o action plan) as these would be part of the assumptions the business case and the cost/benefit analysis is based on.
What's your view on this?

Best,

Thilo
...
2 replies by Rami Kaibni and Stéphane Parent
Dec 15, 2016 3:03 PM
Rami Kaibni
...
Hi Thilo,

You have a point but as I said to Markus, I would only include:

Risk #1
Description
Probability (high level)
Impact (high level)
Dec 16, 2016 1:07 PM
Stéphane Parent
...
If you're going to list only the top five risks - which is a good idea for the business case - you don't need to show the probability and impact. By definition, these top five risks should be the ones that are the most severe to your organization.

I agree with you, Thilo, that we should give an indication of how, at a high level, we plan on addressing these top five risks: mitigation, transfer, ...
avatar
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates New Westminster, British Columbia, Canada
Dec 15, 2016 12:25 PM
Replying to Thilo Wack
...
@ Rami, @ Stéphane:

Agree with you that the business case is not the place for a detailed risk analysis but should only contain high level information about risks as the BC section about risk is meant to provide information used for making decisions. Now mentally putting myself in the place of the guy who's making such decisions I'd like to know about the top 5 risks (based on risk impact and probability) and the respective risk response strategy (high level, w/o action plan) as these would be part of the assumptions the business case and the cost/benefit analysis is based on.
What's your view on this?

Best,

Thilo
Hi Thilo,

You have a point but as I said to Markus, I would only include:

Risk #1
Description
Probability (high level)
Impact (high level)
...
1 reply by Markus Kopko
Dec 16, 2016 5:28 AM
Markus Kopko
...
Hi Rami,

thanks for that; your list is essentially the list of Vincent just without prevention if i am right?!
More or less i have already decided to shortage the list in the BC map to this one, but before do it finally i will wait for Thilo's consideration.

In fact it is no problem to postpone the deeper risk assessment to a later stage. Latest in the "risk management" area we will dive deep in there, right?

Regards,

Markus
< 1 2 3 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

If a woman has to choose between catching a fly ball and saving an infant's life, she will choose to save the infant's life without even considering if there is a man on base.

- Dave Barry

ADVERTISEMENT

Sponsors