http://13.50.150.85/index.php?action=history&feed=atom&title=Risk_Management-Identification 2026-07-14T12:05:32Z Revision history for this page on the wiki MediaWiki 1.43.3 http://13.50.150.85/index.php?title=Risk_Management-Identification&diff=101062&oldid=prev 2021-02-28T21:29:39Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en-GB"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 21:29, 28 February 2021</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l83">Line 83:</td> <td colspan="2" class="diff-lineno">Line 83:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Limitations of the current identification standards ==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Limitations of the current identification standards ==</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>The standards connected to risk identification lacks the connection to specific objectives as they are merely general approaches. The given approach might not be the most effective risk identification technique and it is therefore vital to use the standards but support them with historical projects with similar objectives. Additionally, there is no indicator as to how long time one should spend on risk identification. It is crucial to decide upon a reasonable timeframe for identifying risks as too much focus could end in slower project, programme or portfolio process and hinder success. &lt;ref name="PMIStandard"/&gt;&lt;ref name="P2"/&gt;&lt;ref name="ISO"/&gt;</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">*</ins>The standards connected to risk identification lacks the connection to specific objectives as they are merely general approaches. The given approach might not be the most effective risk identification technique and it is therefore vital to use the standards but support them with historical projects with similar objectives. Additionally, there is no indicator as to how long time one should spend on risk identification. It is crucial to decide upon a reasonable timeframe for identifying risks as too much focus could end in slower project, programme or portfolio process and hinder success. &lt;ref name="PMIStandard"/&gt;&lt;ref name="P2"/&gt;&lt;ref name="ISO"/&gt;</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>The «Committee for Oversight and Assessment of U.S. Department of Energy Project Management» addresses the importance of project management personnel training in the book The Owner’s Role in Project Risk. A limitation with the given methods is that the importance of analytical and management skills amongst the risk owners and risk managers is missing. An incompetent manager with a limited view of the objectives will not be able to identify risks unless assisted with a team of greater knowledge. &lt;ref name="nat"/&gt;</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">*</ins>The «Committee for Oversight and Assessment of U.S. Department of Energy Project Management» addresses the importance of project management personnel training in the book <ins style="font-weight: bold; text-decoration: none;">''</ins>The Owner’s Role in Project Risk<ins style="font-weight: bold; text-decoration: none;">''</ins>. A limitation with the given methods is that the importance of analytical and management skills amongst the risk owners and risk managers is missing. An incompetent manager with a limited view of the objectives will not be able to identify risks unless assisted with a team of greater knowledge. &lt;ref name="nat"/&gt;</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>The experts’, stakeholders’ or other influential parties’ bias should be taken into account during risk identification. If the outcome of the project, programme or portfolio will benefit them in a certain way then it is vital to be sceptical as to which extent they are trustworthy. Including a third part or a similar project team can help to prevent expert bias. It is the project owners who should ensure that identified risks are unbiased by using a team of people who are familiar with the methods required to reduce any possible bias. &lt;ref name="nat"/&gt;</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">*</ins>The experts’, stakeholders’ or other influential parties’ bias should be taken into account during risk identification. If the outcome of the project, programme or portfolio will benefit them in a certain way then it is vital to be sceptical as to which extent they are trustworthy. Including a third part or a similar project team can help to prevent expert bias. It is the project owners who should ensure that identified risks are unbiased by using a team of people who are familiar with the methods required to reduce any possible bias. &lt;ref name="nat"/&gt;</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>   </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>   </div></td></tr> </table>

S210444 http://13.50.150.85/index.php?title=Risk_Management-Identification&diff=101048&oldid=prev 2021-02-28T21:27:52Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en-GB"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 21:27, 28 February 2021</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l83">Line 83:</td> <td colspan="2" class="diff-lineno">Line 83:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Limitations of the current identification standards ==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Limitations of the current identification standards ==</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>The standards connected to risk identification lacks the connection to <del style="font-weight: bold; text-decoration: none;">spesific </del>objectives as they are merely general approaches. The given approach might not be the most effective risk identification technique and it is therefore vital to use the standards but support them with historical projects with similar objectives. Additionally, there is no indicator as to how long time one should spend on risk identification. It is crucial to decide upon a reasonable timeframe for identifying risks as too much focus could end in slower project, programme or portfolio process and hinder success. &lt;ref name="PMIStandard"/&gt;&lt;ref name="P2"/&gt;&lt;ref name="ISO"/&gt;</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>The standards connected to risk identification lacks the connection to <ins style="font-weight: bold; text-decoration: none;">specific </ins>objectives as they are merely general approaches. The given approach might not be the most effective risk identification technique and it is therefore vital to use the standards but support them with historical projects with similar objectives. Additionally, there is no indicator as to how long time one should spend on risk identification. It is crucial to decide upon a reasonable timeframe for identifying risks as too much focus could end in slower project, programme or portfolio process and hinder success. &lt;ref name="PMIStandard"/&gt;&lt;ref name="P2"/&gt;&lt;ref name="ISO"/&gt;</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>The «Committee for Oversight and Assessment of U.S. Department of Energy Project Management» addresses the importance of project management personnel training in the book The Owner’s Role in Project Risk. A limitation with the given methods is that the importance of analytical and management skills amongst the risk owners and risk managers is missing. An incompetent manager with a limited view of the objectives will not be able to identify risks unless assisted with a team of greater knowledge. &lt;ref name=&quot;nat&quot;/&gt;</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>The «Committee for Oversight and Assessment of U.S. Department of Energy Project Management» addresses the importance of project management personnel training in the book The Owner’s Role in Project Risk. A limitation with the given methods is that the importance of analytical and management skills amongst the risk owners and risk managers is missing. An incompetent manager with a limited view of the objectives will not be able to identify risks unless assisted with a team of greater knowledge. &lt;ref name=&quot;nat&quot;/&gt;</div></td></tr> </table>

S210444 http://13.50.150.85/index.php?title=Risk_Management-Identification&diff=101028&oldid=prev 2021-02-28T21:23:49Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en-GB"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 21:23, 28 February 2021</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l83">Line 83:</td> <td colspan="2" class="diff-lineno">Line 83:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Limitations of the current identification standards ==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Limitations of the current identification standards ==</div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">The standards connected to risk identification lacks the connection to spesific objectives as they are merely general approaches. The given approach might not be the most effective risk identification technique and it is therefore vital to use the standards but support them with historical projects with similar objectives. Additionally, there is no indicator as to how long time one should spend on risk identification. It is crucial to decide upon a reasonable timeframe for identifying risks as too much focus could end in slower project, programme or portfolio process and hinder success. &lt;ref name="PMIStandard"/&gt;&lt;ref name="P2"/&gt;&lt;ref name="ISO"/&gt;</ins></div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">The «Committee for Oversight and Assessment of U.S. Department of Energy Project Management» addresses the importance of project management personnel training in the book The Owner’s Role in Project Risk. A limitation with the given methods is that the importance of analytical and management skills amongst the risk owners and risk managers is missing. An incompetent manager with a limited view of the objectives will not be able to identify risks unless assisted with a team of greater knowledge. &lt;ref name="nat"/&gt;</ins></div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>The <del style="font-weight: bold; text-decoration: none;">«Committee for Oversight and Assessment of U.S. Department of Energy Project Management» addresses the importance of project management personnel training in the book ''The Owner’s Role in Project Risk''. A limitation with the given methods is that the importance of analytical and management skills amongst the risk owners and risk managers is missing. An incompetent manager with a limited view of the objectives will not be able to identify risks unless assisted. &lt;ref name="nat"/&gt;</del></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>The <ins style="font-weight: bold; text-decoration: none;">experts’</ins>, <ins style="font-weight: bold; text-decoration: none;">stakeholders’ or </ins>other influential <ins style="font-weight: bold; text-decoration: none;">parties’ bias </ins>should be taken into account during risk identification. If the outcome of the project, programme or portfolio will benefit them in a certain way then it is vital to be sceptical as to which extent they are trustworthy. Including a third part or a similar project team can help to prevent expert bias. It is the project owners who should ensure that identified risks are unbiased by using a team of people who are familiar with the methods required to reduce any possible bias. &lt;ref name="nat"/&gt;</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">The bias of experts</del>, <del style="font-weight: bold; text-decoration: none;">stakeholders and all </del>other influential <del style="font-weight: bold; text-decoration: none;">parties </del>should <del style="font-weight: bold; text-decoration: none;">also </del>be taken into account during risk identification. If the outcome of the project, programme or portfolio will benefit them in a certain way then it is vital to be sceptical as to which extent they are trustworthy. Including a third part or a similar project team can help to prevent expert bias. It is the project owners who should ensure that identified risks are unbiased by using a team of people who are familiar with the methods required to reduce any possible bias. &lt;ref name="nat"/&gt;</div></td><td colspan="2" class="diff-side-added"></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>   </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>   </div></td></tr> </table>

S210444 http://13.50.150.85/index.php?title=Risk_Management-Identification&diff=100904&oldid=prev 2021-02-28T21:03:14Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en-GB"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 21:03, 28 February 2021</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l85">Line 85:</td> <td colspan="2" class="diff-lineno">Line 85:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>The «Committee for Oversight and Assessment of U.S. Department of Energy Project Management» addresses the importance of project management personnel training in the book The Owner’s Role in Project Risk. A limitation with the given methods is that the importance of analytical and management skills amongst the risk owners and risk managers is missing. An incompetent manager with a limited view of the objectives will not be able to identify risks unless assisted. &lt;ref name="nat"/&gt;</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>The «Committee for Oversight and Assessment of U.S. Department of Energy Project Management» addresses the importance of project management personnel training in the book <ins style="font-weight: bold; text-decoration: none;">''</ins>The Owner’s Role in Project Risk<ins style="font-weight: bold; text-decoration: none;">''</ins>. A limitation with the given methods is that the importance of analytical and management skills amongst the risk owners and risk managers is missing. An incompetent manager with a limited view of the objectives will not be able to identify risks unless assisted. &lt;ref name="nat"/&gt;</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>The bias of experts, stakeholders and all other influential parties should also be taken into account during risk identification. If the outcome of the project, programme or portfolio will benefit them in a certain way then it is vital to be sceptical as to which extent they are trustworthy. Including a third part or a similar project team can help to prevent expert bias. It is the project owners who should ensure that identified risks are unbiased by using a team of people who are familiar with the methods required to reduce any possible bias. &lt;ref name=&quot;nat&quot;/&gt;</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>The bias of experts, stakeholders and all other influential parties should also be taken into account during risk identification. If the outcome of the project, programme or portfolio will benefit them in a certain way then it is vital to be sceptical as to which extent they are trustworthy. Including a third part or a similar project team can help to prevent expert bias. It is the project owners who should ensure that identified risks are unbiased by using a team of people who are familiar with the methods required to reduce any possible bias. &lt;ref name=&quot;nat&quot;/&gt;</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> </table>

