Horned Frog Banking Consolidation Project

Transcription

1 Project Charter Horned Frog Banking Consolidation Project Start: September 5, 2018 Projected End: April 10, 2018 Approval of the Project Charter indicates an understanding of the purpose and content described in this deliverable. By signing this deliverable, each individual agrees work will be initiated on this project and necessary resources are committed as described herein Approver Name Title Signature Date Dr. Whitten Project Sponsor DW 09/19/2018 Ryan Reynolds Delivery Manager RR 09/19/2018 Chris Evans Stakeholder CE 09/19/2018 Mark Ruffalo Stakeholder MR 09/19/2018 Page 1 of 7

2 Section 1: Business Case, Deliverables and Scope Excludes Business Case Horned Frog Bank offers a wide array of banking services to its customers. Making its debut in the industry in the year 2000, the bank has come a long way with its financial solutions. It comprises of 1000 employees working out of different locations in USA. Horned Frog Bank is headquartered in Houston, Texas with branches in various cities of New York, New Jersey, Illinois, and Colorado serving approximately 20 million customers and small firms. ity of our customers are in the health, logistics and manufacturing sector. The internal employees in the company use around 50 applications on a daily basis to provide services to our customers. Savings and Checking accounts, Loans, Mortgages and Merchant Services are some of the services that Horned Frog has to offer. The abiding vision of Horned Frog bank is to become the leader in the financial sector and be at the top of innovation. Our mission is to provide the best financial solutions and services to our customers, maintain market ethics, and focus on customer satisfaction. For our employees to serve our customers better, we have put together a consolidation project which addresses the following. Implement Single sign on for the 50+ web applications. This upgrade will provide easy access to the applications and saves time for our users. Another objective of this project is to revamp the user interface to bring uniformity for all our applications. Also, in order for the upper management to provide quicker feedback and approvals, we will make the applications compatible to mobile devices. This will reduce the Turn Around Time (TAT). We would also like to implement a web application dashboard which will comprise of number of services and cases resolved by the employees and the total TAT. The data for this dashboard is retrieved from the existent 50+ applications. The main purpose of the dashboard is to measure employee performance. The overall budget for this project is estimated to be $120,000 and the project time is expected to be 7 months. Deliverables Deliverabl e # Description Owner Business Goal/ Initiative D-1 Implementation of Single Sign On Change of Authentication Chandan Acharya To provide easy and faster access to users across all web applications D-2 Revamp of User Interface Mrinalini Dey To bring uniformity across all the applications hosted on multiple platforms Page 2 of 7

3 D-3 Implementation as Mobile Application D-4 Creation of Dashboard Application Sharon Priscilla Somya Sharma To allow senior management to provide faster approvals and feedback thus reducing the Turnaround Time (TAT) To track the number of resolved cases by each employee across all services. Aims at recording employee performance Scope Excludes Exclusion Data populated on User Interface Screen will not be altered Mobile application will not extend to Tablet and notepads Dashboard Application will not feature on mobile, tablets or notepads Exclusion Reason UI will not manipulate fields (add or remove existing fields) and not engage with the database as performing any new operation on database will consume more time and need more funds Application will not be featured or extended on tablets as it is beyond the scope of our budget. Dashboard application will be only a part of monitoring process through desktop logins and any extension will be beyond the scope, time and budget of the approved project Section 2: Assumptions, Constraints and Dependencies Assumptions Assumption # Description Reason for Assumption Impact if Incorrect A-1 Security is robust and comprehensive A-2 Any bugs that are found will be fixed within one month A-3 All 50 applications have a flexible UI Login to bank applications needs to be secure Prolonged bugs will be expensive and time consuming to fix as the project continues An adaptable UI will allow a seamless and effective revamp across all applications Critical Critical Page 3 of 7

