Project Management

Implementation

3.1.1 Status Reports

A project milestone has to be set a baseline on the chosen implementation process and deliverance schedule.

3.1.2 Change Management (UAT)

In the process UAT to the new system the following testing were being implemented. The resultant outcome is needed to re-define new elements…….. eg…

3.1.3 Quality Assurance

To enable execute within short period of time, this project has adopted agile model and V-approach. Every function was presented to end users at the initial stage, which mutual agreement and a sign-off was executed before proceed into next step. This adaptation also benefit on testing steps, where team was able to design test case and perform testing accordingly right after the system deployment.

To ensure the best quality, the system was also being parallel run with existing system and compared with the desired and designated result. Several mock runs using artificial data were also conducted to verify system functionality, and an outcome analysis was based on these test cases. In furtherance toward verifying system effectiveness, limited testing also has been scheduled and executed base on the current live data that were migrated to new system.

3.1.4 Changeover

From the result of the conducted feasibility study, it was determined to change the system business unit by business unit rather than adopting the risky approach of direct changeover.

During the implementation, Singapore HQ office was the first Business Unit to implement the system, using direct cut over method. However, due to maintain data integrity between old system and new system before fully implement, a temporary solution was adopted replication of data from the new system to old system was being implemented as well.

After 2 weeks of implementation, the same method was being replicated to other business units within South East Asian region with Malaysia being change over initially, followed by Brunei, Philippine, Vietnam,...