S210444 http://13.50.150.85/index.php?title=Risk_Management-Identification&diff=100893&oldid=prev 2021-02-28T21:02:19Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en-GB"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 21:02, 28 February 2021</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l90">Line 90:</td> <td colspan="2" class="diff-lineno">Line 90:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>   </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>   </div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Annotated bibliography ==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Annotated bibliography ==</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>'''Project Management <del style="font-weight: bold; text-decoration: none;">Institute, Inc</del>. <del style="font-weight: bold; text-decoration: none;">(PMI)(2017)</del>, <del style="font-weight: bold; text-decoration: none;">Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th Edition)</del>'''  </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>'''<ins style="font-weight: bold; text-decoration: none;">National Research Council. 2005. The Owner's Role in </ins>Project <ins style="font-weight: bold; text-decoration: none;">Risk </ins>Management. <ins style="font-weight: bold; text-decoration: none;">Washington</ins>, <ins style="font-weight: bold; text-decoration: none;">DC: The National Academies Press</ins>'''  </div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>*<del style="font-weight: bold; text-decoration: none;">This book </del>is an <del style="font-weight: bold; text-decoration: none;">updated PMI flagship publication released </del>in <del style="font-weight: bold; text-decoration: none;">2017</del>. <del style="font-weight: bold; text-decoration: none;">It contains </del>a <del style="font-weight: bold; text-decoration: none;">guide </del>of project management and the <del style="font-weight: bold; text-decoration: none;">updated 2017 </del>standards<del style="font-weight: bold; text-decoration: none;">. Chapter 11 addresses Project Risk Management, herein identification of risks</del>.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>*<ins style="font-weight: bold; text-decoration: none;">The report </ins>is an <ins style="font-weight: bold; text-decoration: none;">outcome of the Committee of the Conference on Energy and Water Development of the 105th US Congress </ins>in <ins style="font-weight: bold; text-decoration: none;">1997</ins>. <ins style="font-weight: bold; text-decoration: none;">Here, </ins>a <ins style="font-weight: bold; text-decoration: none;">review and assessment </ins>of <ins style="font-weight: bold; text-decoration: none;">the progress made in </ins>project management <ins style="font-weight: bold; text-decoration: none;">principles was conducted by the National Research Council (NRC) with request from the Department of Energy (DOE). The literature from chapter 4 “Risk Identification </ins>and <ins style="font-weight: bold; text-decoration: none;">Analysis” covers risk identification techniques and is used as an additional literature to </ins>the <ins style="font-weight: bold; text-decoration: none;">international </ins>standards.  </div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">'''Project Management Institute, Inc. (PMI)(2019), Standard for Risk Management in Portfolios, Programs, and Projects'''</del></div></td><td colspan="2" class="diff-side-added"></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">*The book expands the PMI's popular reference, «The Practice Standard for Project Risk Management». It addresses the term life cycle in connection with risk identification and divides the management of risks into different sections for project, programme and portfolio management.</del></div></td><td colspan="2" class="diff-side-added"></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>&#039;&#039;&#039;Munier, Nolberto (2014) , Risk Identification. In: Risk Management for Engineering Projects&#039;&#039;&#039;</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>&#039;&#039;&#039;Munier, Nolberto (2014) , Risk Identification. In: Risk Management for Engineering Projects&#039;&#039;&#039;</div></td></tr> </table>

