Blog Posts Process Analysis

Delivery – Implement Only Process Path Template

Blog: Biz-Performance, David Brown

Delivery – Implement Only

This path is a subset of the normal Delivery processes.  It does not include design or development tasks as it is targeted at a system that is pre-defined and non-configurable.  However, the same (or greater) care must be taken with environmental, human and organisational issues, as there is less likelihood that an organisation’s overall needs will be fully addressed by a fixed configuration solution.





Review technical environment and plan installation
Optional – usually required when insufficient detail was included in the Delivery Approach documentation and segment plan
Plan in detail the physical installation of the packaged software, additional systems software, hardware, communications equipment, servers, PCs etc. Note that increasingly this task is performed by the vendor.
Plan, prepare and conduct project team training
Optional – usually required unless whole team have requisite experience in all aspects of the solution.
Normally, team members need training before productive work can commence.  Training may also be appropriate for management and other staff working with the project team.
Install hardware, communications equipment, system software, and applications software as required for development, implementation and live running.
Optional – required when insufficient provision is already available for the project.
Install and commission items required for design, development, implementation and live running.  This includes system environment requirements, eg log ons, access security, accounts, budgets etc.  With medium systems this is often performed by the vendor.
Data Conversion Strategy
Optional – used where existing data will be brought into the new system
A study should be made into the needs for data conversion.  Data availability and integrity is often wrongly assumed during design work. Recommendations will be made for securing data as required.
Prepare discussion papers
Optional – discussion papers may have been identified in the segment plan or may be used to explore any particular issue that arises as the team see fit.
These are short papers covering a particular subject.  They are not formally controlled, reviewed or signed off.  Their purpose is to assist in the process of deciding an issue during the design work.
Design/Prototype – Brief Implementation Papers
Normal practice
Design or define each topic within the project, using prototyping techniques wherever appropriate,  documenting the recommended approach and details in a Brief Implementation Paper (BIP) per topic.
Issues – control, escalate, resolve
Optional – used where there are several people involved in the project
Issues that arise during the design work are noted, logged, controlled and resolved.  Escalation and tie-breaking mechanisms are used where necessary.
Prepare and instigate operators’ instructions, procedures and manual
Optional – depending on suitability of vendor’s standard materials available
Prepare detailed instructions for the  technical operation of the system, including routine and abnormal running, eg security, disaster recovery.  This will normally include operational-standard JCL and the definition of human/machine interactions.
Identify human and organisational issues
Optional – used where there are several users affected by the project.
Assessment of the required organisational change, and resistance to such a change.
Implement change management programme
Optional – used where organisational change is necessary
Prepare and agree a plan for achieving the human and organisational change through communications, publicity, cascade sponsorship, policies, education etc. Instigate and act upon the plan.
Prepare and instigate User Procedures and User Manual / electronic information
Normal practice
Human procedures should be defined and agreed as part of the functional design work. Manuals or electronic documentation of the procedures and how to use the system should be extracted from the implementation papers and expanded/supplemented as necessary.
Plan, prepare and conduct user and management training and education
Optional – used where user and/or management training is required
Full user training is vital both to the successful use of the system and also to its acceptance and successful take up.  An effective programme should be developed based on the identified training needs of all users and management.
Plan, prepare and conduct operations training
Optional – used where operations staff require training
Computer Operations staff must be trained in running the application.  They must be familiar with the normal interactions that are required and what abnormal conditions they might be expected to handle.
Plan, prepare and conduct User / System / Acceptance and Integration testing
Formal testing must be performed to ensure that all significant aspects of the system are acceptable.  Careful planning and preparation is required to ensure it is complete and comprehensive.  Results must be reviewed and signed off by responsible users.
Plan, prepare and conduct technical tuning and volume testing
Normal practice
The system will need technical tuning to ensure acceptable performance.  Volume testing ensures that full volumes of data and transactions can be accommodated.  Testing should prove that normal loads can be sustained and peak loads can be accommodated.
Define, plan and agree handover / cutover
Normal practice
An analysis should be made of the logistical requirements for changing over to the new systems.  Detailed timings must be considered and agreed.
Define and agree terms of reference for live user support activity
Optional – used where post live support will be required
Analyse and agree the requirement and constitution of functional and technical user support for the live system, eg systems control, help desk, scheduling etc.
Load start up data
Normal practice
All initial data should be loaded.  Includes running of conversion suites and manual data entry.
Validate start up data
Normal practice
Complete loaded data should be validated and signed off by the responsible user managers.
Decision to go live
The ultimate governing body or manager for the project should take the definitive decision to go live.  It must be certain that all vital pre-conditions have been satisfied to at least a minimum level, eg testing, data validation, training, organisation.

Leave a Comment

Get the BPI Web Feed

Using the HTML code below, you can display this Business Process Incubator page content with the current filter and sorting inside your web site for FREE.

Copy/Paste this code in your website html code:

<iframe src="" frameborder="0" scrolling="auto" width="100%" height="700">

Customizing your BPI Web Feed

You can click on the Get the BPI Web Feed link on any of our page to create the best possible feed for your site. Here are a few tips to customize your BPI Web Feed.

Customizing the Content Filter
On any page, you can add filter criteria using the MORE FILTERS interface:

Customizing the Content Filter

Customizing the Content Sorting
Clicking on the sorting options will also change the way your BPI Web Feed will be ordered on your site:

Get the BPI Web Feed

Some integration examples