ERP implementations cannot be successful unless supported by a realistic
project plan. In making the project plan for SAP R/3 implementation, one best practice is to work backwards. By working backwards on the project timeline, it becomes clear as to what are the critical paths within the project and where time can be saved. In one of my earlier posts, I had discussed some of the key milestones in an ERP implementation project. Taking an examples of SAP R/3, common milestones may include:

1. Getting a SAP Project Management Team ready
2. Designing the SAP data center
3. Making the required hardware available on time
4. Getting the SAP development environment ready for SAP developers

Each of the above activities need to be completed on time for the overall SAP R/3 implementation project to complete on time. Activities which lie on the crtical path and on which other activities depend for their start, need to be identified. Out of the activities listed above, having a SAP project management team is a pre-requisite for selection of hardware. Unless this is complete the other activities cannot start. Successfully implementing SAP R/3 requires more than good project management. Factors such as management commitment, integration with legacy systems, user buy-in are also important in achieving the go-live date.

Related Posts

SAP Audit Information System
SAP GL Account Postings
SAP Transport Management System
SAP R/3 Auditor Authorizations