S210444 http://13.50.150.85/index.php?title=Risk_Management-Identification&diff=100801&oldid=prev 2021-02-28T20:51:55Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en-GB"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 20:51, 28 February 2021</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l83">Line 83:</td> <td colspan="2" class="diff-lineno">Line 83:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Limitations of the current identification standards ==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Limitations of the current identification standards ==</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">Some limitations </del>of the <del style="font-weight: bold; text-decoration: none;">international standards are presented below: </del></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">*It might be challenging to identify risks if working </del>in <del style="font-weight: bold; text-decoration: none;">a new environment </del>with <del style="font-weight: bold; text-decoration: none;">little historical background. </del></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">*There </del>is <del style="font-weight: bold; text-decoration: none;">no indicator as to how long time one should spend on </del>risk <del style="font-weight: bold; text-decoration: none;">identification. It </del>is <del style="font-weight: bold; text-decoration: none;">crucial to decide upon a reasonable timeframe for identifying risks as too much focus could end in slower project, programme or portfolio process and hinder success</del>.  </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">The «Committee for Oversight and Assessment </ins>of <ins style="font-weight: bold; text-decoration: none;">U.S. Department of Energy Project Management» addresses the importance of project management personnel training in </ins>the <ins style="font-weight: bold; text-decoration: none;">book The Owner’s Role </ins>in <ins style="font-weight: bold; text-decoration: none;">Project Risk. A limitation </ins>with <ins style="font-weight: bold; text-decoration: none;">the given methods </ins>is <ins style="font-weight: bold; text-decoration: none;">that the importance of analytical and management skills amongst the risk owners and </ins>risk <ins style="font-weight: bold; text-decoration: none;">managers </ins>is <ins style="font-weight: bold; text-decoration: none;">missing</ins>. <ins style="font-weight: bold; text-decoration: none;">An incompetent manager with </ins>a <ins style="font-weight: bold; text-decoration: none;">limited view </ins>of <ins style="font-weight: bold; text-decoration: none;">the objectives </ins>will <ins style="font-weight: bold; text-decoration: none;">not </ins>be <ins style="font-weight: bold; text-decoration: none;">able to identify risks unless assisted. &lt;ref name="nat"/&gt;</ins></div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">*The standards are general and cover </del>a <del style="font-weight: bold; text-decoration: none;">widespread </del>of <del style="font-weight: bold; text-decoration: none;">professions. Not all techniques </del>will be <del style="font-weight: bold; text-decoration: none;">suitable for every scenario and </del></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>The bias <ins style="font-weight: bold; text-decoration: none;">of experts, stakeholders and all other influential parties </ins>should <ins style="font-weight: bold; text-decoration: none;">also </ins>be taken into account during risk identification. If the outcome of the project, programme or portfolio will benefit <ins style="font-weight: bold; text-decoration: none;">them </ins>in a certain way then it is vital to be sceptical as to which extent they are trustworthy. Including a third part or a similar project team can help to prevent expert bias. <ins style="font-weight: bold; text-decoration: none;">It is the project owners who should ensure that identified risks are unbiased by using a team of people who are familiar with the methods required to reduce any possible bias. &lt;ref name="nat"/&gt;</ins></div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">*</del>The <del style="font-weight: bold; text-decoration: none;">experts’ </del>bias should be taken into account during risk identification. If the outcome of the project, programme or portfolio will benefit <del style="font-weight: bold; text-decoration: none;">the expert team </del>in a certain way then it is vital to be sceptical as to which extent they are trustworthy. Including a third part or a similar project team can help to prevent expert bias.  </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>   </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>   </div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Annotated bibliography ==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Annotated bibliography ==</div></td></tr> <tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l115">Line 115:</td> <td colspan="2" class="diff-lineno">Line 115:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>&lt;ref name=&quot;RBS&quot;&gt;Hillson, David (2003), Using a Risk Breakdown Structure in project management&lt;/ref&gt;</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>&lt;ref name=&quot;RBS&quot;&gt;Hillson, David (2003), Using a Risk Breakdown Structure in project management&lt;/ref&gt;</div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">&lt;ref name="nat"&gt; National Research Council. 2005. The Owner's Role in Project Risk Management."4 Risk Identification and Analysis." Washington, DC: The National Academies Press. doi: 10.17226/11183.&lt;/ref&gt;</ins></div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>&lt;ref name=&quot;Brainstorm&quot;&gt;Eleazar, Hernández (2017), Brainstorming p.57-58. In: Leading Creative Teams Management Career Paths for Deigners, Developers, and Copywriters, APress&lt;/ref&gt;</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>&lt;ref name=&quot;Brainstorm&quot;&gt;Eleazar, Hernández (2017), Brainstorming p.57-58. In: Leading Creative Teams Management Career Paths for Deigners, Developers, and Copywriters, APress&lt;/ref&gt;</div></td></tr> </table>

