Project Closure and Postmortem Analysis

The assignment provides a detailed postmortem summary of the deployment of an ERP system, highlighting the success and challenges encountered. It discusses the methodologies used, including the waterfall method, prototyping, and testing. The risk mitigation strategies employed are also examined, focusing on user familiarity, resource availability, future expansion, team work, and compatibility issues. The project status is evaluated, and future enhancement possibilities are discussed, along with implementation support and maintenance plans.

Project draft
Project:
Enterprise resource planning system for ABC Pvt. Ltd
Project closure
1. Postmortem Summary
After the deployment of the system, it has been of great use to the Company since the time used
to process different kind of services such as locating employee file, processing of the pay slips,
evaluating business progress in terms of profit and also maximizing profit since the number of
the personnel required are minimal. Despite all these success, deploying the system had to face
some challenges to ensure that it worked as required. At first the system went into a failure due
to compatibility issues as the hardware available which was a 32 bit processor could not run the
program which was meant to run on a 63 bit machine. Budget allocated was minimum so I had to
work under a tight schedule which proved to be straining.
1.1. Methodologies
At every stage different methods were used to analyses whether the system met requirements and
standard. During the Analysis stage, waterfall method was so important to analyze the resources
needed such as man power, finance, software and hardware (Ruparelia, 2010). Prototyping
was essential tool in coming up with the replica model of the proposed system during the design

phase. It helped in ensuring that the system was broken into units which would be easy to work
on.
Also, we were able to reuse waterfall approach so as to test the units of the systems before
compiling them into a single system, testing the acceptance of the system, its interface and the
wholesome testing of the system functionality. Training of the staff was to be carried out by the
team and some of the staffs who understood well its functionality.
1.2. Method Evaluation
With the right team, it is easier to work on any system and implement it. Also, when the right
kind of resources are available from the hardware and the software and better understanding of
the system requirements, it makes working on it even much easier. Helping the users understand
what the system implements is the key to ensure that there is no system apathy among the users.
1.3. Risk Mitigation
Gargeya & brandy (2005) in the journal Success and failure factors of adopting SAP in ERP
system implementation 501-516 stated that any the success of the project, there are things that the
programmer needs to address before deploying the application. They include;
a. How well are the users familiar with the system?
b. Are the necessary resources available?
c. Future expansion or integration of the system

d. The team work
If the programmer can be able to articulate those issues, all users will be able to work well with
the system thus making the work of deploying easy. With the right resources available, it makes
deploying work even easier and with minimum errors such as compatibility error. Future
expansion is the key as any software should be expandable and able to integrate with other soft
wares that are available in the market. Team work is the key in any project, different personnel
are gifted at different areas which may be another ones weakness thus working on units and later
integrating them (Gefen & Lichtenstein, 2008).
.
2. Project Status
The system was successfully launched and proved to be a key tool in helping the staff to do
arithmetic calculation fast than previous manual work and timely roll out of the pays lips of the
workers. Back up of the company files was created with ease of retrieving the files. The problem
encountered at first with the infrastructures was well handled by purchasing upgraded systems
that made easy for the installation of the system.
Staff and the board were completely happy with the system as the system maximized the profit
and minimized the work which forced some staff to work extra time to complete assigned work
in-time.
3. Future Enhancement
The system was installed with the prospects that there would be future enhancement of the
system if need be. Since changes are inevitable and technology keeps changing, if the future
upgrade was to be done the system gave a room for it such as connecting to the external sever so

as to make it a distributed system as the company intends to open branches countrywide hence
the need for a distributed system in future.
4. Implementation Support
So as to make the system successful, it was not without some of the staff who helped in tasting
process so as to ensure that all the requirements are met as they would be the one to be using the
system. They also helped in training other staff on how to use various functions and get acquitted
with it.
5. Maintenance Plan
In case of any setback to the system the IT staff were to work on it and reach for support in case
the problem seizes. Proper documentation of the system step by stem helped the IT staff
understand the logic fast.

1. References
1. Gefen, D., Wyss, S., & Lichtenstein, Y. (2008). Business familiarity as risk mitigation in
software development outsourcing contracts. MIS quarterly, 531-551. Retrieved from
2. Ruparelia, N. B. (2010). Software development lifecycle models. ACM SIGSOFT
Software Engineering Notes, 35(3), 8-13.
3. Chen, S., Osman, N. M., Nunes, J. M. B., & Peng, G. C. (2011). Information systems
evaluation methodologies. In Proceedings of the IADIS International Workshop on
Information Systems Research Trends, Approaches and Methodologies. Sheffield.
4. Kang, U., Tsourakakis, C. E., & Faloutsos, C. (2009, December). Pegasus: A peta-scale
graph mining system implementation and observations. In Data Mining, 2009. ICDM'09.
Ninth IEEE International Conference on (pp. 229-238). IEEE.
5. Gargeya, V. B., & Brady, C. (2005). Success and failure factors of adopting SAP in ERP
system implementation. Business Process Management Journal, 11(5), 501-516.
6. Morris, M. G., & Venkatesh, V. (2010). Job characteristics and job satisfaction:
understanding the role of enterprise resource planning system implementation. Mis
Quarterly, 143-161.