1. Coding Performance Improvement Project Presented by: Tajul Ariffin Shahul Hamid

2. Team Members  Kevin Project Leader  Tajul Ariffin Shahul Hamid Team Member  Chong Soon Yong Team Member  Adora Affandi Tan Team Member

3. Team Members  Anu Ratha Kunalan Team Member  Sherwina Team Member  Alex Team Member

4. Project Sponsors  John CEO, Global Computers Inc.  Mary CIO, Global Computers Inc.

5. Project Objectives  To develop improvements to the current system that would increase efficiency while reducing cost By reducing the numbers of mainframes and supercomputers needed by the organization  To accomplish the target within the specified set target budget and time deadline

6. Project Initiation  We sat down and discussed potential projects that would have high-payoff and help improve operations and decrease costs  We did research on previous coding improvement projects once we figured that it was the primary choice to fulfill the organization’s goals  Prepared business case and project charter  Submitted to Mary for consideration of the Board

7. Project Planning  Attended 5-day Six-Sigma course as prerequisite for project leader role  Acknowledged Mary & Kevin as project sponsor & mentor and invited them to attend first team meeting  Discussed overall project backbone and overview  Allocated all necessary tasks for preparation of relevant project documentation (e.g.: Team Contract, Scope Statement, Stakeholder Analysis…)

8. Project Planning  Designed and formally accepted a rough work breakdown structure that would be used as a guideline for task distribution and prepared a relevant Gantt chart from this WBS as a tentative measure to progress  Created an early estimate of project costs and possible changes needed to make the budget  Listed down all possible and prioritized risks for the project  Submitted all work & findings to Kevin

9. Project Execution  The group initially chosen was a very opinion driven group  Every one had their own ideas and opinions on how things should be done  No one on the team was very clear about the importance of the Six-Sigma procedures especially the programmers  They argued that it was a waste of time  This created disparity in the team harmony

10. Project Execution  Had a group meeting on the current challenges being faced by the project team  Consulted with Kevin on the issue  Made short presentation about the project status to the Six-Sigma Steering Committee  Developed project Web Site

11. Project Controlling  Due to decision for Six-Sigma Steering Committee, stepped down from role of team leader and allowed Kevin to take over the reigns  Prepared revised working Gantt chart  Updated cost estimate and prepared project financial analysis  Had an appraisal meeting with members of former team who were dropped

12. Project Closing  Prepared lessons learned report and final project report to be handed in to Steering Committee  Reported to Steering Committee on how financial benefits of project could be calculated and automated  Updated project Web Site

13. Conclusion  This project was successfully completed even though it costs fractionally more than originally planned  The benefits, as outlined in the project documentation, can be realized in just a year of implementation  This project has highlighted the importance of team knowledge in Six-Sigma procedures of a Six-Sigma project is to be carried out smoothly  This work has also highlighted the precedence and need for a core group of project managers with Six-Sigma training and know-how