Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Special pages
Niidae Wiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Risk management
(section)
Page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
===Project management=== {{Main|Project risk management}} Project risk management must be considered at the different phases of acquisition. At the beginning of a project, the advancement of technical developments, or threats presented by a competitor's projects, may cause a risk or threat assessment and subsequent evaluation of alternatives (see [[Analysis of Alternatives]]). Once a decision is made, and the project begun, more familiar project management applications can be used:<ref>Lev Virine and Michael Trumper. ''Project Decisions: The Art and Science''. (2007). Management Concepts. Vienna. VA. {{ISBN|978-1-56726-217-9}}</ref><ref>Lev Virine and Michael Trumper. ''ProjectThink: Why Good Managers Make Poor Project Choices''. Gower Pub Co. {{ISBN|978-1409454984}}</ref><ref>Peter Simon and David Hillson, Practical Risk Management: The ATOM Methodology (2012). Management Concepts. Vienna, VA. {{ISBN|978-1567263664}}</ref> * Planning how risk will be managed in the particular project. Plans should include risk management tasks, responsibilities, activities and budget. * Assigning a risk officer β a team member other than a project manager who is responsible for foreseeing potential project problems. Typical characteristic of risk officer is a healthy skepticism. * Maintaining live project risk database. Each risk should have the following attributes: opening date, title, short description, probability and importance. Optionally a risk may have an assigned person responsible for its resolution and a date by which the risk must be resolved. * Creating anonymous risk reporting channel. Each team member should have the possibility to report risks that he/she foresees in the project. * Preparing mitigation plans for risks that are chosen to be mitigated. The purpose of the mitigation plan is to describe how this particular risk will be handled β what, when, by whom and how will it be done to avoid it or minimize consequences if it becomes a liability. * Summarizing planned and faced risks, effectiveness of mitigation activities, and effort spent for the risk management.
Summary:
Please note that all contributions to Niidae Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Encyclopedia:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Search
Search
Editing
Risk management
(section)
Add topic