S210444 http://13.50.150.85/index.php?title=Risk_Management-Identification&diff=100387&oldid=prev 2021-02-28T19:54:41Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en-GB"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 19:54, 28 February 2021</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l7">Line 7:</td> <td colspan="2" class="diff-lineno">Line 7:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Why identify risks? ==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Why identify risks? ==</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>A risk is defined as the uncertainty of an event, that if occurs, impacts the event either in a positive or negative manner <del style="font-weight: bold; text-decoration: none;">&lt;ref name="</del>PMIStandard<del style="font-weight: bold; text-decoration: none;">"/&gt;</del>. When managing projects, programmes or portfolios, it is vital to identify and manage risks in order to prevent negative <del style="font-weight: bold; text-decoration: none;">outcomes </del>and benefit from positive outcomes. Risk management is a common practice and lies within the planning stage of project<del style="font-weight: bold; text-decoration: none;">, programme and portfolio </del>management. According to the “Standard for Risk Management in Portfolios, Programs, and Projects” published by PMI<del style="font-weight: bold; text-decoration: none;">&lt;ref name="</del>PMIStandard<del style="font-weight: bold; text-decoration: none;">"/&gt;</del>, identifying risks is the second out of seven stages within the risk management life cycle. Hence, identifying risks is one of the early stages of risk management and a necessity in order to pursue further risk management actions and prevent a negative impact on the projects’ success.&lt;ref name="PMIStandard"/&gt;</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>A risk is defined as the uncertainty of an event, that if occurs, impacts the event either in a positive or negative manner <ins style="font-weight: bold; text-decoration: none;">(</ins>PMIStandard<ins style="font-weight: bold; text-decoration: none;">)</ins>. When managing projects, programmes or portfolios, it is vital to identify and manage risks in order to prevent negative <ins style="font-weight: bold; text-decoration: none;">-, </ins>and benefit from positive<ins style="font-weight: bold; text-decoration: none;">, </ins>outcomes<ins style="font-weight: bold; text-decoration: none;">. The project, programme or portfolio manager should always make sure that risk identification and further risk management is carried out, but the ownership and responsibility of risks is distributed to relevant individuals, teams or departments</ins>. Risk management is a common practice and lies within the planning stage of project management. According to the “Standard for Risk Management in Portfolios, Programs, and Projects” published by <ins style="font-weight: bold; text-decoration: none;">the Project Management Institute (</ins>PMI<ins style="font-weight: bold; text-decoration: none;">)</ins>PMIStandard, identifying risks is the second out of seven stages within the risk management life cycle. Hence, identifying risks is one of the early stages of risk management and a necessity in order to pursue further risk management actions and prevent a negative impact on the projects’ success.&lt;ref name="PMIStandard"/&gt;</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Context and Application ==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Context and Application ==</div></td></tr> <tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l14">Line 14:</td> <td colspan="2" class="diff-lineno">Line 14:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[[File:Red.png|right|thumb|300px|Figure 1: Illustrates that identifying risks is a part of the risk management life cycle.Modified from&lt;ref name=&quot;PMIStandard&quot;/&gt;.&lt;ref name=&quot;Red&quot;/&gt;]]</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[[File:Red.png|right|thumb|300px|Figure 1: Illustrates that identifying risks is a part of the risk management life cycle.Modified from&lt;ref name=&quot;PMIStandard&quot;/&gt;.&lt;ref name=&quot;Red&quot;/&gt;]]</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>In 2019, PMI published the international standard “Standard for Risk Management in Portfolios, Programs, and Projects” PMIStandard. The standard is put to practice worldwide and is a tool for project, programme or portfolio managers to achieve success. PMI divides risks into two categories; &#039;&#039;individual risks&#039;&#039; that effect one or more objectives and &#039;&#039;overall risks&#039;&#039; as the uncertainty of the whole project, programme or portfolio that arises as a collection of all sources of uncertainty. Both individual and overall risks are important to identify within the identification process. Additionally, they address the risks with positive outcomes as &#039;&#039;opportunities&#039;&#039; and risks with negative outcomes as &#039;&#039;threats&#039;&#039;. The separate terms are applied to distinguish the possible outcomes and effects of risks within projects, programmes or portfolios. Other terms used to distinguish and characterise risks are &#039;&#039;conditional risks&#039;&#039; that will occur as an effect of another risk occurring. The term &#039;&#039;correlated risks&#039;&#039; is used for risks that vary accordingly due to a fixed correlation. &#039;&#039;Independent and dependent risks&#039;&#039; are also two terms addressed when stating the dependencies of two risks to one another.  The wide termination of risks serves as a purpose to initiate structure and to differentiate them from one another.&lt;ref name=&quot;PMIStandard&quot;/&gt;&lt;ref name=&quot;RiskEng&quot;/&gt;</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>In 2019, PMI published the international standard “Standard for Risk Management in Portfolios, Programs, and Projects” PMIStandard. The standard is put to practice worldwide and is a tool for project, programme or portfolio managers to achieve success. PMI divides risks into two categories; &#039;&#039;individual risks&#039;&#039; that effect one or more objectives and &#039;&#039;overall risks&#039;&#039; as the uncertainty of the whole project, programme or portfolio that arises as a collection of all sources of uncertainty. Both individual and overall risks are important to identify within the identification process. Additionally, they address the risks with positive outcomes as &#039;&#039;opportunities&#039;&#039; and risks with negative outcomes as &#039;&#039;threats&#039;&#039;. The separate terms are applied to distinguish the possible outcomes and effects of risks within projects, programmes or portfolios. Other terms used to distinguish and characterise risks are &#039;&#039;conditional risks&#039;&#039; that will occur as an effect of another risk occurring. The term &#039;&#039;correlated risks&#039;&#039; is used for risks that vary accordingly due to a fixed correlation. &#039;&#039;Independent and dependent risks&#039;&#039; are also two terms addressed when stating the dependencies of two risks to one another.  The wide termination of risks serves as a purpose to initiate structure and to differentiate them from one another.&lt;ref name=&quot;PMIStandard&quot;/&gt;&lt;ref name=&quot;RiskEng&quot;/&gt;</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>In addition to PMI, ISO and PRINCE2 are two practiced standards that differ slightly from the methodology given by PMI. In terms of risk identification, PMI is the only standard that addresses the life cycle term, whilst ISO and Prince2 lists identification as either the first or second step within the procedure of risk management. However, all sources addresses the importance of risk management as a continuous procedure, as risks are not only to be identified at the beginning of a project, but is a continuous process from the projects’, programmes’, or portfolios’ initiation to completion. Hence, the methodology given by PMI, addressing risk identification as a step within a life cycle, amplifies the importance of the practice throughout the whole project. The risk management life cycle is illustrated in Figure 1&lt;ref name="Red"/&gt;. &lt;ref name="PMIStandard"/&gt;&lt;ref name="P2"/&gt;&lt;ref name="ISO"/&gt;</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>In addition to PMI, ISO and PRINCE2 are two practiced standards that differ slightly from the methodology given by PMI. In terms of risk identification, PMI is the only standard that addresses the life cycle term, whilst ISO and Prince2 lists identification as either the first or second step within the procedure of risk management. However, all sources addresses the importance of risk management as a continuous procedure, as risks are not only to be identified at the beginning of a project, but is a continuous process from the projects’, programmes’, or portfolios’ initiation to completion. Hence, the methodology given by PMI, addressing risk identification as a step within a <ins style="font-weight: bold; text-decoration: none;">"</ins>life cycle<ins style="font-weight: bold; text-decoration: none;">"</ins>, amplifies the importance of the practice throughout the whole project. The risk management life cycle is illustrated in Figure 1&lt;ref name="Red"/&gt;. &lt;ref name="PMIStandard"/&gt;&lt;ref name="P2"/&gt;&lt;ref name="ISO"/&gt;</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Inputs ==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Inputs ==</div></td></tr> </table>

