ATTENTION ( KIM WOODS) need done by sunday 11-5- 2017

profilebrowfjxrome25
WEEK3ASSIGNMENTEXAMPLEGLADWELL.docx

As out text indicates “Needs analysis refers to the process of thoroughly gathering, prioritizing, and documenting an organization’s HR information requirements, and it serves as a necessary input for the subsequent design and implementation of an HRIS. An HRIS needs analysis usually takes on a particularly prominent role in the analysis phase of an HRIS development project, prior to significant design and implementation activities. It is important to note, however, that the needs analysis for the HRIS continues through the entire systems development process because each stage in the process could lead to the identification of new needs for the HRIS. Consider some of the potential costs of not planning and conducting a thorough needs analysis (with Golaub’s Feedback):”

Potential Costs (from Kavanagh text)

Golaub’s Response

Users reject an HRIS that fails to provide the functionality they need.

If the HRIS is not designed to meet the needs of the end user, it will be rejected

Vendor software packages are selected based on incomplete, inaccurate, or irrelevant criteria.

When choosing software packages, the needs analysis needs to be referenced.  Why invest in software that does not meet the indicated needs.  Additionally purchasing software with features that will not be used (irrelevant criteria) is a waste.

Costly custom systems are developed and built based on arbitrary data.

The data needs identified must be relevant.  Investing thousands of dollars in a customized system with irrelevant data only leads to a need for “another new HRIS.”

Custom additions to the HRIS are required to fill needs after implementation, as these needs were not properly identified during the needs analysis.

A lack of planning and ensuring that (as is quoted above) “the needs analysis for the HRIS continues through the entire systems development process,” can lead to “add-ons-forever”

Scope creep occurs because of growth in the goals, functionality, and requirements of the HRIS without adjustments to the time, cost, or resources allocated to the project.

Scope creep generally refers to unpredicted or unexpected changes in the scope of the HRIS project, without additional funding, time, etc.  As needs change, or continue to grow during the project, it can negatively impact the success/implementation of the system if these possibilities were not considered. Simply stated, extra time, resources and money should be included in the initial project proposal, in the event of unexpected changes.