Software implementation methods

Description of the Administration

Sanolabor is a big sized selling and distribution company in Slovenia. It chiefly deals with health care, pharmaceutical and laboratory equipments acquired from more than 500 makers and providers both internationally and locally ( Sanolabor. Corporate Profile [ Online ] ) . In 2000 the company was awarded an ISO 9001:2000 quality direction certification for its proviso of quality services.

The company is divided into two chief parts ; the retail subdivision which was apparatus to cover with individualized demands ( Sanolabor. Retail. Offer [ Online ] ) and the sweeping section which supplies wellness establishments, scientific establishments and industry with merchandises like ; research lab plans, medical and hospital equipment and a scope of other commercial merchandises ( Sanolabor. Wholesale [ Online ] ) .

Description of the Implementation Method

Sanolabor decided to roll-out their new Customer Relationship Management ( CRM ) utilizing the rapid execution. Software execution methods ( Anon. , 2001, pg39 ) suggests This technique is used to deploy systems whose faculties have already been predefined taking to a fast and direct alteration over from the bequest system to the new one, as a consequence companies are sometimes forced to alter their concern processes to suit the system. In Software execution methods ( Anon. , 2001, pg39 ) Rapid execution is categorized into two parts there is: The preconfigured faculty where the user accepts the basic constellation of the system and the predefined concern procedures and the Vanilla Implementation where the user gets to analyse and take the map parametric quantities of the already preconfigured package. Some of the advantages that come with Rapid execution are:

  1. The undertaking costs less.
  2. There is speedy determination devising.
  3. There are minimum concern breaks while implementing the system.

Some of the disadvantages of utilizing this method are:

  1. Companies may non hold clip custom-make the package to suit their concern procedures.
  2. Most of the clip the top direction is required to take part and do speedy determinations.
  3. It is normally inflexible and delivers a system with limited functionality.

Summary of instance survey

Sanolabor decided to follow a Microsoft Excel-based system due to the addition of planetary competition and rapid alteration in the market. The system would assist the company supervise client information and bring forth analytical studies but because of its engineering it became unstable and could non work decently. Sing that a alteration was needed a undertaking squad was setup its undertaking was to present a to the full functional CRM system. The undertaking commenced on January 2006 and its timeline was set to one twelvemonth, the first aim of this squad was to look for a seller who would be able to supply a system whose characteristics replicated the old one together with some improved maps.

The seller ‘s first undertaking was to capture user demands and within a short clip the first paradigm was delivered. By this clip the undertaking squad had grown to 42 people, they were divided into three groups and sanolabor ‘s computing machines were chosen as a testing environment. A preparation session was held in July and failed due deficiency of proper planning. Two months subsequently another preparation session was constituted and because of better be aftering the consequences were deemed successful.

Data migration was initiated following and completed without any challenges ; one time this was done the CRM was quickly implemented and shortly after jobs at the operational and managerial degree began to harvest up. Another job which was encountered was that 60 workstations crashed due to incompatibility issues with an interface developed by the seller, the company besides changed its concern procedures to suit the package. The system was monitored for four months with errors being reported to the seller and after subsequent corrections were made it became stable and the undertaking was closed in March 2007. ( 286 words )

Critical analysis of the success of the execution method used

Bing that sanolabor did non see the concluding version of their CRM system during the proving session, it was an unadvised move to quickly implement the new system. In a systems development life-cycle all members of a squad set abouting a undertaking must be actively involved, the undertaking director should understand his/her function and every activity must be planned and monitored. In sanolabor ‘s instance the undertaking squad left all the work from the analysis to the execution phase to the package seller. No enterprise was taken until jobs started to happen in the latter phases of the development life-cycle and as a consequence it ended up being dearly-won for the company in footings of resources and clip.

Harmonizing to package execution methods ( Anon. , 2001, pg41 ) one should thoroughly measure to find where rapid execution is appropriate for your organisation, this rating was non done decently even though the implementing undertaking of the new CRM system into the company was successful. Below is a elaborate history of the challenges and the result that lead to a successful CRM execution. These experiences were both shared by the undertaking squad and the package seller.

