Spelling suggestions: "subject:"business processes -- data processing"" "subject:"business processes -- mata processing""
1 |
Addressing application software package project failure : bridging the information technology gap by aligning business processes and package functionalityKruger, Wandi 12 1900 (has links)
Thesis (MComm)--Stellenbosch University, 2011. / ENGLISH ABSTRACT: An application software package implementation is a complex endeavour, and as such it
requires the proper understanding, evaluation and redefining of the current business
processes to ensure that the project delivers on the objectives set at the start of the
project.
Numerous factors exist that may contribute to the unsuccessful implementation of
application software package projects. However, the most significant contributor to the
failure of an application software package project lies in the misalignment of the
organisation’s business processes with the functionality of the application software
package. Misalignment is attributed to a gap that exists between the business processes
of an organisation and what functionality the application software package has to offer to
translate the business processes of an organisation into digital form when implementing
and configuring an application software package. This gap is commonly referred to as
the information technology (IT) gap.
The purpose of this assignment is to examine and discuss to what degree a supporting
framework such as the Projects IN Controlled Environment (PRINCE2) methodology
assists in the alignment of the organisation’s business processes with the functionality of
the end product; as so many projects still fail even though the supporting framework is
available to assist organisations with the implementation of the application software
package.
This assignment proposes to define and discuss the IT gap. Furthermore this
assignment will identify shortcomings and weaknesses in the PRINCE2 methodology
which may contribute to misalignment between the business processes of the
organisation and the functionality of the application software package.
Shortcomings and weaknesses in the PRINCE2 methodology were identified by:
• Preparing a matrix table summarising the reasons for application software
package failures by conducting a literature study; Mapping the reasons from the literature study to those listed as reasons for project
failure by the Office of Government Commerce (the publishers of the PRINCE2
methodology); • Mapping all above reasons to the PRINCE2 methodology to determine whether
the reasons identified are adequately addressed in the PRINCE2 methodology.
This assignment concludes by proposing recommendations for aligning the business
processes with the functionality of the application software package (addressing the IT
gap) as well as recommendations for addressing weaknesses identified in the PRINCE2
methodology. By adopting these recommendations in conjunction with the PRINCE2
methodology the proper alignment between business processes and the functionality of
the application software package may be achieved. The end result will be more
successful application software package project implementations. / AFRIKAANSE OPSOMMING: Toepassingsprogrammatuurpakket implementering is komplekse strewe en vereis
daarom genoegsame kennis, evaluasie en herdefiniëring van die huidige
besigheidsprosesse om te verseker dat die projek resultate lewer volgens die doelwitte
wat aan die begin van die projek neergelê is.
Daar bestaan talryke faktore wat kan bydrae tot die onsuksesvolle implementering van
toepassingsprogrammatuurpakket projekte. Die grootste bydrae tot die mislukking van
toepassingsprogrammatuurpakket lê egter by die wanbelyning van die organisasie se
besigheidsprosesse met die funksionaliteit van die toepassingsprogrammatuurpakket.
Wanbelyning spruit uit gaping tussen die besigheidsprosesse van `n organisasie en
die funksionaliteit wat die toepassingsprogrammatuur kan aanbied om die
besigheidsprosesse van 'n organisasie om te skakel in digitale formaat wanneer `n
toepassingsprogrammatuurpakket geimplementeer en gekonfigureer word. Daar word
gewoonlik na hierdie gaping verwys as die informasie tegnologie (IT) gaping.
Die doel van hierdie opdrag is om te evalueer en bespreek in watter mate
ondersteunende raamwerk soos die PRojects IN Controlled Environment (PRINCE2)
metodologie kan help om die organisasie se besigheidsprosesse in lyn te bring met die
funksionaliteit van die eindproduk; aangesien so baie projekte steeds misluk ten spyte
van die ondersteunende raamwerke wat beskikbaar is om organisasies by te staan met
die implementering.
Die opdrag beoog om die IT gaping te definieer en te bepreek. Verder sal hierdie opdrag
die swakhede in die PRINCE2 metodologie, wat moontlik die volbringing van behoorlike
belyning tussen die besigheidsprosesse en die funksionaliteit van die
toepassingsprogrammatuurpakket belemmer, identifiseer. Swakhede en tekortkominge in die PRINCE2 metodologie is as volg geïdentifiseer:
• Voorbereiding van matriks-tabel wat die redes vir
toepassingsprogrammatuurpakket mislukking deur middel van die uitvoering van
literatuurstudie opsom
• Koppeling van die redes bekom deur middel van die literatuurstudie met die redes
vir projek mislukking geidentifiseer deur die Office of Government Commerce
(uitgewers van die PRINCE2 metodologie)
• Koppeling van al die bogenoemde redes na die PRINCE2 metodologie om vas te
stel of die redes wat geïdentifiseer is voldoende deur die PRINCE2 metodologie
aangespreek word.
Die opdrag sluit af met aanbevelings om die besigheidsprosesse in lyn te bring met die
funksionaliteit van die toepassingsprogrammatuurpakket en aanbevelings vir swakhede
wat in die PRINCE2 metodologie geïdentifiseer is aan te spreek. Behoorlike belyning
tussen besigheidsprosesse en die funksionaliteit van toepassingsprogrammatuurpakket
kan behaal word indien hierdie aanbevelings aangeneem word en tesame met die
PRINCE2 metodologie gebruik word. Die eindresultaat is meer suksesvolle
implementering van toepassingsprogrammatuurpakket projekte.
|
Page generated in 0.348 seconds