Craig Kerstiens • 12/26/2017

Guidance on performing retrospectives

Read Original

This article provides practical guidance for running software engineering retrospectives after outages or incidents. It covers capturing details, structuring the meeting, and focusing on process improvements rather than blame, aimed at helping teams learn and prevent future issues.

0 comments
#DevOps #incident management #Postmortem
Guidance on performing retrospectives

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
The Beautiful Web
Jens Oliver Meiert • 2 votes
2
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane • 1 votes
3
LLM Use in the Python Source Code
Miguel Grinberg • 1 votes
4
Wagon’s algorithm in Python
John D. Cook • 1 votes
5
An example conversation with Claude Code
Dumm Zeuch • 1 votes