Scribd Logo
Upload

Welcome to Scribd!

  • 7 views

    2.2 HRIT Requirements Questionnaire

    Uploaded by

    Jorge Manuel Ramos Luza
    This document contains a questionnaire to help organizations validate high-level HRIT requirements. It includes questions organized under six categories: business objectives, future needs, system users, current problems, criteria for success, and assumptions/open issues. The questionnaire is meant to guide requirements setting and ensure vendors meet needs.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd

    2.2 HRIT Requirements Questionnaire

    Uploaded by

    Jorge Manuel Ramos Luza
    7 views3 pages
    This document contains a questionnaire to help organizations validate high-level HRIT requirements. It includes questions organized under six categories: business objectives, future needs, system users, current problems, criteria for success, and assumptions/open issues. The questionnaire is meant to guide requirements setting and ensure vendors meet needs.

    Original Description:

    HRIT Requirements Questionnaire

    Copyright

    © © All Rights Reserved

    Available Formats

    DOC, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document contains a questionnaire to help organizations validate high-level HRIT requirements. It includes questions organized under six categories: business objectives, future needs, system users, current problems, criteria for success, and assumptions/open issues. The questionnaire is meant to guide requirements setting and ensure vendors meet needs.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    7 views3 pages

    2.2 HRIT Requirements Questionnaire

    Uploaded by

    Jorge Manuel Ramos Luza
    This document contains a questionnaire to help organizations validate high-level HRIT requirements. It includes questions organized under six categories: business objectives, future needs, system users, current problems, criteria for success, and assumptions/open issues. The questionnaire is meant to guide requirements setting and ensure vendors meet needs.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    You are on page 1of 3

    HRIT Requirements Questionnaire

    What it does:
    This questionnaire allows organizations to validate high-level requirements with business sponsors using a well-defined
    set of criteria to select the best vendor that meets organization’s business needs and solves practical problems. Use
    these questions to ascertain company HRIT requirements under 6 major categories:
     Business objectives
     Future needs
     System users
     Current problems
     Criteria for success
     Assumptions and open issues

    How to Use it:


    Use this questionnaire to guide the requirements setting process and revisit this information throughout the vendor
    selection process to ensure vendors will meet all HRIT requirements.

    Instructions:
     Send this questionnaire to business sponsors and key stakeholders in the HRIT process.
     Business sponsors and key stakeholders should return completed questionnaire to HR or meet to discuss
    specific questions in greater detail.
     Synthesize and document results and revisit this information during the RFI, RFP, and vendor selection steps.

    CEB Corporate Leadership Council


    © 2015 CEB
    HRIT Requirements Questionnaire

    A. Determine Business Objectives

    1. What are your goals in developing this system?


    2. Who are the key stakeholders and users? Do their goals differ? If so, how?
    3. How do the system goals map to business goals?
    4. What is the most important business goal of the system?
    5. Will the system change the way you are doing things now?
    6. Will the system help you be more efficient? How?
    7. What are the system deliverables?
    8. What will the new system accomplish that is not currently accomplished manually or with
    other systems?
    9. What will the new system do?

    B. Determine Future Needs

    1. What business requirements will this system address?


    2. What information do you need from this system that you don’t have now?
    3. Is any of this data currently captured in any other corporate system?
    4. How would you like to see this information?
    5. What functionality do you need from the system?
    6. Are the data and/or functionality shared by other (many) business areas?
    7. If so, which?
    8. If the reports were dynamic, what would they do differently?
    9. How much historical information is required?

    C. Determine System Users

    1. Who will be using the system?


    2. What are the titles and roles of the people who will use the system?
    3. What are their levels of expertise?

    D. Determine Current Problems

    1. What are the current problems you face without the system today?
    2. What problems should this system solve?
    3. Do you have to do things manually that you would like to automate?
    4. Do you have performance problems that need to change?
    5. Do you have functional limitations that you would like to change?
    6. Are you using packages that force you to constrain your business functionality to the
    boundaries of the package?
    7. Which reports do you currently use? What data on the report are important?
    8. How do you use the information?
    9. Are there specific bottlenecks to getting at information?
    10. How do you analyze the information you currently receive? What types of data are used?
    How do you currently get the data? How often do you get new data?
    11. What type of ad hoc analysis do you typically perform? Who requests ad hoc information?
    What do you do with the information?

    CEB Corporate Leadership Council


    © 2015 CEB
    HRIT Requirements Questionnaire

    E. Determine Criteria for Success

    1. What is most important for success of the application?


    2. What do we need to accomplish to make this project successful?
    3. What do we need to change to make this project successful?
    4. What buy-in do we need?
    5. Are we lacking any critical elements such as budget, resource allocation, or support?
    6. What are training considerations for developers and users?

    F. Determine Assumptions and Open Issues

    1. List assumptions.
    2. List open issues, responsible parties, and resolution date.

    CEB Corporate Leadership Council


    © 2015 CEB

    You might also like

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy