Risk Management 101: Raising a Risk
March 4, 2008 | Author: admin | Filed under: Risk Management, Risk Identification
Risk Management 101: Raising a Risk (#2 in the series Risk Management 101)
By Craig Brown
Different project managers and business analysts have different approaches to risks. Some only want important risks flagged others only want risks flagged that are specifically related to the project’s scope and others, like me, like to capture all risks identified by the project team and stakeholders. The important thing to remember is what you’re there to do, and how risk identification can help or hinder your efforts.
Regardless of the threshold for entry onto your risk register it is critical to have one and to pro-actively manage risks. Many projects hold risk workshops early in the project and leave it at that. Some hold risk workshops at the beginning of each phase of the project and others hold weekly or fortnightly risk meetings where issues are raised and managed.
The savvy project manager has a team that are always identifying and managing risks, and using meetings as a forum for managing the most complex and important ones.
Craig Brown has worked as a project manager and business analyst mainly in the Australian ITC and the banking industries. He has also worked in the law, education and welfare industries, including starting a law firm. Craig now has a Master’s degree in project management from RMIT university, and is currently working with a Melbourne based IT consulting firm called OptimiseIT. Craig’s personal blog can be found at http://betterprojects.net.
Related Articles
No comments yet.
feel free to leave a comment
Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!
XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>
All fields marked with " * " are required.