In order to successfully implement a system in a real-work environment one must understand the concern needs every bit good as user demands of that company and good preparation guidelines must besides be followed, sanolabor ‘s CRM undertaking lacked these properties and as a consequence the company faced a batch of jobs in the execution stage. After choosing a seller the undertaking squad decided to utilize the vanilla execution to deploy the system, hence a batch of loops to the parametric quantities were done in conformity to the users ‘ demands, the result was that the undertaking director did non see the concluding version of the system ( Franka & A ; Armand, 2007 ) . The first jobs began to demo up in the preparation stage ; the users were unhappy because of the manner the Sessionss were carried out. ( Sanolabor, 2006e cited in Franka & A ; Armand, 2007 ) gives an history of the issues that were faced during preparation:

  1. The user demands were inadequately fulfilled i.e. non all the maps performed as the user expected.
  2. The employees had a negative attitude towards the CRM because they feared that the work burden would increase and the company ‘s organisational construction would alter, therefore their motive was low.
  3. The undertaking squad had grown to 42 people by this clip which made it excessively big for proper preparation to take topographic point.
  4. A suited preparation environment was non carefully chosen. It was done with sanolabor ‘s old computing machines which were really slow and lacked the capacity to back up the package.
  5. Due to the big figure of users that were supposed to be trained and the handiness of clip, the Sessionss were excessively short and did n’t supply sufficient information of the systems functionality.
  6. The user manuals were besides unequal because they did non reflect the proper guidelines of how to utilize the CRM.
  7. The preparation was conducted unprofessionally.

Because the above result had to be rectified, the undertaking squad took charge of the undertaking and started by make up one’s minding to carry through the user demands foremost, one time this was complete they moved to prove it and it was done to a satisfactory degree. The following measure after successfully finishing the first two activities was developing. These Sessionss took topographic point two months subsequently after the initial attempted and in order to obtain successful consequences a different attack was taken. The undertaking director take to ( Franka & A ; Armand, 2007 ) :

  1. Motivate the user groups by giving them confidence of better things to come, this ensured cooperation.
  2. Reduce the undertaking squad significantly to 21 people: seven users per group this ensured manageableness,
  3. Add the Sessionss to three hours from the old 45 proceedingss this gave the users ‘ ample clip to prove the system.
  4. Improved the user manual, this lead to a better apprehension of the system.
  5. Upgraded the computing machines that were at sanolabor to back up the CRM.

The consequences of the 2nd preparation were positive as it could besides be seen from the users. The following measure was to migrate the information from the bequest systems to the new CRM solution ; this was done without any jobs. After the preparation and informations migration was completed successfully, the squad was now certain that the system was ready to ‘go unrecorded ‘ . It was quickly implemented and shortly after jobs began to happen: at the operational degree Franka & A ; Armand ( 2007 ) study that ‘reclamations grounds was uncomplete, print of demands was inconsistent with demands, communicating between merchandise directors was hindered ‘ and for the analytical degree ‘reports did non present contents sing certain filters, other studies were impossible to obtain ‘ . Sanolabor besides wanted to utilize Microsoft Outlook together with the CRM solution, this prompted the seller to come up with an interface that would incorporate both. Franka & A ; Armand ( 2007, pg.205 ) writes that the:

‘Purpose was to put in the interface on all of the 60 working Stationss automatically, but it happened that the basic Microsoft system crashed down. Companies or providers proficient sup­port did non expect instability, which could ensue from such operation. It caused extra costs to the company ; purchasing new licenses and probationary support with installing of new programmes on all working Stationss ‘ .

Due to the dictates of utilizing the rapid execution method sanolabor had to alter their concern processes to suit into their new system this did non do any jobs because they were already client oriented. The execution procedure was monitored for four months where the undertaking director consistently reported errors to the provider and checked on its public presentation ( Sanolabor, 2006b cited in Franka & A ; Armand, 2007 ) .

Company decided to travel with an analytical CRM for the intent of leading, activity monitoring of employees, better inform­ing, betterment of dealingss with clients and better strate­gic determinations. It gave the replies to employees, why company decided to upgrade CRM. All this can act upon on the betterment of the general relationship with custom­ers. After going stable in March 2007 the undertaking officially closed.


  • Sanolabor. Corporate Profile [ Online ] Available at: hypertext transfer protocol: // IDPodPodrocja=442 [ Accessed 1 March 2010 ] )
  • Sanolabor. Retail. Offer [ Online ] Available at: hypertext transfer protocol: // IDPodPodrocja=445 [ Accessed 1 March 2010 ] )
  • Sanolabor. Wholesale [ Online ] Available at: hypertext transfer protocol: // IDPodPodrocja=440 [ Accessed 1 March 2010 ]
  • Franka Piskar & A ; Armand Faganel, 2009. A Successful CRM Implementation Project in a Service Company: Case Study. [ pdf ] Slovenia: Organizacija volume 42 Available at: hypertext transfer protocol: // [ Accessed 30 February 2010 ]
  • Anon, 2001. Software Implementation Method. [ pdf ] Available: hypertext transfer protocol: // [ Accessed 27 February 2010 ]