FOR AROKA
High level implementation plan:
High level implementation plan of the business enterprise software application.
There are several phases that can be used to achieve this implementation.
The table below indicate the phases with their timelines.
|
SUBTASKS. |
TIMELINES. |
DURATION |
|
Project establishment. |
Comprises of the following activities: 1. Mobilization. 2. Project team formation. 3. Project plan detailing e.g. documentation and fine tuning. Deliverables of this phase are: 1. Project administration plan. 2. Project standards document. 3. Project board formation. 4. Project implementation committee formation. 5. Key users team formation. |
3-4 Weeks. |
|
· Communication plan formulation.
· Change control process. |
Activities: 1. Keep the stake holders informed. 2. Make documentation required for the project. Deliverables: · Well defined communication process. · Documentation. -Change protocol to be followed |
Two weeks. |
|
Procedure development. |
Comprises of the following activities which are iterative: 1. Process mapping. 2. Gap detention. 3. Work around identification. 4. Organizational impact analysis. Deliverables: 1. Business model through flow chart. 2. Customization design specification document for identified modifications. 3. Draft procedure manual. 4. Acceptance test plan and data. |
3 weeks |
|
Application software customization. |
Activities: 1. Program development. 2. Unit testing. 3. System testing. Deliverables: Customized unit and system tested application software. |
2 weeks. |
|
Acceptance testing. |
The aim of user acceptance testing is to exhibit that the system works. Deliverables: · Tested application software. · Updated procedure manual. |
3 weeks. |
|
End user training |
All identified end users will be trained in the specific functions they are needed to work. Deliverables: · End users trained as per training plan. |
5 weeks. |
|
Conference room trial |
This phase deals on the simulation of the actual business environment. Activities which are iterative: · Identification and entry of representative data. · Simulation of the business model. · Business model enhancement. · Finalization of procedure manual. Deliverables: · Final procedure manual. · Final business model |
2 weeks |
|
Data loading. |
Activities: 1. Data conversion and loading. 2. Establishment of access rights and passwords. Deliverables: · Data loading completed. |
3 weeks. |
|
Live trail. |
This phase allows users to work on the application software with real time data. Deliverables: · Live trial completed.
|
4 weeks. |
References
1. Yusuf, Y., Gunasekaran, A., & Abthorpe, M. S. (2005). Enterprise information and project implementation: A case study of ERP in Rolls-Royce. International Journal of Production Economics, 87(3), 251-266.
2. Shiffman, R. N., Michel, G., Essaihi, A., & Thornquist, E. (2004). Bridging the guideline implementation gap: systematic, document-centered approach to guideline implementation. Journal of the American Medical Informatics Association, 11(5), 418-426.
3. Dawson, J., & Owens, J. (2008). Critical success factors in the chartering phase: a case study of an ERP implementation. International Journal of Enterprise Information Systems, 4(3), 9.