Project Closeout Report

Project Closeout Report

Allison Connolly
DeVry University
MGMT340 Business Systems Analysis
Professor Michael Bird

Project Closeout Report

2

The purpose of this report is to present all of the necessary

documentation and evaluations in order to finalize the system development
life cycle and perform a project closedown. The loyalty program that was
designed and implemented by Petries Electronics was a success; it was not
an easy process, as the both the development team and Petries employees
encountered many challenges in order to bring the project to fruition. There
were setbacks that threatened the success of the project, however with
slight extensions in time and budget constraints, Petries implementation
was successful.
The system was tested thoroughly for a substantial amount of time
(nearly a month) with real data in the Petries facilities. Critical metrics were
measured, and adjustments were made in order to improve the performance
and functionality of the system before normal installation. Operating the new
system along with the old system utilizing a parallel method proved to be
helpful for both the end users and the development team. The data traffic
that was utilized to test the system was nearly triple the amount of traffic
that is normally expected, however the system worked with no interruption
or issue. Minor changes that were required were completed in less than an
hour, without interruption to the end users.
The personnel that were assigned to this project were in fact highly
skilled and motivated, however their main job duties consumed the majority
of the time and resources that would have been beneficial to the project. All
of the personnel that were involved, from employees in marketing to the

Project Closeout Report

3

project design manager had something to offer to the project and its
success. In some circumstances, one idea inspired another idea that was
more beneficial to the project, leading to a more functional, higher quality
system.
There are four types of maintenance as described in the text.
Corrective maintenance is used to repair design and programming errors,
and should be where the vast majority of the priority lies. Adaptive
maintenance refers to modifying the system in order to support
environmental changes, while perfective maintenance adds new features for
use or improves the current system performance. Preventative maintenance
safeguards the system from future problems. Petries Electronics will need to
implement an easy-to-follow maintenance system for their loyalty program.
In discussions with the development team, it has been determined that the
system would likely need a major update in approximately five years; until
this occurs, the vendor will provide minor updates free of charge as agreed.
Log reports of performance metrics will be automatically sent to the vendor
every Friday for review and evaluation by the development team to
determine if minor updates need to be made. Due to the fact that the system
is web-based, maintenance and changes can be performed easily in nonpeak traffic hours. Careful analysis and review, along with a well thought-out
design, leads to the conclusion that only minor maintenance should be
required. Credit to the success of the system should also be given to the pilot

Project Closeout Report

4

system, as this allowed for any bugs or kinks in the system to be worked out
before the full project implementation.
Corrective maintenance is expected to begin during the first month
after the system has been installed and implemented. Adaptive maintenance
does not appear to be required, as many of the changes that we believe to
be needed were done through the numerous life cycles that the system has
gone through (including the pilot system). Perfective and preventative
maintenance can be done in the future, as our budget has allowed an extra
fee for the development team to perform this maintenance. Numerous
measures have been put in place that ensure that only minor maintenance
will be required in terms of preventative maintenance. These guarantees
include the fact that the system has been forecast to handle nearly triple the
size of our current client base and the fact that the minimal design on the
website, in conjunction with less pictures, ensure that the side will load
efficiently on web browsers and operation systems across the board.
To measure maintenance effectiveness, there are a number of factors
that should be taken into consideration. The number of failures, the time
between each failure, and the types of failures should be accounted for.
There has been a distinct process that will be made available for the
personnel of Petries to follow. A checklist has been created that must be
utilized for each instance of failure. The form is accessible via the companys
corporate network, and the information technology department should be
made aware of any failures that do occur, citing the checklist.

Project Closeout Report

5

In order to control maintenance requests and configuration

management, it is essential that the form mentioned above is accurately and
efficiently filled out, with the information forwarded to the IT department.
This form allows the user to provide a clear and concise picture of exactly
what the failure was, so that the IT department can forward the details to the
vendors development team for correction of the error. Performing this
process should minimize risks and assure flawless operation of the system.
There will also be a system put in place that allows the user sending the form
to IT to categorize the failure as needing immediate attention so that it may
be quickly resolved. The IT department will then categorize all requests on a
daily basis to ensure that the critical issues are dealt with first.
This project was an invaluable lesson to both customers and the staff
of Petries. A breakdown of how the project transpired from start to finish will
be made available, and will cover key lessons that were delivered during this
process. These include ensuring that all requirements are clear and
identified, as well as written down and laid out during the analysis phase of
the project. Timelines must be strictly adhered to, and decisions that affect
the outcome of a particular segment of the project need to be prioritized as
first. Another valuable lesson that should be taken away from this project is
that the collaboration and meeting of team members is essential to project
success; meetings that allow free expression of thoughts and ideas (as they
pertain to the project) will benefit the project and the company as a whole.

Project Closeout Report

6

In conclusion, it is with great certainty and pride to announce that this

system has made its way to production. Issues did arise throughout the
process, namely with communication and cooperation issues between
departments; these issues were dealt with in a timely and efficient manner.
The success of the project, along with the satisfaction of both customers and
employees, has strengthened the team and its members as a whole.

References
Valacich, J., George, J., Hoffer, J. (08/2014). Essentials of Systems Analysis and
Design, 6th Edition.

[Bookshelf Online]. Retrieved from

https://online.vitalsource.com/#/books/9781323312407/