4 A-4 Implementation of SSO and Change of Authentication will be integrated together A-5 Mobile application will be available to employees only over Level 7 (SMEs, Delivery Managers, Architects) Since both are related to the login process, integrating them together will be optimal Mobile application is primarily being developed for faster approvals from senior management Constraints Constraint # Description Reason for Constraint Impact if Incorrect Comments C-1 Budget is limited to $120,000 Business Constraint Impact to Cost C-2 The mobile application will be available on phones having following software versions or higher : ios v9.0 Android v6.0 Dependencies Technical Constraint Application will not work on phones with a lower OS than the ones specified Dependency # Description Reason for Dependency Impact if Incorrect Comments D-1 UI revamp needs to be completed before SSO implementation can start D-2 Mobile Application can be started only after the SSO is implemented successfully D-3 Dashboard creation is not dependent on any other project Front end changes should be applied before the back-end changes can be modified SSO needs to be working correctly in the workstations before mounting to the mobile application It is independent of the other aspects of the project Minor Page 4 of 7

5 Section 3: Schedule, Budget and Project Team Schedule Phase Schedule # Milestone / Chargeable Deliverable Planned Date Planning P-1 Business Case September 5, 2018 P-2 Signed Team Contract September 10, 2018 P-3 Project Charter September 19, 2018 P-4 Requirement Gathering Document September 21, 2018 Analysis A-1 Project Kick-Off September 24, 2018 A-2 Scope Statement September 26, 2018 A-3 Work Breakdown Schedule September 28, 2018 A-4 Stakeholder Analysis October 1, 2018 A-5 Gantt Chart October 5, 2018 A-6 PERT Diagram October 8, 2018 A-7 Project Budget Statement October 15, 2018 A-8 Quality Assessment Document October 19, 2018 A-9 Organization Team Chart & Responsibility Assessment Matrix October 24, 2018 A-10 Communication Plan October 29, 2018 A-11 Risk Assessment Document October 31, 2018 A-12 Risk Mitigation Plan November 5, 2018 A-13 Request For Proposal November 9, 2018 A-14 Proposal Evaluation Sheet November 14, 2018 A-15 Change Management Plan November 19, 2018 Implementation And Design I-1 System Design Document November 26, 2018 I-2 SSO Impact Analysis Document November 28, 2018 I-3 Authentication Change Analysis November 30, 2018 I-4 UI Design Layout December 3, 2018 I-5 Mobile Implementation Design Document December 5, 2018 Page 5 of 7

6 I-6 Dashboard Application Design Document December 7, 2018 I-7 Process Flows Description December 10, 2018 I-8 Design And Implementation February 1, 2019 I-9 Interface Specifications Document February 4, 2019 I-10 Test Plans February 6, 2019 I-11 Test Reports February 8, 2019 I-12 Unit And Integration Test Case Document February 12, 2019 I-13 Integration Test Results February 15, 2019 I-14 Issue Log And Resolution February 20, 2019 Operations And Hypercare O-1 Onsite Delivery And Setup February 1, 2019 O-2 User Acceptance Test Results February 22, 2019 O-3 Product Migration February 25, 2019 O-4 Cut Over and Go Live February 27, 2019 O-5 Post Production Review March 1, 2019 O-6 Production Support - Hyper Care March 8, 2019 O-7 Sign-Off Complete March 11, 2019 Budget Budget # Amount (USD) Source B-1 1,20,000 Executive Sponsorship Preliminary Project Team Role Name Project Sponsor Dr Whitten dwhitten@tamu.edu Project Manager Sharon Priscilla sharonpriscilla@tamu.edu Page 6 of 7

7 Design Architect Somya Sharma Business Process Consultant Offshore Delivery Manager Chandan Acharya Mrinalini Dey Section 4: Risk and Quality Considerations Risk Assessment Level The project is associated with very high level risks that have been described below High Level Risks Requirements Risk Requirements can be misunderstood in the initial phases Scope of the project may expand the requirements leading to delay Technology Risk Certain requirements may be more tedious to implement than initially planned End-user may not be satisfied with the UI/design leading to redesign and implementation Resources Risk Some resources may leave the project before it is completed Disagreement over the design and implementation, among the developers, may impact the project schedule Cost may increase due to delay in execution Initial Quality Considerations Ease of transition between the various applications Uniformity & Usability in the UI of the application Minimal downtime during handover of the end product Bugs found during the testing phase will be resolved in a month High severity bugs will be fixed in 7 days Page 7 of 7