Project Manager
- ITIL
- Change Management
- Incident Management
- AI
- Agile
- Oracle Cloud
Job Description
Based on ITIL best practices and responsibilities commonly used in enterprise support and transition programs, plus references found in your transition and CAB-related materials, here is a professional role description for both positions.Â
Change Management is primarily responsible for the overall quality of the Change Management process and verifies that Changes are communicated in a timely and adequate manner. He or she is the main coordinator within this process and is the focal regarding Changes for BIMBO IT organization.
Roles and Responsibilities
- Responsibilities include, but are not limited to, those listed for each role.
- Roles are meant as logical groupings of tasks. They are not intended to match particular organizational structure or formal job roles.
- Several roles may be performed by the same individual provided proper segregation of duties is maintained.
- A role may be split up among several individuals.
Change Management Team leader
The Change Group Leader has overall responsibility for assigning the change workload that is referred to his or her Change Group.
Â
Specific responsibilities include:
- Monitoring the Change Group queue for incoming Changes
- Verifying each Change is assigned to a proper workgroup
- Identifying Change assignment issues and escalating incorrect assignments to Change Management, as required
- Reassigning an inappropriately assigned Change Record to the correct Change group and notifying that Change Group Leader as required
- Verifying their Change Group complies with the Change Process
- Requesting education for group members when required
- Acting as point of escalation for day-to-day schedule slips as required to bring the Change back on schedule
- Monitoring that issues encountered during the implementation of a Change are properly documented in the Change Record
- Reviewing Changes for process compliance
- Creating and distributing Change Management reports (Dashboard / KPIs)
- Identifying Change Requests that have not been acted upon in a timely manner and takes appropriate action.
- Reviewing failed and canceled Changes to verify the cause of the failure or cancellation.
- Drive continuous improvement of the Change Management process.
Â
Change Owner
The Change Owner is responsible for an individual Change. The Change Owner follows the Change from beginning to end, bringing in analysts and specialists as needed to complete the project. The Change Owner is responsible for seeing that analysts and specialists bring the Change to a close.
Â
   Specific responsibilities include:
- Verifying the supporting documentation accompanying the Change Record is complete. If required information is missing, the Change Owner is responsible for obtaining additional information and updating the Change Record and Change Plan including:
- Detailed description
- Risk identification
- Execution procedure (Step by step checklist), functional test and backout plans
- Declare possible BIMBO business impact
- Describe Impacted systems
- Setting the technical risk of the Change.
- Identifying groups to contribute resources and skills for the Change.
- Preparing the Change, providing detailed change information.
- Conducting post review to verify successful implementation along with identification of any external impacts or new requirements.
- Notifying the Change Requestor of Unsuccessful Changes.
- Follow up and coordinate the change execution.
- Assist the Change Requestor to accomplish change objective.
- Obtain approvals and make sure the change record is approved on time.
- Assist in the CAB/UCAB/ECAB Change Meetings.
- Build up a Communication Plan.
- Close the Change record with the corresponding closure code.
CAB (Change Advisory Board) Manager / Lead
Role Purpose
The CAB Manager is responsible for governing the Change Management process, ensuring all production changes are assessed, reviewed, approved, scheduled, and implemented with minimal business risk and service disruption. The role chairs CAB meetings and coordinates stakeholders across applications, infrastructure, security, and business teams.
Key Responsibilities
- Lead and facilitate CAB,Urgent CAB (UCAB) and Emergency CAB (ECAB) meetings.
- Emergency Change applicable only to operational Incident that always have to be triggered from MIM (Major Incident Management) with Incident (P1 | P2). The approvals will be given during MIM session and must be closed during the session. A reconvene must be made if the execution is not finished. In case an Emergency Change that does not have MIM (Major Incident Management) will be closed and it will be reported by escalation because is not aligned to the Change Control Process.
- Urgent Change will be associated with any situation with an imminent impact on the business, financial or legal situation. Isnot allowed as urgent change because of an immediate schedule of execution.
- Chairing the Change Advisory Board (CAB) meetings as required.
- Recording actions taken during an Emergency Change.
- Building and maintaining the Forward Schedule of Change (Consolidated Change Schedule).
- Integrating new Changes into the existing change schedule.
- Review, assess, and prioritize Change Requests (CRs/RFCs).
- Evaluate business impact, technical impact, risks, dependencies, and rollback plans.
- Ensure compliance with ITIL Change Management processes and organizational policies.
- Coordinate with application teams, infrastructure teams, vendors, and business stakeholders.
- Verifying no outstanding issues exist that require additional attention
- Verifying those issues are resolved and addressed by the appropriate individuals.
- Verifying required technical information (documents) included in the Change Record.
- Obtain additional information if required.
- Approve, reject, or escalate changes based on risk and governance requirements.Making the final decision concerning whether the Change is authorized or not.
- Notify to the affected groups if the change has been rejected.
- Ensure adequate testing, implementation, validation, and backout plans exist.
- Monitor change success rates and track change-related incidents.
- Conduct Post Implementation Reviews (PIRs) for failed or high-risk changes.
- Facilitating and assisting in resolving conflicts in the schedule and negotiating adjustments with the relevant parties.
- Preparing the Change CAB Minute, providing detailed change information.
Key Deliverables
- CAB agenda and minutes.
- Change risk assessments.
- Change approval records.
- Forward Schedule of Changes.
- Change success and compliance metrics.
EEO/About Us
About Us
Infosys is a global leader in next-generation digital services and consulting. We enable clients in more than 50 countries to navigate their digital transformation. With over four decades of experience in managing the systems and workings of global enterprises, we expertly steer our clients through their digital journey. We do it by enabling the enterprise with an AI-powered core that helps prioritize the execution of change. We also empower the business with agile digital at scale to deliver unprecedented levels of performance and customer delight. Our always-on learning agenda drives their continuous improvement through building and transferring digital skills, expertise, and ideas from our innovation ecosystem.
EEO
Infosys provides equal employment opportunities to applicants and employees without regard to race; color; sex; gender identity; sexual orientation; religious practices and observances; national origin; pregnancy, childbirth, or related medical conditions; status as a protected veteran or spouse/family member of a protected veteran; or disability.
Skillset
Process|Maintenance and Production Support process|Support Process - Transition, Process|Quality models/improvement frameworks|CMMi for Development, Process|Service Management|ITIL, Technology|Oracle Cloud|Project Management Cloud- Domain: Retail ,CPG and logistics
Project Manager · Infosys