S210444 http://13.50.150.85/index.php?title=Risk_Management-Identification&diff=100312&oldid=prev 2021-02-28T19:42:10Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en-GB"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 19:42, 28 February 2021</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l2">Line 2:</td> <td colspan="2" class="diff-lineno">Line 2:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">Risk </del>identification is necessary for all projects, programmes and portfolios that strive to achieve a set of objectives with success. <del style="font-weight: bold; text-decoration: none;">The international </del>standards made by <del style="font-weight: bold; text-decoration: none;">the </del>Project Management Institute(PMI), PRojects IN Controlled Environments (PRINCE2) and the International <del style="font-weight: bold; text-decoration: none;">Organisation </del>for <del style="font-weight: bold; text-decoration: none;">Standardisation </del>(ISO) addresses tools and techniques in order to perform <del style="font-weight: bold; text-decoration: none;">a </del>successful identification <del style="font-weight: bold; text-decoration: none;">process for project, programme or portfolio managers</del>. The <del style="font-weight: bold; text-decoration: none;">standards highlight </del>the <del style="font-weight: bold; text-decoration: none;">importance </del>of <del style="font-weight: bold; text-decoration: none;">handling the objectives</del>. However, <del style="font-weight: bold; text-decoration: none;">successful </del>risk <del style="font-weight: bold; text-decoration: none;">management involves </del>more than listing <del style="font-weight: bold; text-decoration: none;">identified risks</del>. <del style="font-weight: bold; text-decoration: none;">Risk identification is an iterative process in an ongoing life cycle for projects, programmes or portfolios and demands the identified risks to be structured in </del>a <del style="font-weight: bold; text-decoration: none;">way that matches their complexity and level </del>of <del style="font-weight: bold; text-decoration: none;">impact. Adopting </del>identification techniques such as brainstorming, risk checklists and risk breakdown structure are necessary actions in order to output a thorough risk register, risk report and perform revision of project documents. Some key success factors for risk identification, amongst others, are the implementation of effective and clear communication, early and comprehensive identifications, inclusion of risks both as threats and opportunities<del style="font-weight: bold; text-decoration: none;">, </del>individual <del style="font-weight: bold; text-decoration: none;">and </del>overall <del style="font-weight: bold; text-decoration: none;">risks </del>and <del style="font-weight: bold; text-decoration: none;">include a variety </del>of <del style="font-weight: bold; text-decoration: none;">departments for multiple risk perspectives</del>.&lt;ref name="PMIStandard"/&gt;&lt;ref name="P2"/&gt;&lt;ref name="ISO"/&gt;</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">The term ''risk </ins>identification<ins style="font-weight: bold; text-decoration: none;">'' refers to the investigation of objectives for opportunities and threats. The process </ins>is necessary for all projects, programmes and portfolios that strive to achieve a set of objectives with success. <ins style="font-weight: bold; text-decoration: none;">International </ins>standards made by Project Management Institute (PMI), PRojects IN Controlled Environments (PRINCE2) and the International <ins style="font-weight: bold; text-decoration: none;">Organization </ins>for <ins style="font-weight: bold; text-decoration: none;">Standardization </ins>(ISO) addresses tools and techniques in order to perform successful <ins style="font-weight: bold; text-decoration: none;">risk </ins>identification. The <ins style="font-weight: bold; text-decoration: none;">process might be thought of as simply listing </ins>the <ins style="font-weight: bold; text-decoration: none;">risks a team could think </ins>of. However, risk <ins style="font-weight: bold; text-decoration: none;">identification is </ins>more <ins style="font-weight: bold; text-decoration: none;">comprehensive </ins>than <ins style="font-weight: bold; text-decoration: none;">risk </ins>listing. <ins style="font-weight: bold; text-decoration: none;"> Adopting </ins>a <ins style="font-weight: bold; text-decoration: none;">variety </ins>of identification techniques such as brainstorming, risk checklists and risk breakdown structure are necessary actions in order to output a thorough risk register, risk report and perform revision of project documents. Some key success factors for risk identification, amongst others, are the implementation of effective and clear communication, early and comprehensive identifications, inclusion of risks both as threats and opportunities <ins style="font-weight: bold; text-decoration: none;">and their impact as an </ins>individual <ins style="font-weight: bold; text-decoration: none;">or </ins>overall <ins style="font-weight: bold; text-decoration: none;">risk. Risk identification for projects, programmes or portfolios must be treated as an iterative process which needs to be managed according to their complexity </ins>and <ins style="font-weight: bold; text-decoration: none;">level </ins>of <ins style="font-weight: bold; text-decoration: none;">impact. </ins></div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>.&lt;ref name="PMIStandard"/&gt;&lt;ref name="P2"/&gt;&lt;ref name="ISO"/&gt;</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Why identify risks? ==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Why identify risks? ==</div></td></tr> </table>

