Docstoc

Project Risk and Product Risk

Document Sample
Project Risk and Product Risk Powered By Docstoc
					      PROJECT RISK ASSESSMENT

      Project Name:                                                                Project Size:
      Project Manager:                                                             Date:
      Risk Score:                                                                  Risk Rating:

      Project Risk Score & Risk Rating Guidelines
      0 to 500:          LOW RISK
      501 to 900:        MEDIUM RISK
      901 or higher: HIGH RISK



      The Project Risk Assessment is a self-evaluation of the project risks by identifying activities that typically
      represent risk. By completing this worksheet at the time of Project Origination, you can provide additional
      information that is relevant to understand the potential impacts this effort might have.

      Review each question below and assign a risk rating of 0-40 based on the most relevant risk category item
      and its relevance to your project. Risk scores of 30 or 40 must be explained in the Comments
      column.

      The Project Risk Assessment - along with the Conceptual Business Case - will form the basis for any
      technical reviews appropriate during the origination process.

      If you have any questions about completing this document, please contact the PMO (Bill Kanfield
      kanfi001@umn.edu or 612-626-4223).
  #   Risk Category                                                                   Score        Comments
  1   Type of Project:                                                                        0
      - Maintenance (e.g., correct problems)                                                  5
      - Enhancement (e.g., add new features)                                                  10
      - Product introduction                                                                  10
      - Process improvement/re-engineering                                                    20
      - Upgrade existing software or applications                                             20
      - New development – replace existing automated system                                   20
      - New development – replace manual system                                               25
      - New development – develop system to support new business                              25
      - Pricing enhancement/installation                                                      30
      - Implementation of software package in-house                                           30
      - Outsourcing to external vendor                                                        40
      - Re-engineering of system’s architecture                                               40
      - Other:
  2   Impact to business operations (e.g., data/staffing/monetary):                           0

      - No impact                                                                             0
      - Limited                                                                               20
      - Medium                                                                                30
      - Major                                                                                 40
  3   Impact to the environment, customer, or University Services' reputation if              0
      the technology fails:
      - No impact, or no technology involved                                                  0
      - Limited impact                                                                        10
      - Moderate impact                                                                       30
      - Significant impact                                                                    40
  4   Outages required during the implementation:                                             0
      - None required                                                                         0



eb7f4efa-1895-4796-bf2b-95a58589e42e.xls                                                                        Page 1
      - Outages to be planned after business hours                                   20
      - Outages to be planned during business hours                                  40
  5   Number of years Project Manager has had a proven track record as a PM:         0

      - More than three                                                              2
      - One to three                                                                 5
      - Less than one                                                                10
  6   Number of project team members:                                                0
      - One to five                                                                  2
      - Six to ten                                                                   5
      - Eleven to fifteen                                                            10
      - Sixteen to twenty                                                            20
      - More than 20                                                                 40
  7   Project team adequately staffed to complete deliverables:                      0
      - Yes                                                                          0
      - No                                                                           40


  8   Number of vendors involved in the design and/or implementation of the          0
      project or technology:
  9   - None                                                                         0
      - One                                                                          10
      - Two                                                                          20
      - Three or more                                                                40
  9   Level of vendor support necessary for the technology after implementation:     0

              -   N/A (no vendors involved)                                          0
              -   No subsequent vendor support necessary                             0
              -   Minor support necessary (e.g., maintenance only)                   20
      -    Major support necessary (e.g., programming, upgrades, etc.)               40
  10 Will any of the vendor-supported processes or functions be outsourced?:         0

          - N/A (no vendors involved)                                                0
          - No, vendor will support all processes or functions after technology is   10
          implemented
          - Yes, vendor will outsource some of the processes or functions            20
      - Yes, vendor will outsource all of the processes or functions                 40
  11 Based on information today, project timeframe to complete project:              0

      - Less than four months                                                        5
      - Four to six months                                                           10
      - Seven to twelve months                                                       15
      - Twelve months or more                                                        20
  12 Does the project have a rigid due date (i.e., an end date that cannot be        0
     moved due to legal, regulatory, or for business or technology reasons)?:

      - No, end date is flexible & can be moved without affecting dependencies       0
      - Yes, project has a mandatory due date that cannot be moved                   20
  13 Amount and level of documentation currently available:                          0
      - Extensive and detailed documentation                                         0
      - Extensive documentation, but not detailed                                    10
      - Limited documentation, but detailed                                          20
      - Limited documentation, but not detailed                                      30
      - No documentation                                                             40
  14 Project Scope:                                                                  0
          - Scope clear, complete, and stable                                        0
         - Scope is documented, but has some unclear, incomplete, or have unstable   10
         high-level requirements
      - Minimal or no scope/high-level requirements documented                       20
  15 Number of organizational entities (besides systems) that need to be             0
     involved:
     - Zero                                                                          0
      - One to two                                                                   10


