Casual Articles
#1 in Business Subscribe Email Print

You are here: Home > Internet and Businesses Online > Ecommerce > Managing Project Risks and Issues

Tags

  • should
  • order
  • project objectives
  • certain risks
  • system based

  • Links

  • Get Your 3 Free Credit Reports Now, Did I Mention They were Free?
  • Are You Ready For Your Motorcycle Track Day? Part I
  • How To Find Golf Instruction Online Free
  • Casual Articles - Managing Project Risks and Issues

    Let the Gimmicks Go
    Gimmicks are cute but they do not give you the aura of professionalism. Of course, it depends on what you are planning to do with your business. If you are selling Clown services, then use all the gimmicks you can find. If you are a serious accountant, then the gimmicks should go or at least be downplayed. By gimmicks, I mean the one liners that follow you company name and logo. For example I saw a sign outside a pet store that was trying to sell pet
    p>For each risk, one should enter a counter-measure in the risk plan. Where a risk can be eliminated, then this will be the counter-measure. Where it cannot be fully eliminated, then risk mitigation actions will be the most appropriate.

    Issues Log

    A Risk is something that is yet to happen, whilst an Issue is something that has already happened. It may well be convenient to use the Risk Log to also track any issues on the project. Issues will generally fall into one of the following ca

    The Importance of Image in Business Communications
    As a parent, I try to teach my children to look beyond people’s appearances, and not to judge others based on if they’re wearing the latest fashions, or if their appearance is not as aesthetically pleasing as others. We live in a world where we are bombarded by messages that material things matter. While we may aim to teach our children to look beyond the first impression to what the person is like underneath, we do not get the same opportunity in t
    Inherent (or Business) Risk

    Inherent Risk is the risk that exists in the environment around your portal project. It will tend to be unique to your organisation; it's culture and politics. For example, if you have a fragmented business (either geographical or functional), then this will create a higher inherent risk of poor communication.

    Project (Specific) Risk

    Project Risk is the risk specific to your project. Some Project Risk stems from the nature of what you are doing; there are certain risks common to any project (e.g. the unfamiliarity to users of the technology you are deploying). However, most project risk is under your direct influence; for example the skills of the project team, the level of governance effectiveness and so on.

    Stage Risk

    Finally, there is 'stage risk' which is the risk associated with the particular activity of any given phase of the project plan.

    The Risk Log & Risk Plan

    In order to stay in control of the risks to your portal project, it makes sense to have a formal log of all risks, to which anyone involved with the project is entitled to add. You might use a formal workshop to first populate the log.

    Assessing Risks

    Each risk (however derived) can be assessed using a simple methodology, whereby the probability of the risk being realised ('likelihood') and the size of the impact on the project objectives ('severity') can be measured.

    The simplest system (based on the PRINCE project management method) is to give a score of 1-3 for likelihood and severity (where 1 is low and 3 is high). From these scores, the importance of each risk can be measured as the product of likelihood and severity.

    Clearly, any risk of importance 9 demands immediate attention, followed by risks rated 6 and so on.

    Risk Counter-measures

    The importance of each risk should be regularly maintained, based on the extent to which the likelihood and severity of impact change over time.

    For each risk, one should enter a counter-measure in the risk plan. Where a risk can be eliminated, then this will be the counter-measure. Where it cannot be fully eliminated, then risk mitigation actions will be the most appropriate.

    Issues Log

    A Risk is something that is yet to happen, whilst an Issue is something that has already happened. It may well be convenient to use the Risk Log to also track any issues on the project. Issues will generally fall into one of the following cat

    A Lesson for Budding Entrepreneurs
    RR Donnelley, the largest Commercial Printer in the world, was and is a great company to work for. My career was going just great – I had gained a reputation as a Troubleshooter and Turnaround Manager, perhaps also some would say a bit of a Maverick. Whilst I provided the drive and hands-on change management – Donnelley supplied the comfort of having a multi-billion dollar corporation behind me. Specialist staff, experienced operations people and top-
    ; there are certain risks common to any project (e.g. the unfamiliarity to users of the technology you are deploying). However, most project risk is under your direct influence; for example the skills of the project team, the level of governance effectiveness and so on.

    Stage Risk

    Finally, there is 'stage risk' which is the risk associated with the particular activity of any given phase of the project plan.

    The Risk Log & Risk Plan

    In order to stay in control of the risks to your portal project, it makes sense to have a formal log of all risks, to which anyone involved with the project is entitled to add. You might use a formal workshop to first populate the log.

    Assessing Risks

    Each risk (however derived) can be assessed using a simple methodology, whereby the probability of the risk being realised ('likelihood') and the size of the impact on the project objectives ('severity') can be measured.

    The simplest system (based on the PRINCE project management method) is to give a score of 1-3 for likelihood and severity (where 1 is low and 3 is high). From these scores, the importance of each risk can be measured as the product of likelihood and severity.

    Clearly, any risk of importance 9 demands immediate attention, followed by risks rated 6 and so on.

    Risk Counter-measures

    The importance of each risk should be regularly maintained, based on the extent to which the likelihood and severity of impact change over time.

    For each risk, one should enter a counter-measure in the risk plan. Where a risk can be eliminated, then this will be the counter-measure. Where it cannot be fully eliminated, then risk mitigation actions will be the most appropriate.

    Issues Log

    A Risk is something that is yet to happen, whilst an Issue is something that has already happened. It may well be convenient to use the Risk Log to also track any issues on the project. Issues will generally fall into one of the following ca

    How To Write A Super Bowl Ad
    Well, it's that time of year again. No, not the holidays. It's Super Bowl ad writing time.And all the big boys at all the fancy advertising agencies across the country are, as we speak, camping out at Starbucks and abandoning all thoughts of REM sleep, and disappointing spouses (yet again) in the unrealistic hopes of writing an ad that somehow makes it onto the Super Bowl.And they go through this pain and suffering because every one of t
    risks to your portal project, it makes sense to have a formal log of all risks, to which anyone involved with the project is entitled to add. You might use a formal workshop to first populate the log.

    Assessing Risks

    Each risk (however derived) can be assessed using a simple methodology, whereby the probability of the risk being realised ('likelihood') and the size of the impact on the project objectives ('severity') can be measured.

    The simplest system (based on the PRINCE project management method) is to give a score of 1-3 for likelihood and severity (where 1 is low and 3 is high). From these scores, the importance of each risk can be measured as the product of likelihood and severity.

    Clearly, any risk of importance 9 demands immediate attention, followed by risks rated 6 and so on.

    Risk Counter-measures

    The importance of each risk should be regularly maintained, based on the extent to which the likelihood and severity of impact change over time.

    For each risk, one should enter a counter-measure in the risk plan. Where a risk can be eliminated, then this will be the counter-measure. Where it cannot be fully eliminated, then risk mitigation actions will be the most appropriate.

    Issues Log

    A Risk is something that is yet to happen, whilst an Issue is something that has already happened. It may well be convenient to use the Risk Log to also track any issues on the project. Issues will generally fall into one of the following ca

    Tracking an Employee's Success or Failure
    When you have started any performance improvement plan with an employee, it is essential that you are doing your follow-up work in a timely manner.Once you have given your employee a memo or a probation letter with corrective actions that are needed and the corresponding deadlines, you need to mark your own calendar. When deadlines have been given, you need to be prepared to meet with the employee on each of those deadline dates to find out whe
    ct management method) is to give a score of 1-3 for likelihood and severity (where 1 is low and 3 is high). From these scores, the importance of each risk can be measured as the product of likelihood and severity.

    Clearly, any risk of importance 9 demands immediate attention, followed by risks rated 6 and so on.

    Risk Counter-measures

    The importance of each risk should be regularly maintained, based on the extent to which the likelihood and severity of impact change over time.

    For each risk, one should enter a counter-measure in the risk plan. Where a risk can be eliminated, then this will be the counter-measure. Where it cannot be fully eliminated, then risk mitigation actions will be the most appropriate.

    Issues Log

    A Risk is something that is yet to happen, whilst an Issue is something that has already happened. It may well be convenient to use the Risk Log to also track any issues on the project. Issues will generally fall into one of the following ca

    Fast Blog Traffic Four Ways- Boost Your Traffic In Days
    Your blog's set up, you've made some posts, and now you're ready for readers. How quickly you get blog traffic and readers is up to you - you need to promote your blog. Once you do, you'll see your traffic statistics gradually rising.Let's look at four ways which will help you to get an ever-increasing flow of traffic to your blog.1. Write Articles And Post Them To Article DirectoriesWeb site owners are always loo
    p>For each risk, one should enter a counter-measure in the risk plan. Where a risk can be eliminated, then this will be the counter-measure. Where it cannot be fully eliminated, then risk mitigation actions will be the most appropriate.

    Issues Log

    A Risk is something that is yet to happen, whilst an Issue is something that has already happened. It may well be convenient to use the Risk Log to also track any issues on the project. Issues will generally fall into one of the following categories:

    (R) - Request for a change (in the scope of the project);
    (O) - An item has been identified that is Off-Specification;
    (Q) - A Question has been raised that needs to be resolved;
    (S) - A Statement of Concern has been raised by someone; and
    (I) - Other issues.

    To score issues, just ascribe an importance score (of between 1 and 9).

    Managing Risks and Issues

    Once you have put a Plan in place, then it is important to regularly monitor and report on the counter-measures that have been deployed and whether or not they have been successful in reducing the overall risk profile of the project.

    For templates and examples of risks and issues pertinent to intranet portal deployment projects, please check out my chapter on Managing Risks and Issues in the (free to access) Intranet Portal Guide.

    If you act, manage and report regularly on risks and issues, you will have substantially improved your chances of project success!

    HTTP = HTML link (for blogs, profiles,phorums):
    <a href="http://www.casualarticles.com/article/61737/casualarticles-Managing-Project-Risks-and-Issues.html">Managing Project Risks and Issues</a>

    BB link (for phorums):
    [url=http://www.casualarticles.com/article/61737/casualarticles-Managing-Project-Risks-and-Issues.html]Managing Project Risks and Issues[/url]

    Related Articles:

    Trade-Marking Your Logo Design

    Organizational Culture and Creative Blocks - the Similarities

    Website Publishing and Google AdSense

    Bookmark it: del.icio.us digg.com reddit.com netvouz.com google.com yahoo.com technorati.com furl.net bloglines.com socialdust.com ma.gnolia.com newsvine.com slashdot.org simpy.com shadows.com blinklist.com