S210444 http://13.50.150.85/index.php?title=Risk_Management-Identification&diff=92779&oldid=prev 2021-02-24T14:00:18Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en-GB"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 14:00, 24 February 2021</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l29">Line 29:</td> <td colspan="2" class="diff-lineno">Line 29:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==== Risk Breakdown Structure (RBS)====</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==== Risk Breakdown Structure (RBS)====</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>[[File:PS.jpg|right|thumb|400px|Figure 2: Shows the risk breakdown structure for the PESTLE model. <del style="font-weight: bold; text-decoration: none;">Inspired by </del>&lt;ref name="P2"/&gt;.&lt;ref name="Pestle1"/&gt;]]A risk breakdown structure (RBS) is a hierarchical decomposition of potential sources of risk&lt;ref name="P2"/&gt; . The structure aims to divide the risks into specific domains with enhanced detail and further subdivisions. The purpose of RBS is to make a detailed overview for the manager of the project, programme or portfolio of the different sections that the risks correspond to. There are several ways to organise the risk breakdown structure and each risk may be broken down differently according to complexity and size. In PRINCE2, the PESTLE (Political, Economic, Social, Technical, Legislative, Environmental) division is described as one of many generic subdivisions that can be implemented for a wide range of projects, programmes or portfolios. In addition to PESTLE, the guidebook for PMI addresses TECOP (technical, environmental, commercial, operational, political), and VUCA (volatility, uncertainty, complexity, ambiguity) as two other relevant generic structures suitable for RBS. &lt;ref name="PMIGuide"/&gt;</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>[[File:PS.jpg|right|thumb|400px|Figure 2: Shows the risk breakdown structure for the PESTLE model. <ins style="font-weight: bold; text-decoration: none;">Modified from </ins>&lt;ref name="P2"/&gt;.&lt;ref name="Pestle1"/&gt;]]A risk breakdown structure (RBS) is a hierarchical decomposition of potential sources of risk&lt;ref name="P2"/&gt; . The structure aims to divide the risks into specific domains with enhanced detail and further subdivisions. The purpose of RBS is to make a detailed overview for the manager of the project, programme or portfolio of the different sections that the risks correspond to. There are several ways to organise the risk breakdown structure and each risk may be broken down differently according to complexity and size. In PRINCE2, the PESTLE (Political, Economic, Social, Technical, Legislative, Environmental) division is described as one of many generic subdivisions that can be implemented for a wide range of projects, programmes or portfolios. In addition to PESTLE, the guidebook for PMI addresses TECOP (technical, environmental, commercial, operational, political), and VUCA (volatility, uncertainty, complexity, ambiguity) as two other relevant generic structures suitable for RBS. &lt;ref name="PMIGuide"/&gt;</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Figure 2 is a graphical representation of the PESTLE template model and should be modified into further specific and relevant subdivisions when put to practice.  </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Figure 2 is a graphical representation of the PESTLE template model and should be modified into further specific and relevant subdivisions when put to practice.  </div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>An additional general RBS is depicted in Figure 3&lt;ref name=&quot;RBS14&quot;/&gt;. The figure is modified for the purpose of this article and illustrates a universal and general decomposition made by the Risk Management Specific Interest Group of the Project Management Institute (PMI Risk SIG) and the Risk Management Working Group of the International Council On Systems Engineering (INCOSE RMWG). The model breaks down the different risks associated to the categories: technology, management and external.&lt;ref name=&quot;P2&quot;/&gt;&lt;ref name=&quot;PMIGuide&quot;/&gt;&lt;ref name=&quot;RBS&quot;/&gt;  </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>An additional general RBS is depicted in Figure 3&lt;ref name=&quot;RBS14&quot;/&gt;. The figure is modified for the purpose of this article and illustrates a universal and general decomposition made by the Risk Management Specific Interest Group of the Project Management Institute (PMI Risk SIG) and the Risk Management Working Group of the International Council On Systems Engineering (INCOSE RMWG). The model breaks down the different risks associated to the categories: technology, management and external.&lt;ref name=&quot;P2&quot;/&gt;&lt;ref name=&quot;PMIGuide&quot;/&gt;&lt;ref name=&quot;RBS&quot;/&gt;  </div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>[[File:RBS14.jpg|center|thumb|800px|Figure 3: Shows a generic risk breakdown structure based on PMI Risk SIG and INCOSE RMWG. <del style="font-weight: bold; text-decoration: none;">Inspired by </del>&lt;ref name="PMIGuide"/&gt;&lt;ref name="RBS"/&gt; ]]</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>[[File:RBS14.jpg|center|thumb|800px|Figure 3: Shows a generic risk breakdown structure based on PMI Risk SIG and INCOSE RMWG. <ins style="font-weight: bold; text-decoration: none;">Modified from </ins>&lt;ref name="PMIGuide"/&gt;&lt;ref name="RBS"/&gt; ]]</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> </table>

