Make Incident Retrospectives Part of Engineering Culture

This standard mandates the integration of incident retrospectives into daily engineering workflows to embed learning from failures into the organisation's culture.

1. Make Incident Retrospectives Part of Engineering Culture:

Learning from failures should be embedded in daily workflows, not just crisis moments. This approach ensures continuous improvement and resilience.

• 1.1 Integration into Workflows:
  • 1.1.1 Sprint Reviews:
    • Include incident learnings in sprint reviews and team retrospectives.
    • Automate the inclusion of incident learnings in sprint reports.
  • 1.1.2 Near Miss Discussions:
    • Encourage teams to proactively discuss near misses, not just major outages.
    • Automate the tracking of near miss discussions.
• 1.2 Regular Engineering Practice:
  • 1.2.1 Post-Incident Learning:
    • Make post-incident learning a regular engineering practice, not an exception.
    • Automate the scheduling of post-incident learning sessions.
  • 1.2.2 Continuous Improvement:
    • Embed a culture of continuous improvement based on incident learnings.
    • Automate the tracking of improvement actions.

By making incident retrospectives part of engineering culture, organisations can ensure continuous learning and improvement.

---