Global Computers, Inc.

'We deliver only the best'

		60 6253 6587 \| Call Today!

Main Menu

Home

Phase 1

Phase 2

Phase 3

Phase 4

Phase 5

Sitemap

Final Project Report

Final Project Documentation for

Coding Performance Improvement Project

Prepared by: Ng Choy Moon Date: 20^th Oct 2004

I. Project Description

This project was initiated to solve Global Computer Inc. current problem. The main issue in this project is that Global Computers does not fully utilize its character as a computer company as it does not use computing power economically as many programs are not coded for efficiency. Thus, the company spends hundreds of millions of dollars for supercomputers and mainframe computing powers. The project objectives are as below:

· To improve programs’ efficiency

· To reduce the number of supercomputers and mainframes

· To save costs by reducing computing power

The cost estimation of this project will be $220,000 to modify coding, and another $500,000 is to implement the newly coded program into existing running system. We have scheduled the project to be completed within 6 months, which starts at September 2004 and ends at March 2005.

II. Project Proposal and Backup Data

a. Proposed Projects Summarization

Please refer to page 1

b. Weighted Decision Matrix

Please refer to page 4

c. Job Description of Project Manager

Please refer to page 5

d. Dream Team

Please refer to page 14

e. Team Contract

Please refer to page 17

f. DMAIC Process

Please refer to page 26

g. Project Status Presentation

Please refer to page 32

h. Final Project Presentation

Please refer to page 44

i. Benefit Calculation

Please refer to page 46

j. Earned Value Chart

Please refer to Exhibit E

III. Original and Revised Project Plans and Schedules

a. Project Charter

Please refer to page 12

b. Work Breakdown Structure (WBS)

Please refer to page 22

c. Gantt Chart & Network Diagram

Please refer to Exhibit C

d. Reviewed Gantt Chart

Please refer to Exhibit D

e. Cost Estimates

Please refer to page 23

f. Updated Cost Estimates

Please refer to page 39

IV. Deliverables

a. Business Case

Please refer to page 10

b. Stakeholder Analysis

Please refer to page 19

c. Scope Statement

Please refer to page 20

d. Impact Matrix

Please refer to page 4

e. List of Prioritized Risks

Please refer to page 4

f. Pareto Diagram

Please refer to page 31

g. Business Case - Financial Analysis

Please refer to Exhibit A

h. Updated Financial Analysis

Please refer to Exhibit B

i. Retrenchment Announcement

Please refer to page 41

V. Final Project Report

This project was carried-out in order to do recoding; improve the performance of the coding. This will increase the efficiency of the programs and reduce the numbers of supercomputers and mainframe consumed computing powers. The reduction in power supply will help the company to reduce operational costs drastically.

The programs were coded for more efficiency under the development within 6 months and with a final budget of $400,000. Thus, we can say that the project is completed successfully even though it was 25% over the allotted budget. To complete this project, we had used Microsoft Project 2000 to prepare network diagram and Gantt chart. We had also use Microsoft Word to prepare the documents and Microsoft Excel to generate histograms and Pareto diagram.

The drawbacks of this project were lack of sense of responsibilities amongst team members and being uncooperative. Team members just kept saying how to do things but did not pay attention to the details and get the work done. And if things continue this way, we were afraid the project might lag in schedule and over budget. The mentor for the project, Kevin, realized the impact and damages that they can bring to the project. Thus, Kevin had decided to reorganize the team, laying off three of the members, and recruiting new members of his own staff. The project had managed to complete on time, though it was a little over budget after the joining of new members.

There were changes in cost estimates and financial analysis as new members joined in and the project going behind schedule. But since there was no review meetings hold regularly, most of the mistakes were occurred during the first three months. This created wrong schedule and misleading financial information to the top management. Fortunately, we were still able to get return on investment (ROI) at year 1 after being over budget.

This project has had provided us useful experiences that will guide us to be more careful when preparing the financial information in the future. We will hold review meetings more frequently to make sure that everything is going on as planned. Communications among members will be improved in order to promote such smooth process of working as, understands the scope of the project, project goals and schedule, and also the required outputs and deliverables.