Scribd
Upload
14 views3 pages

Change RQT For Cardless

Uploaded by

abrihammulat34
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
14 views3 pages

Change RQT For Cardless

Uploaded by

abrihammulat34
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

IT Change Request Form

Requester’s Detail
RFC Number:
Requesting Organ
(Department):
Digital Banknking Business
Email address: [email protected]
Telephone number: Date of request: Proposed Change Implementation Date Required Down Time
0945556958 Jan, 2025

**Remark: missing to fill a detail or providing incorrect details may lead to form rejection.

Change Details
Please describe the change you are requesting.
Short change Cardless Transaction
request title
Change type ☒ Normal ☐Emergency ☐Standard

☐Application ☐Hardware ☐Operating System ☐Storage ☐ Service Outage


Change Area
☐ Database ☐Network ☐ Security ☐ Process ☐Document

☒Environment
Change Category ☒New Feature ☐Configuration

☐Other (Specify):_______________________________

Full Description of This change request involves deploying the cardless transaction feature from the
the Change:
test environment to the production environment. The feature has been
thoroughly tested and validated in the test environment, ensuring functionality,
security, and performance meet the required standards.
Priority ☒1 – Urgent: “I can’t move forward until this change is resolved.”
☐2 – High: “I’m fine for right now, but unless this change is resolved until
______, I won’t be able to move forward.”
☐3 – Medium: “I’m fine for right now, but this may impact my ability to move forward
in the near future.”
☐ 4 – Minor: “This change is not impacting my ability to move forward.”
Test plan Attach as separate file
Implementation Attach as separate file
Action plan
Remediation /Fall Attach as separate file
Back plan

Change Justification
Please provide your reasoning for this request. Purpose: Performance improvement, security hardening, etc.
Reason /Justification for the The migration of the cardless transaction feature from the test environment to
change production is essential to deliver this functionality to end-users. The feature has
successfully passed all test cases and meets performance, security, and
reliability standards. Deploying it in the production environment will enhance
customer experience by providing a seamless and efficient transaction method,
aligning with business objectives and user expectations.
Business purpose / Enhance customer convenience and satisfaction by enabling secure, cardless
Technical benefit transactions.Ensure reliable, scalable, and efficient transaction processing in the
production environment.
Cross-reference to the related
RFC (if available)
Annex 1 RFC No. Last revised :
IT Change Request Form

Environment (s) Impacted


Please list Processes, products, modules, files, programs etc that could be affected by the change.
1. Middleware
2. CBS
3. MB-APP
4. MB_USSD

Risk Impact
Please select the possible risk impact of the change. You may use the “Risk Assessment Guideline”.
Risk Impact Severity ☐1 - Critical Impact: Total Production failure
☐2 - High Impact: Significant degradation of production environment performance.
☐3 - Medium Impact: Manageable degradation of production environment
performance.
☒4 - Minor Impact: Minor performance degradation of production environment
Time impact if the risk
materialize
Resource requirements:
( consultant , h/w, s/w )
Configuration Item (CI)

Change Requester (Manager)

Name: Girum Bogale Signature:_________________ Date: January 1, 2025

Received by: _________________________ Signature______________ Date:_____________

Change Approved by: __________________ Signature______________ Date:_____________

Change Authorized by: _________________

Disposition:
☐Approved for Immediate Work
☐Approved as Prioritized
☐ Approved for Further Investigation (Cost/Benefit, Impact Analysis)
☐ Request Rejected
Implementation Date & Time:

Communication Plan:

Annex 1 RFC No. Last revised :


IT Change Request Form

Change Advisory Board use only

Change Advisory Board :


Position Name Signature Date
☐ CIO

☐ Director- Application Management

☐ Director- Infrastructure Management

☐ Director- IS Security

☐ Manager- Application Management

☐ Manager- Infrastructure Management

☐ Director- Digital Banking

☐ Manager- Digital Banking

☐ Director- International Banking


Operation
☐ Subject Matter Experts

Annex 1 RFC No. Last revised :

You might also like