"> Change Acceptance (IT) and Transitioning – BAI07 (COBIT2019) – Process-Symphony – ITSM Knowledge Orchestrators

Search Knowledge

Change Acceptance (IT) and Transitioning – BAI07 (COBIT2019)

Parent Framework: COBIT 2019

Domain: Build, Acquire and Implement

Managed Change Acceptance and Transitioning

Formally accept and make operational new solutions. Include implementation planning, system and data conversion, acceptance testing,

communication, release preparation, promotion to production of new or changed business processes and I&T services, early production support, and

a post-implementation review.


Implement solutions safely and in line with the agreed expectations and outcomes.

Management Practice

BAI07.01 Establish an implementation plan.

Establish an implementation plan that covers system and data conversion, acceptance testing criteria, communication, training, release preparation, promotion to production, early production support, a fallback/back-up plan, and a post-implementation review. Obtain approval from relevant parties.

BAI07.02 Plan business process, system and data conversion.

Prepare for business process, I&T service data and infrastructure migration as part of the enterprise’s development methods. Include audit trails and a recovery plan should the migration fail.

BAI07.03 Plan acceptance tests.

Establish a test plan based on enterprise wide standards that define roles, responsibilities, and entry and exit criteria. Ensure that the plan is approved by relevant parties.

BAI07.04 Establish a test environment.

Define and establish a secure test environment representative of the planned business process and IT operations environment in terms of performance, capacity, security, internal controls, operational practices, data quality, privacy requirements and workloads.

BAI07.05 Perform acceptance tests.

Test changes independently, in accordance with the defined test plan, prior to migration to the live operational environment.

BAI07.06 Promote to production and manage releases.

Promote the accepted solution to the business and operations. Where appropriate, run the solution as a pilot implementation or in parallel with the old solution for a defined period and compare behavior and results.

If significant problems occur, revert to the original environment based on the fallback/back-up plan. Manage releases of solution components.

BAI07.07 Provide early production support.

For an agreed period of time, provide early support to users and I&T operations to resolve issues and help stabilize the new solution.

BAI07.08 Perform a post-implementation review.

Conduct a post-implementation review to confirm outcome and results,identify lessons learned, and develop an action plan. Evaluate actual performance and outcomes of the new or changed service against expected performance and outcomes anticipated by the user or customer.


Business process testing BPTS

The planning, design, management, execution and reporting of business process tests and usability evaluations. The application of evaluation skills to the assessment of the ergonomics, usability and fitness for purpose of defined processes. This includes the synthesis of test tasks to be performed (from statement of user needs and user interface specification), the design of an evaluation programme, the selection of user samples, the analysis of performance, and inputting results to the development team.


Release and deployment RELM

The management of the processes, systems and functions to package, build, test and deploy changes and updates (which are bounded as “releases”) into a live environment, establishing or continuing the specified service, to enable controlled and effective handover to operational management and the user community. The application of automation to improve the efficiency and quality of releases.


Service acceptance SEAC

The achievement of formal confirmation that service acceptance criteria have been met, and that the service provider is ready to operate the new service when it has been deployed. (Service acceptance criteria are used to ensure that a service meets the defined service requirements, including functionality, operational support, performance and quality requirements).


Testing TEST

The planning, design, management, execution and reporting of tests, using appropriate testing tools and techniques and conforming to agreed process standards and industry specific regulations. The purpose of testing is to ensure that new and amended systems, configurations, packages, or services, together with any interfaces, perform as specified (including security requirements) , and that the risks associated with deployment are adequately understood and documented. Testing includes the process of engineering, using and maintaining testware (test cases, test scripts, test reports, test plans, etc) to measure and improve the quality of the software being tested.


User experience evaluation USEV

Validation of systems, products or services, to assure that the stakeholder and organisational requirements have been met, required practice has been followed, and systems in use continue to meet organisational and user needs. Iterative assessment (from early prototypes to final live implementation) of effectiveness, efficiency, user satisfaction, health and safety, and accessibility to measure or improve the usability of new or existing processes, with the intention of achieving optimum levels of product or service usability.


{{ reviewsOverall }} / 5 Users (0 votes)
What people say... Login to rate
Order by:

Be the first to leave a review.

/ 5
{{{review.rating_comment | nl2br}}}

Show more
{{ pageNumber+1 }}