Incident Report:

Required Pre-Read

Include links to any relevant documentation or pre-read material that provides context or necessary background information about the incident.

Attendees

List all individuals involved in the incident analysis and resolution. Include names and roles.

Agenda

Outline the topics and activities planned for the incident review meeting. Be clear about the objectives and expected outcomes of each agenda item.

Checklist & Prompts

Provide a list of standard questions or prompts to guide the incident analysis. This may include questions about the incident process, playbooks used, and potential improvements.

Reference Material

Include any relevant reference materials such as incident category, duration, impact, and links to incident threads or tickets.

Timeline

Provide a detailed timeline of the incident, including key events, actions taken, and decisions made.

Discussion

Incident Process Adherence

Discuss whether the existing incident process was followed and document any deviations.

Playbooks Used

Detail the playbooks or standard procedures that were utilized during the incident.

Prevention Strategies

Identify strategies or actions that could prevent similar incidents in the future.

Mitigation Improvement

Suggest ways to reduce the time to mitigate similar incidents in the future.

Summary

Provide a concise summary of the incident, including main takeaways, lessons learned, and any follow-up actions.

</div><div 
  data-tab-item="Markdown"
  data-tab-group="default"
  class='tab-item '>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-Markdown" data-lang="Markdown"><span class="line"><span class="cl"><span class="gh"># Incident Report: &lt;incident name&gt;

| Lead | Empty | | —————- | —– | | Analysis Date | Empty | | Severity | Empty | | Treatment Ticket | Empty | <aside> ⚠️ Guidelines for Incident Reports - Fast and light: Keep the report concise, ≤ 500 words, less than an hour of your time. Be scrappy, delete sections in this template you don’t need. Aim to write up within 24-48 hours of the incident being resolved - Just the facts: avoid unecessary jargon, write just enough to provide a clear understanding of what happened and when. Focus on facts and avoid placing blame. The goal is to learn and improve. - Make it useful: Highlight key learnings and actionable items for preventing future incidents. Get a review before it gets sent out. Follow up and commit to delivering actions. - Share what you learnt: Share it asynchronously on #tech, considering bringing it to DevCru to present. - Severity: Use the [Bug and Incident Severity Guide](./bug_and_incident_severity.md)) to grade the incident with a severity. </aside> ## Required Pre-Read Include links to any relevant documentation or pre-read material that provides context or necessary background information about the incident. ## Attendees List all individuals involved in the incident analysis and resolution. Include names and roles. ## Agenda Outline the topics and activities planned for the incident review meeting. Be clear about the objectives and expected outcomes of each agenda item. ## Checklist & Prompts Provide a list of standard questions or prompts to guide the incident analysis. This may include questions about the incident process, playbooks used, and potential improvements. ## Reference Material Include any relevant reference materials such as incident category, duration, impact, and links to incident threads or tickets. ## Timeline Provide a detailed timeline of the incident, including key events, actions taken, and decisions made. ## Discussion ### Incident Process Adherence Discuss whether the existing incident process was followed and document any deviations. ### Playbooks Used Detail the playbooks or standard procedures that were utilized during the incident. ### Prevention Strategies Identify strategies or actions that could prevent similar incidents in the future. ### Mitigation Improvement Suggest ways to reduce the time to mitigate similar incidents in the future. ## Summary Provide a concise summary of the incident, including main takeaways, lessons learned, and any follow-up actions. —