Epic Goal

Retrospective to squeeze improvements out of the incident.

Why is this important?

Improving the future to limit our exposure to previously-identified issues. We have existing tickets like OTA-681 tracking improvements. This ticket isn't intended to hold work itself, it's tracking the incident and linking out to other tickets (in any project) that would have helped with this incident.

Scenarios

The Cincinnati pods backing the OpenShift Update Service had a few hours of struggle and drama. We would prefer to address the tooling to make that kind of incident less likely in the future. Making it easy to manage related work makes it more likely that that work is identified, prioritized, and delivered.

Dependencies

No actual work under this ticket; it's just a place for priority-setters to see links to tickets in other places that might be worth prioritizing.

Acceptance Criteria

We'll close once we get through the retro, since folks are unlikely to be brainstorming about new work to link after that point.

Drawbacks or Risk

Maybe we're comfortable with our current service level objectives and don't think it's worth trying to brainstorm or prioritize further improvements.

Done - Checklist

• Retro meeting complete.
• At least OTA team lead and project manager have reviewed linked tickets to assess their priority.