Required Considerations When Acquiring Computer System Case Study

806 Words 4 Pages
Required Considerations when Acquiring Computer Systems

Introduction

The majority of businesses today rely on some sort of computer or IT system, regardless of the business’ size. The integration of a computer system into a business is not a decision to be taken lightly, as it can be a significant expense to purchase hardware, develop and install software, and train employees on specific procedures.

The Failure of a System: Novopay

In August of 2012, a new salary payment system for those in the educational sector was rolled out, and was quickly found to be riddled with errors, with over 8000 logged errors in the first four months of operation (Kroenke & Hooper, 2013). Whilst the majority of employees received their correct pay check on
…show more content…
Despite popular media opinion, it is important to remember that the failure of the Novopay project is not due to the lack of consistent user training – the system itself has inconsistencies and that is what is at fault (Hubbard, 2012).

Project Faults

Kroenke and Hooper (2013) cite five key components for project management when implementing new computer systems. These are purpose, scope, time frame, cost and quality. It appears that there is a significant mistake made within each component of project management, all contributing towards the failure of Novopay.

Purpose

Novopay was planned as a payroll system, handling the salaries of over 100,000 employees within the education sector, and dealing with over 10,000 different pay combinations (Kroenke & Hooper, 2013). Once released for use, it was apparent that Novopay was not able to successfully meet its
…show more content…
With Novopay, delays pushed back the release by two years (Kroenke & Hooper, 2013). The developer behind the Novopay project, Talent2, failed to meet agreed deadlines as outlined in the contract, which consequently created a lack of trust between collaborators, causing a working relationship breakdown. With already having a deadline that was significantly pushed back, there was pressure to release the system for nationwide use in the education sector. When both developer and Ministry decided on a live release date, they both knew that sufficient testing of the product had not been completed, and that members of the sector had not been appropriately trained. Coding of the software was also still being completed at this time (Jack & Wevers,

Related Documents