The Open-IT Enterprise Transition Programme (ETP) is a customisable, comprehensive transitioning process for organizations of virtually any size or industry focus. It provides a practical, time-tested route, starting from where you are now, to the goal of an agile Enterprise Service-Oriented Architecture (ESOA). Our approach to ESOA normally involves a number of technologies and approaches, including the OMG’s Model-driven Architecture (MDA) and component-based development (CBD).

The primary goal of ETP is to simultaneously increase the capability of an organization to derive business benefits from ESOA while decreasing the risk inherent in any technology transition. ETP is also designed to demystify new technology by setting realistic and pragmatic goals and objectives that are useful to both the business and information systems organizations. First and foremost of these goals is to provide value to the business throughout the transition process.

ETP is a five-phase programme which can start tomorrow morning, will guide the organization through the desired transition during which a number of development projects will occur, and which ends when the organization has successfully completed the transition. The phases are:

·        Initiation – Work is done to define the goals of the transition in business as well as technical terms, the scope of the transition, the technical architectures to be applied, and the processes to be used. Specific foundation deliverables are produced, including a Strategic Transition Assessment Review and a Comprehensive Architecture review.
This phase typically lasts around eight weeks.

The goal of the Initiation Phase is to initiate the transition by defining the SureTran path, develop a transition plan and schedule along with suitable pilot project(s), and achieve an overall understanding of how the transition will progress through, potentially, multiple iterations. At the end of this phase the client will have a wealth of highly useful information and plans from which future decisions may be made. In short, the first stage can be thought of as defining what the transition will do, and why.

·        Concept – An initial project is chosen, and during its development the various concepts required for a full transition are defined, implemented, and tested.
This phase, depending on the project chosen, can take around six months, and it is normally possible to see value added by the end of this phase.

·        Implementation – the ESOA concepts developed and tested in the Concept Phase are rolled out to a wider number of projects (perhaps three or four), so expanding the skill base, and further enhancing and cementing the ESOA concept implementations.
This phase can start before the end of the Concept Phase, and lasts in the order of twelve months.

·        Consolidation – The lessons learned during the Implementation Phase are consolidated, and the full roll-out of the ESOA approach is planned.
This phase takes around two months to complete.

·        Replication – The ESOA development capabilities acquired in the Implementation phase are rolled out to the full development organization.
This phase, depending on the size of the organization, can take in the order of twelve months.

The timescales given are for a large IT development organization, and can vary significantly depending on circumstances. Some transition programmes can complete within fifteen months, others take longer.

Each phase measures against success criteria defined in the Initiation Phase, and ends with a go/no-go decision for the next Phase, so that IT management can control the pace and direction of the transition.

While ETP helps identify the most practical path for a transition, it does not restrict an organization in what development methodology is adopted for specific projects. For example, any of the generally accepted analysis and design methodologies can be supported within ETP. What ETP does is to provide techniques and guidelines that support a rapid, goal-oriented transfer of technology, know-how, architecture, tools, and methodology across multiple projects.