Business Model Implementation and Enterprise Architecture - Part 6: Transition Concept
Transition Concept
The transition concept ist the main collection of documents and other resources containing the relevant information about the enterprise project. The transition concept has to cover the following topics:
- The detailed description of your business processes. This contains the result of the analysis of the target process landscape and the parts of the gap analysis which are relevant for the business process engineering. The business process section describes the destination of the enterprise project.
- The target architecture which does not inly comprise the software and application landscape. Target architecture means the complete overview about the desired business architecture (business processes and services, organisational structure, etc.). Then it means software, applications and IT infrastructure. It is very important to describe not only the architecture as a static picture but also the planned steps (and intermediate stages) towards this architecture as resulted from the gap analysis.
- The implementation concept is the actual recipe for doing the project. It contains the relevant information about:
- Methods to be applied during software design and development, service and support, business process engineering etc.
- Regulations to follow during the project, especially in connection with the reorganisation of employees.
- Organisational changes to be made.
- The technology to be introduced or changed during the implementation.
- Security aspects on technological level as well as on organisational.
- The complete setup of tools for implementation but also for operation of the new business model.
- Any resources needed for implementing the changes these are qualified employees as well as infrastructural or organisational resources.
- Any legal conditions to be fulflled or at least to be regarded, such as contracts with suppliers, environmental regulations, business specific or general laws, etc.
- Performance indicators to measure the progress and the success of the implementation.
- Any other implementation relevant information specific to your enterprise.
- The quality management plan defines the quality standards of the project deliverables and processes. It contains indicators to measure the quality standards and defines activities for quality assurance. The quality management plan should not be confused with the test management plan or even the test concept. Test management is an important part of quality management but the quality management plan goes much further.
- The change management plan with a detailed listing of all change managament related aspects. As a result of the project context analysis, the change management plan contains all drivers and obstructions as well as all persons, processes and organisational structures to be influenced by the change process. Furthermore, the change management plan contains a list of actions to be performed to keep the change process under control.
- The program and project management plan including program and project timeline, resource and budget planning, project reporting and project controlling guidelines.