eb7f4efa-1895-4796-bf2b-95a58589e42e.xls                                                  Page 2
      - Three to five                                                                       20
      - Six to ten                                                                          30
      - Enterprise-wide                                                                     40
  16 Number of internal or external project interfaces (or handoffs between                 0
     groups; e.g., to X.500, EFS, PeopleSoft, vendor etc.):

      - N/A (no technology involved)                                                        0
      - Less than four                                                                      10
      - Four to twelve                                                                      30
      - More than twelve                                                                    40
  17 Changes to existing systems (including infrastructure) necessary in order              0
     to implement the technology:
          - N/A (no technology involved)                                                    0
            -     Limited                                                                   10
            -     Moderate                                                                  20
            -     Significant                                                               40
  18 Number of applications or systems that require changes or modifications                0
     to code (include need to test):
          - N/A (no technology involved)                                                    0
            -     One                                                                       5
            -     Two or three                                                              10
            -     Four to eight                                                             20
            -     More than eight                                                           0
  19 Estimated development and implementation costs for                                     0
     hardware/software/conversion:
     - N/A (no technology involved)                                                         0
      - Less than $75,000                                                                   10
      - $75,000 to $150,000                                                                 20
      - $150,001 to $250,000                                                                30
      - More than $250,000                                                                  40
  20 Legal & Regulatory Compliance impact:                                                  0
      - None                                                                                0
      - Limited                                                                             10
      - Moderate                                                                            30
      - Significant                                                                         40
  21 Will the Office for General Counsel or Purchasing be used during the                   0
     negotiation, creation, or modification of the contract?

         - No contract is required for project.                                             0
         - No, the existing contract will be used and no modifications or addendums will    5
         be required.
         - Yes, the OGC and Purchasing will be highly involved with contract                10
         negotiation, creation, or modification.
         - Yes, the OGC and Purchasing will be involved, but in a limited capacity          20
       - No, the OGC and Purchasing will not involved with the contract negotiation,        30
       creation, or modification.
  22 Availability of business partner and technology groups:                                0
         - N/A (no technology involved)                                                     0
         - Assigned to desired level of involvement and available immediately when          10
         needed
         - Assigned to desired level of involvement, but likely not available immediately   20
         when needed
         - Not assigned to the desired level of involvement                                 40
  23 Formal Request for Proposal process to be used during technology                       0
     selection:
          - RFP process is not required (N/A)                                               0
            - RFP process will be followed                                                  20
            - RFP process NOT to be followed                                                40
  24 Technology options that have been/will be explored or researched:                      0

         - N/A (no technology involved, or is an enhancement to an existing system or       0
         technology
         - Three or more                                                                    5
         - Two                                                                              10
      - One                                                                                 20


eb7f4efa-1895-4796-bf2b-95a58589e42e.xls                                                         Page 3
      - No additional options were considered                                                                          40
  25 Newness of technology (hardware, systems, databases, communication,                                                0
     etc.) used in the project:
           - N/A (no technology involved)                                                                               0
            - Technology is not new and has been proven or tested                                                       5
            - New to the business line                                                                                 10
            - New to University Services                                                                               20
            - New to the education/learning services industry                                                          40
  26 Has the technology to be used in the project been proven or tested                                                 0
     internally or externally?:
          - Yes                                                                                                         0
            -    No                                                                                                    40
  27 Number of years the project technology has been used in the organization:                                          0

      - N/A (no technology involved)                                                                                    0
      - More than three                                                                                                 5
      - One to three                                                                                                   10
      - Less than one                                                                                                  20
  28 Can sizing and capacity for technology be evaluated and incorporated into                                          0
     design?
          - N/A (no technology involved)                                                                                0
            -    Current and future sizing and capacity analysis is identified                                         10
            -    Only current sizing and capacity analysis is identified                                               20
            -    No sizing and capacity analysis can be identified                                                     40
  29 Project increases system capacity requirements for application:                                                    0

            -    N/A (no technology involved)                                                                           0
            -    Limited                                                                                               10
            -    Moderate                                                                                              20
            -    Significant                                                                                           40
  30 Is this project dependent on, or does it rely on any other projects or                                             0
     changes for support, testing, code changes, or other modifications or new
     implementations?:
           - No dependencies                                                                                            0
            -    One to two dependencies                                                                               10
            -    Three or more dependencies                                                                            20
  31 Type of third party connectivity (non-University Services connectivity) used                                       0
     in project or technology:
          - No third party connectivity                                                                                 0
            -    Existing third party connectivity involved                                                            10
            -    New third party connectivity involved                                                                 40
  32 Level of training necessary for customers and end-users:                                                           0
            -    None                                                                                                   0
            -    Limited training necessary                                                                            20
            -    Extensive training necessary                                                                          40
  33 Amount of training materials and documentation required for customer and                                           0
     end-users to use the new technology:
         - Limited or no documentation needed                                                                           0
            -    Limited documentation, but detailed                                                                   10
            -    Extensive documentation, but not detailed                                                             20
            -    Extensive and detailed documentation                                                                  40
  34 Additional project risks not previously addressed 1:                                                               0
            -                                                                                                        ___
            -                                                                                                        ___
      -                                                                                                              ___
      -                                                                                                              ___
      -                                                                                                              ___
                                                                                                                        0
      TOTAL PROJECT RISK SCORE                                                                                              FINAL PROJECT RISK RATING: Medium High


      1
       Separately list and rank each additional risk not previously addressed that is unique to your business line, technology used, or project using the following scale:
      Low risk = 0-10; Medium risk = 11-20; High risk = 21-40. Add additional lines as needed.



eb7f4efa-1895-4796-bf2b-95a58589e42e.xls                                                                                                                                     Page 4
     Project Risk Score & Risk Rating Guidelines
     0 to 500:       LOW RISK
     501 to 900:   MEDIUM RISK
     901 or higher: HIGH RISK




eb7f4efa-1895-4796-bf2b-95a58589e42e.xls           Page 5

				
DOCUMENT INFO
Description: Project Risk and Product Risk document sample