Create Ongoing Engineering Rotation

[smarithaponnala]

User Story or Problem Statement

As an engineer, I want to be onboarded to PagerDuty and assigned a recurring on-call rotation so that I can respond to incidents and perform resolution.

CMS needs to have a rotation of engineers who are supporting outages and urgent requests, so that we are not only reliant on Tim.

Revelant Links

• CMS Engineering Rotation #20318
• https://dsva.slack.com/archives/CT4GZBM8F/p1738694305775629

Acceptance Criteria and Implement Steps

• Onboarding & Rotation Setup:

1. Engineers are added to PagerDuty and assigned to a recurring monthly on-call schedule.
2. Each sprint, the current on-call engineer has a task for their oncall.
3. Adjustments are made for PTO or availability conflicts.

• Capacity Adjustment:

1. Engineers on-call will have a reduced workload for other sprint tasks (exact percentage TBD).

• On-Call Responsibilities:

1. First responder for incidents and alerts.
2. Perform the following housekeeping tasks as part of their rotation:
3. Review pull requests in our three repositories.
4. Review and address security alerts.
5. Check Drupal for package updates, since Dependabot is no longer handling them.

• Sprint Ticketing

1. Two Github (or equivalent) tickets are created each sprint and assigned to the on-call engineers.
2. Tickets include the above review tasks and tracking of incident response efforts.