| Project Charter | |||
| Project Name | Platform Migration | ||
| Project Sponsor | soontorn | Project Manager | DURG |
| Date of Project Approval | April 11, 2020 | Last Revision Date | May 9, 2020 |
| Project Description | This project is initiated to move current mainframe based internal ticketing application to a cloud platform that is built on service oriented architecture. Reasons for Migration: – The cost per transaction for mainframe-based systems has increased in recent years for a variety of reasons. – Vendor licensing costs have been going up. – Resources skilled in older technologies like COBOL are becoming harder to find and hire. Older technologies lack the coding practices and tools that come with newer frameworks, making it harder to modify and extend older systems. | ||
| Project Goal | – Better technical solutions for business processes and decisions – Reduce cost (licenses, mainternance, employee) – Increased performance – Increased productivity – Reduce complexity – Improve user experience – Retain core ticketing functionalities and business processes | ||
| Project Scope | – Analysis of Application and Check Complatibility – Implement new platform – Test Application Migration – Performance tuning – Data Correction and Issue Fixes – Live Data Migration and Support – On-site Support 1st Week when product was launched – Training to Operation Team – Maintainance and Support 1 Year | ||
| Duration and Budget | Time | 6 Months | |
| Budget | $ 400,000 | ||
| Project Deliverables | – Project Charter – Documented and approved System Architecture – Documented and approved implemenatation design – Documented and approved Business Requirements – Documented and approved Technical Requirements – Documented and approved non-functional requirements and service level agreements | ||
| Stakeholders | Name | Role | |
| AAAAA | Project Manager | ||
| BBBBBBBBB | Sponsor | ||
| CCCCCCCC | Sponsor | ||
| DDDD | Client | ||
| EEEEE | Client | ||
| fffff | Business User | ||
| MY one Lalla | Business User | ||
| GGGGG | Technology Director | ||
| HHHH | Technology Director | ||
| IIII | Vendor Delivery Manager | ||
| JJJJ | Finance Director | ||
| Risks | – Intricate Architecture – Application Dependencies – Architectural difference – Latency – Roll Back Strategy | ||