S210444 http://13.50.150.85/index.php?title=Risk_Management-Identification&diff=89828&oldid=prev 2021-02-21T19:57:28Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en-GB"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 19:57, 21 February 2021</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l58">Line 58:</td> <td colspan="2" class="diff-lineno">Line 58:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==== Risk register ====</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==== Risk register ====</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>The aim of identifying risks is to gather them in a risk register that can actively be used by all active participants of the project, programme or portfolio. The risk register includes a thorough list of all risks identified with detailed information of their potential cause and effect. A specific risk owner may be addressed in order to specify the person or team responsible for monitoring and managing the risk. Possible responses to the risks should be included for those of predictable outcome. The complexity of the risk register and the length of each risk description will differ from the context of the project, programme or portfolio.&lt;ref name="PMIGuide"/&gt; <del style="font-weight: bold; text-decoration: none;">p.417</del></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>The aim of identifying risks is to gather them in a risk register that can actively be used by all active participants of the project, programme or portfolio. The risk register includes a thorough list of all risks identified with detailed information of their potential cause and effect. A specific risk owner may be addressed in order to specify the person or team responsible for monitoring and managing the risk. Possible responses to the risks should be included for those of predictable outcome. The complexity of the risk register and the length of each risk description will differ from the context of the project, programme or portfolio.&lt;ref name="PMIGuide"/&gt;  </div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==== Risk report ====</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==== Risk report ====</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>In addition to the risk register, a risk report can be composed in order to address the overall risk of a specific project, programme or portfolio. The risk report includes summaries of all individual risks and to which extent they impose a threat or opportunity to the project, programme or portfolio as a whole. Tools such as metrics, trends, or risk rating systems may be implied in order to inform the project manager and all relevant parties of historical data, statistics and degree of threat that the identified risks can cause. &lt;ref name="PMIGuide"/&gt; <del style="font-weight: bold; text-decoration: none;">p.418</del></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>In addition to the risk register, a risk report can be composed in order to address the overall risk of a specific project, programme or portfolio. The risk report includes summaries of all individual risks and to which extent they impose a threat or opportunity to the project, programme or portfolio as a whole. Tools such as metrics, trends, or risk rating systems may be implied in order to inform the project manager and all relevant parties of historical data, statistics and degree of threat that the identified risks can cause. &lt;ref name="PMIGuide"/&gt;  </div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==== Revision of project documents ====</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==== Revision of project documents ====</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>Lastly, the outcome of the identification process might have affected the initial assumptions and must therefore be re- assessed. This is an important process in order to include new aspects and concerns from the risk identification stage. For future projects it can also be relevant to compose a register of the tools and techniques used in the specific project, programme or portfolio in order to document what methods that were beneficial to use and which methods that didn’t serve a significant purpose during the risk identification process.&lt;ref name="PMIGuide"/&gt; <del style="font-weight: bold; text-decoration: none;">p.418</del></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>Lastly, the outcome of the identification process might have affected the initial assumptions and must therefore be re- assessed. This is an important process in order to include new aspects and concerns from the risk identification stage. For future projects it can also be relevant to compose a register of the tools and techniques used in the specific project, programme or portfolio in order to document what methods that were beneficial to use and which methods that didn’t serve a significant purpose during the risk identification process.&lt;ref name="PMIGuide"/&gt;  </div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Key success factors for identifying risks ==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== Key success factors for identifying risks ==</div></td></tr> <tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l102">Line 102:</td> <td colspan="2" class="diff-lineno">Line 102:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== References ==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== References ==</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>&lt;references&gt;</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>&lt;references&gt;</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>&lt;ref name="PMIGuide"&gt;Project Management Institute, Inc.(PMI) (2017), Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th Edition) &lt;/ref&gt;</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>&lt;ref name="PMIGuide"&gt;Project Management Institute, Inc.(PMI) (2017), Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th Edition)&lt;/ref&gt;</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>&lt;ref name=&quot;PMIStandard&quot;&gt; Project Management Institute, Inc.(PMI) (2019), Standard for Risk Management in Portfolios, Programs, and Projects&lt;/ref&gt;</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>&lt;ref name=&quot;PMIStandard&quot;&gt; Project Management Institute, Inc.(PMI) (2019), Standard for Risk Management in Portfolios, Programs, and Projects&lt;/ref&gt;</div></td></tr> </table>

S210444