Beruflich Dokumente
Kultur Dokumente
GyanSys InfoTech Pvt Ltd. 1st Floor, Alpha Block, Sigma Soft Tech Park, Whitefield Main Rd, Varthur, Bangalore- 560066
Author
Date of change
Change reference
1. 2.
23/11/2011 29/11/2011
TABLE OF CONTENTS
INTRODUCTION ................................................................................................................................ 2 PROJECT MANAGEMENT APPROACH ................................................................................................ 2 PROJECT SCOPE................................................................................................................................ 2 MILESTONE LIST .............................................................................................................................. 3 SCHEDULE BASELINE AND WORK BREAKDOWN STRUCTURE .......................................................... 3 PROJECT CHANGE CONTROL PROCESS ............................................................................................. 4 COMMUNICATIONS MANAGEMENT PLAN ......................................................................................... 4 COST MANAGEMENT PLAN .............................................................................................................. 5 PROCUREMENT MANAGEMENT PLAN............................................................................................... 5 PROJECT SCOPE MANAGEMENT PLAN .............................................................................................. 5 SCHEDULE MANAGEMENT PLAN...................................................................................................... 5 QUALITY MANAGEMENT PLAN ........................................................................................................ 6 RISK MANAGEMENT PLAN ............................................................................................................... 6 RISK REGISTER ................................................................................................................................ 7 STAFFING MANAGEMENT PLAN ....................................................................................................... 7 RESOURCE CALENDAR ..................................................................................................................... 7 COST BASELINE ............................................................................................................................... 7 QUALITY BASELINE ......................................................................................................................... 7 APPENDIX A..................................................................................................................................... 7 SPONSOR ACCEPTANCE .................................................................................................................... 9
INTRODUCTION
The objective of this project is to implement various ERP modules viz. SD, FICO and MM at the client location. The project management plan outlines what needs to be delivered and when. This shall also be used as a monitoring tool by the business stakeholders and project manager to assess how the project is progressing through scope statement, schedule, resource, communications, procurement (server readiness), quality, risk and stakeholder management as well as project control and other subsidiary management plans.
Each of these phases has several activities and has deliveries associated with it. Each activity shall be closely monitored until its successful closure. The deliverables need an official sign-off from the sponsor before the start of the subsequent phase. The project progress shall be monitored through weekly meetings with the client. Once the initial scope is approved, any changes thereafter shall go through the proper change management process and need to be duly approved. Any other project related changes with respect to schedule or resources need to be appropriately communicated to the stakeholders. Communication with the client regarding decisions taken shall need to be documented and saved via email, appropriate templates, MOM etc. The subsequent sections contain appropriate templates that may be required to fill in to maintain the overall quality as the project progresses. For example, any risk identified should go in the risk management template etc.
PROJECT SCOPE
The following scope is taken from the charter and needs to be elaborated once the SOW is approved and released. 1. After successful implementation of this project Axim would be able to handle all its professional services transactions through SAP. 2. Professional services could be Invoice generation due to placement of a resource at a client location 3. Transactions generated catering to the training needs of a client. 4. Handling any other transactions that would be generated as a result of Axims engagement with a client. 5. The business need of Axim is driven by the fact that, once this project is implemented, they would be having an upper hand with the future client as they are already running on SAP. The clients could be where a candidate is outsourced or it could be a full implementation project. In either case Axim will have an advantage to close the deal. 6. The other business need is to train candidates in a more professional manner by giving them an exposure in the live ERP environment.
MILESTONE LIST
Following are the major milestones. Milestone Project Preparation Business Blue Print Solution development & Realization Final Preparation Go-live and training Description Provides initial planning and preparation Document business process requirements Implement business and process requirements Complete preparation for Go-live. Cutover to live productive operation and support. Date 2nd Dec 2011 16th Jan 2012 17th Feb 2012 8h March 2012 9th April 2012
Integration Test UAT Identify training audiences Finalize training materials Plan production support and cutover Final Preparation Transport from Quality to Prod Data migration Roles and authorizations User manual and support Conduct end-user training Decide Cut-over date Go-live and Support Begin Transitional Support Post-Project Review Close Project
3.d 10.d 1.d 1.d 1.d 13.d 1.d 2.d 1.d 5.d 3.d 1.d 20.d 14.d 5.d 1.d
2/1/2012 2/6/2012 2/6/2012 2/6/2012 2/6/2012 2/21/2012 2/21/2012 2/22/2012 2/24/2012 2/27/2012 3/5/2012 3/8/2012 3/13/2012 3/13/2012 4/2/2012 4/9/2012
2/3/2012 2/17/2012 2/6/2012 2/6/2012 2/6/2012 3/8/2012 2/21/2012 2/23/2012 2/24/2012 3/2/2012 3/7/2012 3/8/2012 4/9/2012 3/30/2012 4/6/2012 4/9/2012
Roles and responsibilities for schedule development are as follows: The project manager will be responsible for facilitating work package definition, sequencing, and estimating duration and resources with the project team. The project manager will also create the project schedule using MS Project 2007 and validate the schedule with the project team, stakeholders, and the project sponsor. The project manager will obtain schedule approval from the project sponsor and baseline the schedule. The project team is responsible for participating in work package definition, sequencing, and duration and resource estimating. The project team will also review and validate the proposed schedule and perform assigned activities once the schedule is approved. The project sponsor will participate in reviews of the proposed schedule and approve the final schedule before it is base lined. The project stakeholders will participate in reviews of the proposed schedule and assist in its validation.
Server readiness at client location. The plan is to use our own sand box in case there is a delay in server readiness. The delay could be managed during the blue printing stages as not too much of work is expected to be done on sand box during this period. Any further delay needs to be highlighted and discussed in the stakeholders meeting so that any project delay can be accounted for. Any other risk If any other risk is uncovered when the project progresses, they need to be documented and discussed in the weekly stakeholders meeting. The most likely and highest impact risks would need to be added to the project schedule to ensure that the assigned manager take the necessary steps to implement the mitigation response at the appropriate time during the schedule. Manager will provide status updates on their assigned risks in the weekly project team meetings. Upon completion of the project, during the closing process, the project manager will analyze each risk as well as the risk management process. Based on this analysis, the project manager will identify any improvements that can be made to the risk management process for future projects. These improvements will be captured as part of the lessons learned knowledge base.
RISK REGISTER
The Risk Register for this project is provided in Appendix A, Risk Register.
RESOURCE CALENDAR
Program Manager Project Manager FICO Consultant SD Consultant MM Consultant ABAP Consultant . Sudhindra Deshpande Prasoon Santhosh Sumiti Inayat Rajan
COST BASELINE
This is a fixed cost project as outlined in the PO.
QUALITY BASELINE
This section needs to be updated after finalization of business blueprint.
APPENDIX A
Axim_Project Change Management Template_SAP implementation_28112011_V1.docx
SPONSOR ACCEPTANCE
Approved by the Project Sponsor:
Date: ___________________