CUSTOMER BANK ACCOUNT MANAGEMENT SYSTEM PROJECT PLAN 10 TH FEB Approved On. 20 Feb 2015 Page 1 of 11 Project Plan Approved By.

Transcription

1 CUSTOMER BANK ACCOUNT MANAGEMENT SYSTEM PROJECT PLAN 10 TH FEB 2015 Approved On. 20 Feb 2015 Page 1 of 11 Project Plan

2 Contents 1. INTRODUCTION Project Overview Scope of Work Project Milestones 4 2. Definitions and Acronyms 4 PROJECT PLANNING Software Development Life Cycle Requirements Change Management Effort Estimation Development Environment Support Documents 7 PROJECT TRACKING Tracking of Tasks Tracking of issues Status Reporting Project Measurements 9 PROJECT TEAM Project Organization Team Members 11 Approved On. 20 Feb 2015 Page 2 of 11 Project Plan

3 1. Introduction 1.1. Project Overview Project Name Customer Bank Account Management System Project Code NA Project Manager Dinesh Jethva Project Leader Asmita Lokhande Project Assistant NA Project Start Date 03 rd Feb 2015 Project End Date 03 rd May 2015 Customer Name & Contact Information SWABHAV TECHLABS PVT LTD Customer Bank Account Management System is a training project where in students emulate functionality required by a bank customer to do money transactions and manage his profile. It also emulates functionality required by an bank employee to manage an customer bank account when customer visits branch Scope of Work This project provides customer account management services which consists of opening an account, showing Account summary to customer, customer transactions at bank branch managed by an employee, payee registration, fund transfer to registered payee and all user profile management functionality. This project is implemented using various standard design patterns, maintains high code quality and designed to adapt and evolve to accommodate new requirements without affecting the existing operations. This relies on a modular architecture, which isolates the complexity of integration, presentation, and business logic from each other in order to allow easy integration of new technologies and processes within the application. Approved On. 20 Feb 2015 Page 3 of 11 Project Plan

4 1.3. Project Milestones Sr. No. Milestone Deliverables Delivery Date Sign-off 1 Responsible Person(s) 1 Requirement gathering SRS baseline 03 rd Feb 2015 Bhavesh Dinesh Jethva /Analysis Talsania 2 Detailed Design Detailed Design with related Document 13 th Feb 2015 Bhavesh Talsania Dinesh Jethva 3 "Coding, Unit Testing and Code Review" Application for testing with related documents 4 System Testing Tested Application with related documents. 30 th April 2015 Dinesh Jethva 30 th April 2015 Dinesh Jethva Asmita Lokhande Asmita Lokhande 2. Definitions and Acronyms Definition / Acronym / Abbreviation Stakeholder OS PL PM CEO Description Swbhav Techlabs Pvt. Ltd. Operating System Project Leader Project Manager Chief Executive Officer Approved On. 20 Feb 2015 Page 4 of 11 Project Plan

5 Project Planning 2.1. Software Development Life Cycle Customer Bank Account Management System will follow the standard development life cycle, however during the requirement phase, the cycle will be more iterative. During the testing phase also the cycle will be more iterative as the application is supposed to communicate with the external systems Requirements Change Management 1. Log the Changes Project Leader 2. Perform an impact analysis n the work Project Manager products 3. Estimate the effort needed for the Project Leader change request 4. Re-estimate the delivery Schedule Project Manager 5. Review the impact with senior Project Manager management 6. Obtain stakeholder sign off Project Manager 7. Rework work products Project Manager 2.3. Effort Estimation Life Cycle Stage Effort (hrs) Percentage of effort (%) Requirement gathering / Analysis Detail Design Coding, Unit Testing and Code Review Data Conversion / Migration System Integration Testing User Acceptance Test Training Implementation Maintenance Project Management Approved On. 20 Feb 2015 Page 5 of 11 Project Plan

6 Buffer hrs mm 2.4. Development Environment Hardware Software Developer PC: Core 2 duo with 2.2 Ghz or above 1 GB SDRAM 10 GB Free Space Database Server: Database Server: MySQL Server 5.1 Web Server Application: Tomcat6 Client Application: JDK: 1.6 MS Windows XP/7 Tools to be used Gradle 2.0 Eclipse IDE Cobertura Database to be used MySql 5.1 Any other tools (Documentation, Project Management, Analysis & Design tools etc.) MS Excel. MS word Approved On. 20 Feb 2015 Page 6 of 11 Project Plan

7 2.5. Support Documents Name Applicability (Y/N) (If applicable, give link to the document here) Quality Plan Y - Software Configuration Y - Management Plan Training Plan Y - Risk Management Plan Y - Staffing Plan Y - Resource Plan Y - Engagement Matrix Y - Test Plan Y - Reasons (If not applicable) Project Tracking Approved On. 20 Feb 2015 Page 7 of 11 Project Plan

8 2.6. Tracking of Tasks Activity Procedure Tool Used (if any) Scheduling Project Leader and Project MS Excel. Manager will track the schedule on daily basis Status Review Meetings 1.Project manager With stakeholder Weekly Every Friday with Project Manager, Project leader NA 2.7. Tracking of issues Issue Type Procedure Escalation Procedure The technical cell and project leader will handle technical issues. Project Internal issues & Support Issues Levels of Escalation are Level 1 Asmita (PL) Level 2 Dinesh (PM) Level 3 Bhavesh (CEO) Escalation will be through mails stakeholder issues The Project leader and project manager will handle the stakeholder issue with frequent discussions and meetings Levels of Escalation are Level 1 Dinesh (PM) Level 2 Bhavesh (CEO) Escalation will be through mails and meetings 2.8. Status Reporting Report to Report Name Frequency Approved On. 20 Feb 2015 Page 8 of 11 Project Plan

9 Report to Report Name Frequency CEO Project Status Weekly Review Report SQA NA NA Any other NA NA 2.9. Project Measurements Parameter Monitor progress against the schedule Monitor the project s costs and expended effort Monitor the attributes of work products and tasks. Monitor resources provided and used Monitor the knowledge and skills of project staff Document significant deviations in project planning parameters. Frequency of Responsibility Measurement weekly Project manager NA monthly Project manager NA weekly Project Leader NA monthly Project manager NA bi-weekly Project Leader NA monthly Project manager NA Recorded in Project Team Approved On. 20 Feb 2015 Page 9 of 11 Project Plan

10 2.10. Project Organization Project Manager Project Leader QC & I Team Member Team Member Approved On. 20 Feb 2015 Page 10 of 11 Project Plan

11 2.11. Team Members Nikhil Gawad Fardeen Shaikh Approved On. 20 Feb 2015 Page 11 of 11 Project Plan