Strategic Board
Design Division
Transition Division
Operations Division
Improvement Division


ITIL-V3 Bookcase
Table of Contents
Close this Page

Change Manager
Project Manager
Development Manager
Deployment Manager
Valdation Manager
Configuration Manager
Knowledge Manager


Transition Division

ITIL : 3.2 Transition Planning and Support : Project Manager

3.2 Project Manager:
Every development project has a Project Manager to drive the planning, design, development, testing and transition to operations.
Even a modest project is complex and demands highly skilled people to be motivated to overcome all the problems that will get in the way.
  01 ISO 9001 Quality Management Standard  

PRINCE2:
Project planning uses PRINCE2 as the UK approved methodology for any kind of project and IT projects in particular.
By having a stable methodology, the Project Manager works in a way where everybody around them knows what is happening, knows where to access all relevant documentation and provides a platform for success.
PRINCE2 is very good at bringing together facts in such a way that a pending problem can be quickly identified and even a project that is not cost justified can be quickly terminated.

Project Framework:
Conversion projects are best treated as a normal development project where the specification of business requirements is well specified in the form of existing source code.
We are highly skilled in the rapid delivery of demonstrable online services, the critical starting point is the scope of business requirement.
Existing source code has significant benefits in that the pedantic detail of field size and permitted values can be derived by inspection or automation.
A potention problem is that the old system design may unduly influence the user interface.
It is very difficult to design a simple solution and where hundreds of existing user interfaces exist it is too easy to replicate what existed into an overly complex service.

Computing in the cloud:
Our web-based application services have considerable benefits over old windows-based systems that should not be influenced by a conversion project.
Application in the cloud are scalable to any number of users with only modest database administration costs.
Applications are free of any dependent computer of smart phone restrictions - any browser on any computer with any operating system can be used.
Applications may be used by authorized people from any location; in the office, with a client, one the road and from home.
Costs are reduced by eliminating the need to install software on computers, by making certain that all user are always using the very latest version of the application and automating business continuity from multiple remote data centers.

PRINCE2:
It would not be reasonable to document our entire PRINCE2 project management procedures within this ITIL document.
It can be implied that each and every PRINCE2 step isperformed in accordance with PRINCE2 standards.
This enables us to professionally manage all projects in the certain knowledge that our clients can monitor all activities as PRINCE2 tasks and deliverables.

Multiple Language Support:
Built into the infrastructure of all our web application services is support for multiple human languages.
Implementation is generally where each authorized user selects the language that they choose to work with and this is stored in their user profile.   When that user signs in, the user interface uses the human language that they have pre-selected.
Many people using different human languages can use the application service at the same time and share data as if they were all using the same human language.   Multiple language support carries no processing overhead as only one language file is loaded to process any one transaction.

Translation:
Data is stored in the database in the language that the data is entered.
Business notes and comments can be translated into another human language in a simply way that may be adequate for internal business use.   Translation is not to legal quality and should not be used in external correspondance that is subject to terms and conditions.
Management information may be generated in different languages from data stored in the database, but that information canot be translated again into another language.   True round-trip translation facilities are not provided.

  
3.3.1 Application Development without Programming
In 1979, Terry Wilcox published Application Development without Programming (ADWP) as the framework of what is now a trade secret.
  02 Development without Programming  

Conversion:
1.Transition strategy (a brief outline of the selected approach to implementing the new service)
. 1.Testing strategy
. 2.Deployment strategy
. 3.Migration concept
. 4.Back-out strategy in the case of a failed deployment
2.Decomposition of the Business Service into Infrastructure Services
. 1.Internal Infrastructure Services on which this service is based
.. 1.Names of the infrastructure services
.. 2.Service providers (responsible Service Owners)
.. 3.References to Operational Level Agreements (OLAs)
.. 4.Required changes to OLAs, if existing OLAs are not sufficient for the service to be established
. 2.Externally supplied Supporting Services on which this service is based
.. 1.Names of the external services
.. 2.Name of the supplier
.. 3.Responsible Supplier Manager
.. 4.References to Underpinning Contracts (UCs)
.. 5.Required changes to UCs, if existing UCs do not support the introduction of the new service
. 3.Details on technical changes required to build, test, deploy and operate the service
.. 1.Development/ customization of base applications for the service (e.g. if the service to be introduced is based on the SAP system or a custom application)
.. 2.Supporting tools
... 1.Development/ customization of migration tools
... 2.Development/ customization of testing tools
... 3.Development/ customization of deployment tools
... 4.Development/ customization of back-out tools in the case of a failed release deployment
.. 3.Infrastructure modifications required to build, test, deploy and operate the service
... 1.Infrastructure components to be purchased and installed
... 2.Infrastructure components to be (re-)configured
.. 4.Required changes to facilities
. 4.Organizational changes required to implement and operate the service
.. 1.Personnel resources to be added
... 1.Specification of required resources
... 2.Strategy for acquiring the resources
.. 2.Skills to be developed
... 1.Specification of the required skills
... 2.Strategy for acquiring the skills
.. 3.Changes to processes
... 1.List of IT processes which must be changed or created, including process owners
... 2.Detailed specification of required changes to IT processes, e.g. in the form of process designs
5.Operational concept, e.g.
. 1.Routine administrative tasks to be carried out
. 2.Rules for archiving and backup