Skip to main content

CobiT

Go Search
Home
  
CobiT > Wiki Pages > WorkDefinition - Install and Accredit Solutions and Changes  

WorkDefinition - Install and Accredit Solutions and Changes

WorkDefinition Information

Install and Accredit Solutions and Changes

Description

New systems need to be made operational once development is complete. This requires proper testing in a dedicated environment with relevant test data, definition of rollout and migration instructions, release planning and actual promotion to production, and a post-implementation review. This assures that operational systems are in line with the agreed-upon expectations and outcomes.

Maturity Model

Management of the process of Install and accredit solutions and changes that satisfies the business requirement for IT of implementing new or changed systems that work without major problems after installation is:

0 Non-existent when
There is a complete lack of formal installation or accreditation processes, and neither senior management nor IT staff members recognise the need to verify that solutions are fit for the intended purpose.

1 Initial/Ad Hoc when
There is an awareness of the need to verify and confirm that implemented solutions serve the intended purpose. Testing is performed for some projects, but the initiative for testing is left to the individual project teams, and the approaches taken vary.Formal accreditation and sign-off are rare or non-existent.

2 Repeatable but Intuitive when
There is some consistency amongst the testing and accreditation approaches, but typically they are not based on any methodology.The individual development teams normally decide the testing approach, and there is usually an absence of integration testing. Thereis an informal approval process.

3 Defined when
A formal methodology relating to installation, migration, conversion and acceptance is in place. IT installation and accreditation processes are integrated into the system life cycle and automated to some extent. Training, testing and transition to production status and accreditation are likely to vary from the defined process, based on individual decisions. The quality of systems entering production is inconsistent, with new systems often generating a significant level of post-implementation problems.

4 Managed and Measurable when
The procedures are formalised and developed to be well organised and practical with defined test environments and accreditation procedures. In practice, all major changes to systems follow this formalised approach. Evaluation of meeting user requirements is standardised and measurable, producing metrics that can be effectively reviewed and analysed by management. The quality of systems entering production is satisfactory to management even with reasonable levels of post-implementation problems. Automation of the process is ad hoc and project-dependent. Management may be satisfied with the current level of efficiency despite the lack of post-implementaiton evaluation. The test system adequately reflects the live environment. Stress testing for new systems and regression testing for existing systems are applied for major projects.

5 Optimised when
The installation and accreditation processes have been refined to a level of good practice, based on the results of continuous improvement and refinement. IT installation and accreditation processes are fully integrated into the system life cycle and automated when appropriate, facilitating the most efficient training, testing and transition to production status of new systems.Well-developed test environments, problem registers and fault resolution processes ensure efficient and effective transition to the production environment. Accreditation usually takes place with no rework, and post-implementation problems are normally limited to minor corrections. Post-implementation reviews are standardised, with lessons learned channelled back into the process to ensure
continuous quality improvement. Stress testing for new systems and regression testing for modified systems are consistently applied.

Define and review a test strategy (entry and exit criteria) and an operational test plan methodologyPerform system conversion and integration tests on test environmentRecommend promotion to production based on agreed-upon accreditation criteriaBuild and maintain a business and technical requirements repository and test cases for accredited systemsDeploy a test environment and conduct final acceptance testsBuild and review implementation plans

Attributes

Element CategoriesAI7.7 Final Acceptance Test, AI7.6 Testing of Changes, AI7.9 Post-implementation Review, AI7.8 Promotion to Production, AI7.3 Implementation Plan, AI7.4 Test Environment, AI7.2 Test Plan, AI7.5 System and Data Conversion, AI7 Install and Accredit Solutions and Changes, AI7.1 Training
IT ResourcesApplication, Information, Infrastructure, People
Primary Business RequirementsEffectiveness
Secondary Business RequirementsAvailability, Efficiency, Integrity
Primary IT Governance Focus AreasValue delivery
Secondary IT Governance Focus AreasPerformance measurement, Resource management, Risk management, Strategic alignment
Goals and Metrics

IT Goals
-Ensure that automated business transactions and information exchanges can be trusted
-Reduce solution and service delivery defects and rework
-Respond to business requirements in alignment with the business strategy
-Ensure seamless integration of applications into business processes
-Ensure proper use and performance of the applications and technology solutions
-Ensure that IT services and the IT infrastructure can properly resist and recover from failure due to error,delivered attack or disaster

IT Metrics
-Percent of stakeholders satisfied with the data integrity of new systems
-Percent of systems that met expected benefits as measured by the post-implementation process


Process Goals
-Verify and confirm that applications and technology solutions are fit for the intended purpose
-Release and properly distribute approved applications and technology solutions
-Prepare business users and operations for using applications and technology solutions
-Ensure that new business applications and changes to existing applications are free from errors

Process Metrics
-Number of errors found during internal or external audits regarding the installation and accreditation process
-Rework after implementation due to inadequate acceptance testing
-Service desk calls from users due to inadequate training
-Application downtime or data fixes caused by inadequate testing


Activity Goals
-Establishing a test methodology that ensures sufficient acceptance testing prior to go-live
-Tracking changes to all configuration items
-Undertaking release planning
-Performing post-implementation reviews
-Evaluating and approving test results by business management

Activity Metrics
-Degree of stakeholder involvement in the installation and accreditation process
-Percent of projects with a documented and approved testing plan
-Number of lessons learnt from postimplementation review
-Percent of errors found during QA review of installation and accreditation functions
-Number of changes without required management sign-off before implementation

Last modified at 12/10/2007 3:51 PM  by Administrator